@robbiesrobotics/alice-agents 1.5.11 → 1.5.13

package/templates/workspaces/olivia/skills/marketing-strategy-pmm/SKILL.md

@@ -1,398 +0,0 @@
----
-name: "marketing-strategy-pmm"
-description: Product marketing skill for positioning, GTM strategy, competitive intelligence, and product launches. Use when the user asks about product positioning, go-to-market planning, competitive analysis, target audience definition, ICP definition, market research, launch plans, or sales enablement. Covers April Dunford positioning, ICP definition, competitive battlecards, launch playbooks, and international market entry. Produces deliverables including positioning statements, battlecard documents, launch plans, and go-to-market strategies.
-triggers:
-  - product marketing
-  - PMM
-  - positioning
-  - GTM strategy
-  - go-to-market
-  - competitive analysis
-  - battlecard
-  - product launch
-  - market entry
-  - sales enablement
-  - win loss analysis
----
-
-# Marketing Strategy & PMM
-
-Product marketing patterns for positioning, GTM strategy, and competitive intelligence.
-
----
-
-## Table of Contents
-
-- [ICP Definition Workflow](#icp-definition-workflow)
-- [Positioning Development](#positioning-development)
-- [Competitive Intelligence](#competitive-intelligence)
-- [Product Launch Planning](#product-launch-planning)
-- [Sales Enablement](#sales-enablement)
-- [International Expansion](#international-expansion)
-- [Reference Documentation](#reference-documentation)
-
----
-
-## ICP Definition Workflow
-
-Define ideal customer profile for targeting:
-
-1. Analyze existing customers (top 20% by LTV)
-2. Identify common firmographics (size, industry, revenue)
-3. Map technographics (tools, maturity, integrations)
-4. Document psychographics (pain level, motivation, risk tolerance)
-5. Define 3-5 buyer personas (economic, technical, user)
-6. Validate against sales cycle and churn data
-7. Score prospects A/B/C/D based on ICP fit
-8. **Validation:** A-fit customers have lowest churn and fastest close
-
-### Firmographics Template
-
-| Dimension | Target Range | Rationale |
-|-----------|--------------|-----------|
-| Employees | 50-5000 | Series A sweet spot |
-| Revenue | $5M-$500M | Budget available |
-| Industry | SaaS, Tech, Services | Product fit |
-| Geography | US, UK, DACH | Market priority |
-| Funding | Seed to Growth | Willing to adopt |
-
-### Buyer Personas
-
-| Persona | Title | Goals | Messaging |
-|---------|-------|-------|-----------|
-| Economic Buyer | VP, Director, Head of [Department] | ROI, team productivity, cost reduction | Business outcomes, ROI, case studies |
-| Technical Buyer | Engineer, Architect, Tech Lead | Technical fit, easy integration | Architecture, security, documentation |
-| User/Champion | Manager, Team Lead, Power User | Makes job easier, quick wins | UX, ease of use, time savings |
-
-### ICP Validation Checklist
-
-- [ ] 5+ paying customers match this profile
-- [ ] Fastest sales cycles (< median)
-- [ ] Highest LTV (> median)
-- [ ] Lowest churn (< 5% annual)
-- [ ] Strong product engagement
-- [ ] Willing to do case studies
-
----
-
-## Positioning Development
-
-Develop positioning using April Dunford methodology:
-
-1. List competitive alternatives (direct, adjacent, status quo)
-2. Isolate unique attributes (features only you have)
-3. Map attributes to customer value (why it matters)
-4. Define best-fit customers (who cares most)
-5. Choose market category (head-to-head, niche, new category)
-6. Layer on relevant trends (timing justification)
-7. Test with 10+ customer interviews
-8. **Validation:** 7+ customers describe value unprompted
-
-### Positioning Statement Template
-
-```
-FOR [target customer]
-WHO [statement of need]
-THE [product] IS A [category]
-THAT [key benefit]
-UNLIKE [competitive alternative]
-OUR PRODUCT [primary differentiation]
-```
-
-### Value Proposition Formula
-
-Template: `[Product] helps [Target Customer] [Achieve Goal] by [Unique Approach]`
-
-Example: "Acme helps mid-market SaaS teams ship 2x faster by automating project workflows with AI"
-
-### Messaging Hierarchy
-
-| Level | Content | Example |
-|-------|---------|---------|
-| Headline | 5-7 words | "Ship faster with AI automation" |
-| Subhead | 1 sentence | "Automate workflows so teams focus on what matters" |
-| Benefits | 3-4 bullets | Speed, quality, collaboration, cost |
-| Features | Supporting evidence | AI automation → 10 hrs/week saved |
-| Proof | Social proof | Customer logos, stats, case studies |
-
----
-
-## Competitive Intelligence
-
-Build competitive knowledge base:
-
-1. Identify tier 1 (direct), tier 2 (adjacent), tier 3 (status quo)
-2. Sign up for competitor products (hands-on evaluation)
-3. Monitor competitor websites, pricing, messaging
-4. Analyze sales call recordings for competitor mentions
-5. Read G2/Capterra reviews (pros and cons)
-6. Track competitor job postings (roadmap signals)
-7. Update battlecards monthly
-8. **Validation:** Sales team uses battlecards in 80%+ competitive deals
-
-### Competitive Tier Structure
-
-| Tier | Definition | Examples |
-|------|------------|----------|
-| 1 | Direct competitor, same category | [Competitor A, B] |
-| 2 | Adjacent solution, overlapping use case | [Alt Solution C, D] |
-| 3 | Status quo (what they do today) | Spreadsheets, manual, in-house |
-
-### Battlecard Template
-
-```
-COMPETITOR: [Name]
-OVERVIEW: Founded [year], Funding [stage], Size [employees]
-
-POSITIONING:
-- They say: "[Their claim]"
-- Reality: [Your assessment]
-
-STRENGTHS:
-1. [What they do well]
-2. [What they do well]
-
-WEAKNESSES:
-1. [Where they fall short]
-2. [Where they fall short]
-
-OUR ADVANTAGES:
-1. [Your advantage + evidence]
-2. [Your advantage + evidence]
-
-WHEN WE WIN:
-- [Scenario where you win]
-
-WHEN WE LOSE:
-- [Scenario where they win]
-
-TALK TRACK:
-Objection: "[Common objection]"
-Response: "[Your response]"
-```
-
-### Win/Loss Analysis
-
-Track monthly:
-- Win rate by competitor
-- Top win reasons (product fit, ease of use, price)
-- Top loss reasons (missing feature, price, relationship)
-- Action items for product, sales, marketing
-
----
-
-## Product Launch Planning
-
-Plan launches by tier:
-
-| Tier | Scope | Prep Time | Budget |
-|------|-------|-----------|--------|
-| 1 | New product, major feature | 6-8 weeks | $50-100k |
-| 2 | Significant feature, integration | 3-4 weeks | $10-25k |
-| 3 | Small improvement | 1 week | <$5k |
-
-### Tier 1 Launch Workflow
-
-Execute major product launch:
-
-1. Kickoff meeting with Product, Marketing, Sales, CS
-2. Define goals (pipeline $, MQLs, press coverage)
-3. Develop positioning and messaging
-4. Create sales enablement (deck, demo, battlecard)
-5. Build campaign assets (landing page, emails, ads)
-6. Train sales and CS teams
-7. Execute launch day (press, email, ads, outbound)
-8. Monitor and optimize for 30 days
-9. **Validation:** Pipeline on track to goal by week 2
-
-### Launch Day Checklist
-
-- [ ] Press release distributed
-- [ ] Email announcement sent
-- [ ] Social media posts live
-- [ ] Paid ads at full budget
-- [ ] Sales outbound blitz launched
-- [ ] In-app notification active
-- [ ] Metrics monitored every 2 hours
-
-### Launch Metrics
-
-| Metric | Leading (Daily) | Lagging (Weekly) |
-|--------|-----------------|------------------|
-| Traffic | Landing page visitors | - |
-| Engagement | Demo requests, signups | Feature adoption % |
-| Pipeline | MQLs generated | SQLs, pipeline $ |
-| Revenue | - | Deals closed, revenue |
-
----
-
-## Sales Enablement
-
-Equip sales team with PMM assets:
-
-1. Create sales deck (15-20 slides, visual-first)
-2. Build one-pagers (product, competitive, case study)
-3. Develop demo script (30-45 min with discovery)
-4. Write email templates (outreach, follow-up, closing)
-5. Create ROI calculator (input costs, output savings)
-6. Conduct monthly enablement calls
-7. Deliver quarterly training (positioning, competitive)
-8. **Validation:** Sales uses assets in 80%+ of opportunities
-
-### Sales Deck Structure
-
-| Slide | Content |
-|-------|---------|
-| 1-2 | Title, agenda |
-| 3-4 | Company intro, problem statement |
-| 5-7 | Solution, key benefits, demo |
-| 8-10 | Differentiation, case study, pricing |
-| 11-12 | Implementation, support, next steps |
-
-### Demo Flow
-
-```
-1. Intro (2 min): Who we are, agenda
-2. Discovery (5 min): Their needs, pain points
-3. Demo (20 min): Product focused on their use case
-4. Q&A (10 min): Objection handling
-5. Next steps (3 min): Trial, POC, proposal
-```
-
-### Sales-Marketing Handoff
-
-| Handoff | Frequency | Content |
-|---------|-----------|---------|
-| Weekly sync | 30 min | Win/loss, competitive, new assets |
-| Monthly enablement | 60 min | Product updates, training |
-| Quarterly review | Half-day | Results, strategy, planning |
-
----
-
-## International Expansion
-
-Enter new markets systematically:
-
-1. Validate market demand (inbound leads, TAM analysis)
-2. Localize website, pricing, legal
-3. Establish sales coverage (hire or agency)
-4. Adapt messaging for cultural fit
-5. Build local partnerships and references
-6. Launch localized campaigns
-7. Monitor CAC and conversion by market
-8. **Validation:** 3+ paying customers from market in first 90 days
-
-### Market Priority (Series A)
-
-| Market | Timeline | Budget % | Target ARR |
-|--------|----------|----------|------------|
-| US | Months 1-6 | 50% | $1M |
-| UK | Months 4-9 | 20% | $500k |
-| DACH | Months 7-12 | 15% | $300k |
-| France | Months 10-15 | 10% | $200k |
-| Canada | Months 7-12 | 5% | $100k |
-
-### Localization Checklist
-
-- [ ] Website translation (professional, not machine)
-- [ ] Currency and pricing localized
-- [ ] Local phone number and address
-- [ ] Legal compliance (GDPR, PIPEDA)
-- [ ] Local payment methods
-- [ ] Sales coverage during local hours
-- [ ] Local case studies and references
-
----
-
-## Reference Documentation
-
-### Positioning Frameworks
-
-`references/positioning-frameworks.md` contains:
-
-- April Dunford 5-step positioning process
-- Geoffrey Moore positioning statement template
-- Positioning validation interview protocol
-- Competitive positioning map construction
-
-### Launch Checklists
-
-`references/launch-checklists.md` contains:
-
-- Tier 1/2/3 launch checklists
-- Week-by-week launch timeline
-- Launch day runbook
-- Post-launch metrics dashboard
-
-### International GTM
-
-`references/international-gtm.md` contains:
-
-- US, UK, DACH, France, Canada playbooks
-- Market-specific channel mix and messaging
-- Localization requirements per market
-- Entry timeline and budget allocation
-
-### Messaging Templates
-
-`references/messaging-templates.md` contains:
-
-- Value proposition formulas
-- Persona-specific messaging
-- Competitive response scripts
-- Objection handling templates
-- Channel-specific copy (landing pages, emails, ads)
-
----
-
-## PMM KPIs
-
-| Metric | Target | Measurement |
-|--------|--------|-------------|
-| Product adoption | >40% in 90 days | Feature usage after launch |
-| Win rate | >30% competitive | Deals won vs. competitors |
-| Sales velocity | -20% YoY | Days from SQL to close |
-| Deal size | +25% YoY | Average contract value |
-| Launch pipeline | 3:1 ROMI | Pipeline $ : marketing spend |
-
----
-
-## Quick Reference
-
-### PMM Monthly Rhythm
-
-| Week | Focus |
-|------|-------|
-| 1 | Review metrics, update battlecards |
-| 2 | Create assets, publish content |
-| 3 | Support launches, optimize campaigns |
-| 4 | Monthly report, plan next month |
-
-## Proactive Triggers
-
-- **No documented positioning** → Without clear positioning, all marketing is guesswork.
-- **Messaging differs across channels** → Inconsistent story confuses buyers.
-- **No ICP defined** → Selling to everyone means selling to no one.
-- **Competitor repositioning** → Market shift detected. Review your positioning.
-
-## Output Artifacts
-
-| When you ask for... | You get... |
-|---------------------|------------|
-| "Position my product" | Positioning framework (April Dunford method) with output |
-| "GTM strategy" | Go-to-market plan with channels, messaging, and timeline |
-| "Competitive positioning" | Positioning map with competitive gaps and opportunities |
-
-## Communication
-
-All output passes quality verification:
-- Self-verify: source attribution, assumption audit, confidence scoring
-- Output format: Bottom Line → What (with confidence) → Why → How to Act
-- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.
-
-## Related Skills
-
-- **marketing-context**: For capturing foundational positioning. PMM builds on this.
-- **launch-strategy**: For executing product launches planned by PMM.
-- **competitive-intel** (C-Suite): For strategic competitive intelligence.
-- **cmo-advisor** (C-Suite): For marketing budget and growth model decisions.

package/templates/workspaces/olivia/skills/marketing-strategy-pmm/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn7f2gr00xy51fj1nx2y64ckjs800mhn",
-  "slug": "marketing-strategy-pmm",
-  "version": "2.1.1",
-  "publishedAt": 1773070262187
-}

package/templates/workspaces/olivia/skills/meta-ads-analytics/SKILL.md

@@ -1,53 +0,0 @@
----
-name: meta-ads-analytics
-description: Le campanhas, conjuntos, anuncios e criativos no Meta Ads para diagnostico, relatorios e recomendacoes operacionais usando somente o MCP brijr/meta-mcp.
-metadata: {"portable":"openclaw-ready","primary_mcp":"brijr/meta-mcp","scope":"analytics"}
-user-invocable: true
----
-
-# Purpose
-Esta skill faz leitura, analise e inteligencia operacional para Meta Ads. Ela diagnostica e estrutura relatorios sem confundir analise com execucao.
-
-# Use this skill when
-- o usuario pedir analise de performance
-- for preciso explicar queda, crescimento ou gargalo
-- for necessario gerar relatorio diario, semanal, executivo, tatico ou pos-teste
-- a tarefa exigir leitura por conta, campanha, conjunto, anuncio ou criativo
-
-# Do not use this skill when
-- a tarefa principal for criar ou editar estrutura
-- a prioridade for escalar ou reestruturar operacao sem antes diagnosticar
-
-# Operating principles
-- primeiro observar, depois concluir
-- separar `fato`, `hipotese` e `recomendacao`
-- localizar o nivel do problema antes de sugerir acao
-- reduzir confianca quando tracking, CRM ou pagina estiverem suspeitos
-- usar somente tools confirmadas do `brijr/meta-mcp`
-
-# Default workflow
-1. Confirmar objetivo de negocio e janela de analise.
-2. Ler performance por conta, campanha, conjunto, anuncio e criativo.
-3. Identificar o primeiro gargalo relevante no funil.
-4. Formular causas provaveis sem assumir causalidade cedo demais.
-5. Priorizar testes ou acoes recomendadas.
-6. Entregar resposta em `diagnostico + proximos passos`.
-
-# Preferred tools
-- `health_check`
-- `get_ad_accounts`
-- `get_campaigns`
-- `get_insights`
-- `compare_performance`
-- `export_insights`
-- `list_ad_sets`
-- `list_ads`
-- `list_ad_creatives`
-
-# References
-- {baseDir}/references/metrics-glossary.md
-- {baseDir}/references/diagnostic-frameworks.md
-- {baseDir}/references/report-templates.md
-- {baseDir}/references/funnel-analysis.md
-- {baseDir}/references/anomaly-playbooks.md
-- {baseDir}/references/official-meta-measurement-notes.md

package/templates/workspaces/olivia/skills/meta-ads-analytics/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn711ft9asct693qcyv1xx65p582w4s8",
-  "slug": "meta-ads-analytics",
-  "version": "1.0.0",
-  "publishedAt": 1773497005168
-}

package/templates/workspaces/olivia/skills/obsidian/SKILL.md

@@ -1,55 +0,0 @@
----
-name: obsidian
-description: Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
-homepage: https://help.obsidian.md
-metadata: {"clawdbot":{"emoji":"💎","requires":{"bins":["obsidian-cli"]},"install":[{"id":"brew","kind":"brew","formula":"yakitrak/yakitrak/obsidian-cli","bins":["obsidian-cli"],"label":"Install obsidian-cli (brew)"}]}}
----
-
-# Obsidian
-
-Obsidian vault = a normal folder on disk.
-
-Vault structure (typical)
-- Notes: `*.md` (plain text Markdown; edit with any editor)
-- Config: `.obsidian/` (workspace + plugin settings; usually don’t touch from scripts)
-- Canvases: `*.canvas` (JSON)
-- Attachments: whatever folder you chose in Obsidian settings (images/PDFs/etc.)
-
-## Find the active vault(s)
-
-Obsidian desktop tracks vaults here (source of truth):
-- `~/Library/Application Support/obsidian/obsidian.json`
-
-`obsidian-cli` resolves vaults from that file; vault name is typically the **folder name** (path suffix).
-
-Fast “what vault is active / where are the notes?”
-- If you’ve already set a default: `obsidian-cli print-default --path-only`
-- Otherwise, read `~/Library/Application Support/obsidian/obsidian.json` and use the vault entry with `"open": true`.
-
-Notes
-- Multiple vaults common (iCloud vs `~/Documents`, work/personal, etc.). Don’t guess; read config.
-- Avoid writing hardcoded vault paths into scripts; prefer reading the config or using `print-default`.
-
-## obsidian-cli quick start
-
-Pick a default vault (once):
-- `obsidian-cli set-default "<vault-folder-name>"`
-- `obsidian-cli print-default` / `obsidian-cli print-default --path-only`
-
-Search
-- `obsidian-cli search "query"` (note names)
-- `obsidian-cli search-content "query"` (inside notes; shows snippets + lines)
-
-Create
-- `obsidian-cli create "Folder/New note" --content "..." --open`
-- Requires Obsidian URI handler (`obsidian://…`) working (Obsidian installed).
-- Avoid creating notes under “hidden” dot-folders (e.g. `.something/...`) via URI; Obsidian may refuse.
-
-Move/rename (safe refactor)
-- `obsidian-cli move "old/path/note" "new/path/note"`
-- Updates `[[wikilinks]]` and common Markdown links across the vault (this is the main win vs `mv`).
-
-Delete
-- `obsidian-cli delete "path/note"`
-
-Prefer direct edits when appropriate: open the `.md` file and change it; Obsidian will pick it up.

package/templates/workspaces/olivia/skills/obsidian/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn70pywhg0fyz996kpa8xj89s57yhv26",
-  "slug": "obsidian",
-  "version": "1.0.0",
-  "publishedAt": 1767545362143
-}

package/templates/workspaces/olivia/skills/openclaw-accounting/SKILL.md

@@ -1,125 +0,0 @@
-Description
-
-A powerful local AI accounting assistant that helps you record daily income and expenses through natural language, query transactions, and generate statistical reports. All data is securely stored locally — no internet connection required.
-
-Capabilities
-
-1. Natural Language Accounting
-- Record income and expenses through conversation
-- Automatically detect amount, category, and date
-- Smart category suggestions
-
-2. Transaction Queries
-- Query by time range (today, this week, this month, this year, etc.)
-- Filter by category
-- Keyword search
-- Support for multi-condition combined filtering
-
-3. Statistical Analysis
-- Total income and expense summary
-- Category breakdown analysis
-- Daily average spending calculation
-- Balance auto-calculation
-
-4. Report Generation
-- Generate detailed income/expense reports
-- Category statistics TOP ranking
-- Export support
-
-Usage Examples
-
-Recording Transactions
-- "Record expense: lunch 35 yuan"
-- "Income: salary received 15000 yuan"
-- "Spent 120 on movie tickets, category entertainment"
-- "Transport today 20 yuan"
-
-Querying Transactions
-- "Show this month's transactions"
-- "How much did I spend this week"
-- "Query food and dining expenses"
-- "Show last month's income"
-
-Statistics
-- "Summarize this month's income and expenses"
-- "Spending overview for this year"
-- "Show my expense categories"
-
-Available Tools
-
-add_transaction
-Add a transaction record
-- type: expense or income
-- amount: amount
-- description: description
-- category: category (optional)
-- tags: tags (optional)
-
-query_transactions
-Query transaction records
-- period: time range
-- type: transaction type filter
-- category: category filter
-- keyword: keyword search
-- limit: result count limit
-
-get_statistics
-Get income/expense statistics
-- period: statistics time period
-
-generate_report
-Generate detailed report
-- period: report time period
-
-get_categories
-Get all available categories
-
-update_transaction
-Update a transaction record
-- id: record ID
-- other fields to update
-
-delete_transaction
-Delete a transaction record
-- id: record ID
-
-Category System
-
-Expense Categories
-- Food & Dining: meals, takeout, beverages, etc.
-- Transport: bus, subway, taxi, fuel, etc.
-- Shopping: supermarket, online shopping, daily necessities, etc.
-- Entertainment: movies, games, travel, etc.
-- Healthcare: doctor visits, medicine, checkups, etc.
-- Education: tuition, training, books, etc.
-- Housing: rent, mortgage, utilities, etc.
-- Utilities: phone bill, internet, etc.
-- Other
-
-Income Categories
-- Salary: monthly salary, annual salary, etc.
-- Bonus: year-end bonus, performance bonus, etc.
-- Investment: stocks, funds, wealth management, etc.
-- Freelance: side jobs, self-employment, etc.
-- Gift: monetary gifts, red envelopes, etc.
-- Reimbursement: expense reimbursement, refunds, etc.
-- Other
-
-Data Storage
-
-- All data saved in local JSON files
-- Path: configured data directory / accounting.json
-- Auto backup: retains the last 30 backups
-- Open data format, exportable at any time
-
-Quick Commands
-
-- /accounting.help - Show help
-- /accounting.stats - Quick view of this month's statistics
-
-Notes
-
-1. The data file is created automatically on first use
-2. Use positive numbers for amounts
-3. Edit/delete operations require the record ID (obtainable via query)
-4. Back up your data file regularly to prevent accidental loss

package/templates/workspaces/olivia/skills/openclaw-accounting/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn79scevzzwgbfj6j4yq9aq68x82783p",
-  "slug": "openclaw-accounting",
-  "version": "0.1.0",
-  "publishedAt": 1772528164871
-}

package/templates/workspaces/olivia/skills/openclaw-security-toolkit/CHANGELOG.md

@@ -1,35 +0,0 @@
-# Changelog
-
-All notable changes to this project will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-## [1.0.0] - 2026-03-11
-
-### Added
-- Initial release
-- Security audit module with comprehensive checks
-- Secret scanner with pattern detection (API keys, tokens, passwords)
-- Access control management (devices, users, channels)
-- Token management (status, rotation, validation)
-- Security report generation (JSON, Markdown, Table formats)
-- Auto-fix capabilities for supported issues
-- Internationalization support (English, Chinese)
-- Deep scan mode for thorough analysis
-- Security scoring system
-
-### Security
-- Detection for OpenAI API keys (`sk-*`)
-- Detection for Feishu app secrets
-- Detection for generic API keys and tokens
-- Detection for private keys
-- Gateway bind address check
-- Token strength validation
-- Public IP exposure check
-
-## [0.1.0] - 2026-03-10
-
-### Added
-- Project initialization
-- Basic design documentation