@robbiesrobotics/alice-agents 1.5.10 → 1.5.13

package/templates/workspaces/olivia/skills/analytics-tracking-2/SKILL.md

@@ -1,309 +0,0 @@
----
-name: analytics-tracking
-description: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.
-metadata:
-  version: 1.1.0
----
-
-# Analytics Tracking
-
-You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.
-
-## Initial Assessment
-
-**Check for product marketing context first:**
-If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
-
-Before implementing tracking, understand:
-
-1. **Business Context** - What decisions will this data inform? What are key conversions?
-2. **Current State** - What tracking exists? What tools are in use?
-3. **Technical Context** - What's the tech stack? Any privacy/compliance requirements?
-
----
-
-## Core Principles
-
-### 1. Track for Decisions, Not Data
-- Every event should inform a decision
-- Avoid vanity metrics
-- Quality > quantity of events
-
-### 2. Start with the Questions
-- What do you need to know?
-- What actions will you take based on this data?
-- Work backwards to what you need to track
-
-### 3. Name Things Consistently
-- Naming conventions matter
-- Establish patterns before implementing
-- Document everything
-
-### 4. Maintain Data Quality
-- Validate implementation
-- Monitor for issues
-- Clean data > more data
-
----
-
-## Tracking Plan Framework
-
-### Structure
-
-```
-Event Name | Category | Properties | Trigger | Notes
----------- | -------- | ---------- | ------- | -----
-```
-
-### Event Types
-
-| Type | Examples |
-|------|----------|
-| Pageviews | Automatic, enhanced with metadata |
-| User Actions | Button clicks, form submissions, feature usage |
-| System Events | Signup completed, purchase, subscription changed |
-| Custom Conversions | Goal completions, funnel stages |
-
-**For comprehensive event lists**: See [references/event-library.md](references/event-library.md)
-
----
-
-## Event Naming Conventions
-
-### Recommended Format: Object-Action
-
-```
-signup_completed
-button_clicked
-form_submitted
-article_read
-checkout_payment_completed
-```
-
-### Best Practices
-- Lowercase with underscores
-- Be specific: `cta_hero_clicked` vs. `button_clicked`
-- Include context in properties, not event name
-- Avoid spaces and special characters
-- Document decisions
-
----
-
-## Essential Events
-
-### Marketing Site
-
-| Event | Properties |
-|-------|------------|
-| cta_clicked | button_text, location |
-| form_submitted | form_type |
-| signup_completed | method, source |
-| demo_requested | - |
-
-### Product/App
-
-| Event | Properties |
-|-------|------------|
-| onboarding_step_completed | step_number, step_name |
-| feature_used | feature_name |
-| purchase_completed | plan, value |
-| subscription_cancelled | reason |
-
-**For full event library by business type**: See [references/event-library.md](references/event-library.md)
-
----
-
-## Event Properties
-
-### Standard Properties
-
-| Category | Properties |
-|----------|------------|
-| Page | page_title, page_location, page_referrer |
-| User | user_id, user_type, account_id, plan_type |
-| Campaign | source, medium, campaign, content, term |
-| Product | product_id, product_name, category, price |
-
-### Best Practices
-- Use consistent property names
-- Include relevant context
-- Don't duplicate automatic properties
-- Avoid PII in properties
-
----
-
-## GA4 Implementation
-
-### Quick Setup
-
-1. Create GA4 property and data stream
-2. Install gtag.js or GTM
-3. Enable enhanced measurement
-4. Configure custom events
-5. Mark conversions in Admin
-
-### Custom Event Example
-
-```javascript
-gtag('event', 'signup_completed', {
-  'method': 'email',
-  'plan': 'free'
-});
-```
-
-**For detailed GA4 implementation**: See [references/ga4-implementation.md](references/ga4-implementation.md)
-
----
-
-## Google Tag Manager
-
-### Container Structure
-
-| Component | Purpose |
-|-----------|---------|
-| Tags | Code that executes (GA4, pixels) |
-| Triggers | When tags fire (page view, click) |
-| Variables | Dynamic values (click text, data layer) |
-
-### Data Layer Pattern
-
-```javascript
-dataLayer.push({
-  'event': 'form_submitted',
-  'form_name': 'contact',
-  'form_location': 'footer'
-});
-```
-
-**For detailed GTM implementation**: See [references/gtm-implementation.md](references/gtm-implementation.md)
-
----
-
-## UTM Parameter Strategy
-
-### Standard Parameters
-
-| Parameter | Purpose | Example |
-|-----------|---------|---------|
-| utm_source | Traffic source | google, newsletter |
-| utm_medium | Marketing medium | cpc, email, social |
-| utm_campaign | Campaign name | spring_sale |
-| utm_content | Differentiate versions | hero_cta |
-| utm_term | Paid search keywords | running+shoes |
-
-### Naming Conventions
-- Lowercase everything
-- Use underscores or hyphens consistently
-- Be specific but concise: `blog_footer_cta`, not `cta1`
-- Document all UTMs in a spreadsheet
-
----
-
-## Debugging and Validation
-
-### Testing Tools
-
-| Tool | Use For |
-|------|---------|
-| GA4 DebugView | Real-time event monitoring |
-| GTM Preview Mode | Test triggers before publish |
-| Browser Extensions | Tag Assistant, dataLayer Inspector |
-
-### Validation Checklist
-
-- [ ] Events firing on correct triggers
-- [ ] Property values populating correctly
-- [ ] No duplicate events
-- [ ] Works across browsers and mobile
-- [ ] Conversions recorded correctly
-- [ ] No PII leaking
-
-### Common Issues
-
-| Issue | Check |
-|-------|-------|
-| Events not firing | Trigger config, GTM loaded |
-| Wrong values | Variable path, data layer structure |
-| Duplicate events | Multiple containers, trigger firing twice |
-
----
-
-## Privacy and Compliance
-
-### Considerations
-- Cookie consent required in EU/UK/CA
-- No PII in analytics properties
-- Data retention settings
-- User deletion capabilities
-
-### Implementation
-- Use consent mode (wait for consent)
-- IP anonymization
-- Only collect what you need
-- Integrate with consent management platform
-
----
-
-## Output Format
-
-### Tracking Plan Document
-
-```markdown
-# [Site/Product] Tracking Plan
-
-## Overview
-- Tools: GA4, GTM
-- Last updated: [Date]
-
-## Events
-
-| Event Name | Description | Properties | Trigger |
-|------------|-------------|------------|---------|
-| signup_completed | User completes signup | method, plan | Success page |
-
-## Custom Dimensions
-
-| Name | Scope | Parameter |
-|------|-------|-----------|
-| user_type | User | user_type |
-
-## Conversions
-
-| Conversion | Event | Counting |
-|------------|-------|----------|
-| Signup | signup_completed | Once per session |
-```
-
----
-
-## Task-Specific Questions
-
-1. What tools are you using (GA4, Mixpanel, etc.)?
-2. What key actions do you want to track?
-3. What decisions will this data inform?
-4. Who implements - dev team or marketing?
-5. Are there privacy/consent requirements?
-6. What's already tracked?
-
----
-
-## Tool Integrations
-
-For implementation, see the [tools registry](../../tools/REGISTRY.md). Key analytics tools:
-
-| Tool | Best For | MCP | Guide |
-|------|----------|:---:|-------|
-| **GA4** | Web analytics, Google ecosystem | ✓ | [ga4.md](../../tools/integrations/ga4.md) |
-| **Mixpanel** | Product analytics, event tracking | - | [mixpanel.md](../../tools/integrations/mixpanel.md) |
-| **Amplitude** | Product analytics, cohort analysis | - | [amplitude.md](../../tools/integrations/amplitude.md) |
-| **PostHog** | Open-source analytics, session replay | - | [posthog.md](../../tools/integrations/posthog.md) |
-| **Segment** | Customer data platform, routing | - | [segment.md](../../tools/integrations/segment.md) |
-
----
-
-## Related Skills
-
-- **ab-test-setup**: For experiment tracking
-- **seo-audit**: For organic traffic analysis
-- **page-cro**: For conversion optimization (uses this data)
-- **revops**: For pipeline metrics, CRM tracking, and revenue attribution

package/templates/workspaces/olivia/skills/analytics-tracking-2/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn78vnzara27r3yd7tmq0cykx580gxbk",
-  "slug": "analytics-tracking-2",
-  "version": "0.1.0",
-  "publishedAt": 1772687355491
-}

package/templates/workspaces/olivia/skills/api-doc-writer/SKILL.md

@@ -1,232 +0,0 @@
----
-name: api-doc-writer
-description: API接口文档助手。用于编写REST API文档、定义接口规范、生成接口说明。当需要编写API文档、接口规范时触发。
----
-
-# API接口文档助手
-
-## API文档模板
-
-```markdown
-# API接口文档
-
-版本：V1.0
-更新日期：YYYY-MM-DD
-维护人：XXX
-
----
-
-## 接口概览
-
-| 模块 | 接口数 | 负责人 |
-|------|--------|--------|
-| 用户模块 | 5 | @xxx |
-| 订单模块 | 8 | @xxx |
-| 支付模块 | 4 | @xxx |
-
----
-
-## 通用说明
-
-### 认证方式
-```
-Authorization: Bearer <token>
-```
-
-### 请求格式
-```
-Content-Type: application/json
-```
-
-### 响应格式
-```json
-{
-  "code": 0,
-  "message": "success",
-  "data": {}
-}
-```
-
-### 状态码
-| 状态码 | 说明 |
-|--------|------|
-| 0 | 成功 |
-| 1001 | 参数错误 |
-| 2001 | 未授权 |
-| 3001 | 资源不存在 |
-| 5001 | 服务器错误 |
-
----
-
-## 接口详情
-
-### 1. 用户接口
-
-#### 1.1 获取用户信息
-
-**接口地址**
-```
-GET /api/v1/users/{id}
-```
-
-**请求参数**
-| 参数名 | 类型 | 位置 | 必填 | 说明 |
-|--------|------|------|------|------|
-| id | long | path | 是 | 用户ID |
-
-**请求示例**
-```
-GET /api/v1/users/123
-```
-
-**响应示例**
-```json
-{
-  "code": 0,
-  "message": "success",
-  "data": {
-    "id": 123,
-    "name": "张三",
-    "email": "zhangsan@example.com",
-    "phone": "13800138000",
-    "created_at": "2024-01-01 10:00:00"
-  }
-}
-```
-
-**错误示例**
-```json
-{
-  "code": 3001,
-  "message": "用户不存在",
-  "data": null
-}
-```
-
----
-
-#### 1.2 创建用户
-
-**接口地址**
-```
-POST /api/v1/users
-```
-
-**请求参数**
-| 参数名 | 类型 | 必填 | 说明 |
-|--------|------|------|------|
-| name | string | 是 | 用户名 |
-| email | string | 是 | 邮箱 |
-| phone | string | 否 | 手机号 |
-| password | string | 是 | 密码 |
-
-**请求示例**
-```json
-{
-  "name": "张三",
-  "email": "zhangsan@example.com",
-  "phone": "13800138000",
-  "password": "123456"
-}
-```
-
-**响应示例**
-```json
-{
-  "code": 0,
-  "message": "success",
-  "data": {
-    "id": 123,
-    "name": "张三"
-  }
-}
-```
-
----
-
-### 2. 订单接口
-
-#### 2.1 订单列表
-
-**接口地址**
-```
-GET /api/v1/orders
-```
-
-**请求参数**
-| 参数名 | 类型 | 位置 | 必填 | 说明 |
-|--------|------|------|------|------|
-| page | int | query | 否 | 页码，默认1 |
-| page_size | int | query | 否 | 每页数量，默认20 |
-| status | string | query | 否 | 订单状态 |
-
-**请求示例**
-```
-GET /api/v1/orders?page=1&page_size=10&status=paid
-```
-
-**响应示例**
-```json
-{
-  "code": 0,
-  "message": "success",
-  "data": {
-    "total": 100,
-    "page": 1,
-    "page_size": 10,
-    "list": [
-      {
-        "id": "ORD202401010001",
-        "user_id": 123,
-        "amount": 100.00,
-        "status": "paid",
-        "created_at": "2024-01-01 10:00:00"
-      }
-    ]
-  }
-}
-```
-
----
-
-## 接口变更记录
-
-| 版本 | 日期 | 变更内容 | 变更人 |
-|------|------|----------|--------|
-| V1.0 | YYYY-MM-DD | 初始版本 | @xxx |
-| V1.1 | YYYY-MM-DD | 新增xxx接口 | @xxx |
-```
-
-## 接口设计原则
-
-### RESTful规范
-| 方法 | 用途 | 示例 |
-|------|------|------|
-| GET | 查询 | GET /users |
-| POST | 创建 | POST /users |
-| PUT | 完整更新 | PUT /users/1 |
-| PATCH | 部分更新 | PATCH /users/1 |
-| DELETE | 删除 | DELETE /users/1 |
-
-### URL命名规范
-```markdown
-- 使用名词复数：/users
-- 使用小写：/user-info
-- 使用连字符分隔：/order-details
-- 避免动词：不用 /getUser
-```
-
-### 状态码规范
-| 类别 | 状态码 | 说明 |
-|------|--------|------|
-| 1xx | 信息 | 接收的请求正在处理 |
-| 2xx | 成功 | 请求正常处理完毕 |
-| 3xx | 重定向 | 需要附加操作完成请求 |
-| 4xx | 客户端错误 | 请求有语法错误 |
-| 5xx | 服务器错误 | 服务器处理出错 |
-
-### 安全建议
-- 敏感信息加密传输
-- 身份验证Token过期机制
-- 接口调用频率限制
-- 参数校验过滤

package/templates/workspaces/olivia/skills/api-doc-writer/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn71h18yq7ayrcsa39r02ht4dd82pyc9",
-  "slug": "api-doc-writer",
-  "version": "1.0.1",
-  "publishedAt": 1774378972837
-}

package/templates/workspaces/olivia/skills/api-generator/SKILL.md

@@ -1,49 +0,0 @@
----
-version: "2.0.0"
-name: api-generator
-description: "API code generator. Generate RESTful endpoints, GraphQL schemas, OpenAPI/Swagger docs, API clients, mock servers, authentication, rate limiting."
-author: BytesAgain
-homepage: https://bytesagain.com
-source: https://github.com/bytesagain/ai-skills
----
-
-# ⚡ API Generator
-
-Generate production-ready API code scaffolds from zero. REST, GraphQL, auth, tests — all in one tool.
-
-## Usage
-
-```bash
-bash scripts/apigen.sh <command> <resource_name> [options]
-```
-
-## Commands
-
-### Core Generation
-- **rest** `<name>` — RESTful CRUD endpoints (Express.js)
-- **graphql** `<name>` — GraphQL Type + Query + Mutation schema
-- **swagger** `<name>` — OpenAPI 3.0 specification document
-
-### Utilities
-- **client** `<name>` — Python API client class
-- **mock** `<name>` — Mock API server with in-memory store
-- **auth** `<type>` — Auth code (`jwt` / `oauth` / `apikey`)
-- **rate-limit** `<type>` — Rate limiter (`token-bucket` / `sliding-window`)
-- **test** `<name>` — Jest + Supertest API test suite
-
-## Examples
-
-```bash
-bash scripts/apigen.sh rest user          # RESTful user endpoints
-bash scripts/apigen.sh graphql product    # GraphQL product schema
-bash scripts/apigen.sh auth jwt           # JWT authentication
-bash scripts/apigen.sh test order         # Order API tests
-```
-
-## Output
-
-All code prints to stdout. Copy or redirect into your project files.
-Generated code includes full comments and can serve as a project starting point.
----
-💬 Feedback & Feature Requests: https://bytesagain.com/feedback
-Powered by BytesAgain | bytesagain.com

package/templates/workspaces/olivia/skills/api-generator/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn799vbsx79g84ah3nyba7gj3982m6f1",
-  "slug": "api-generator",
-  "version": "2.0.0",
-  "publishedAt": 1773773744210
-}

package/templates/workspaces/olivia/skills/api-generator/tips.md

@@ -1,10 +0,0 @@
-# API Generator Tips
-
-1. **Swagger first, code second** — Define your API contract with `swagger` before writing `rest` code. Keeps docs and code in sync.
-2. **Mock-driven development** — Use `mock` to spin up a fake API so frontend can start work in parallel
-3. **Always add auth** — Every public-facing API needs authentication. `auth jwt` is the most common starting point
-4. **Rate-limit public APIs** — Prevent abuse with `rate-limit`. Token bucket fits most use cases
-5. **Test edge cases** — After generating tests with `test`, add boundary cases: empty values, overlong strings, concurrent requests
-6. **Centralize API calls** — Use `client` to generate a unified API layer. No more scattered fetch/axios calls
-7. **GraphQL for flexibility** — Use `graphql` schemas to let clients query only what they need, reducing data transfer
-8. **Version your specs** — Commit swagger docs to git. API changes should have a paper trail

package/templates/workspaces/olivia/skills/apple-notes/SKILL.md

@@ -1,50 +0,0 @@
----
-name: apple-notes
-description: Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks Clawdbot to add a note, list notes, search notes, or manage note folders.
-homepage: https://github.com/antoniorodr/memo
-metadata: {"clawdbot":{"emoji":"📝","os":["darwin"],"requires":{"bins":["memo"]},"install":[{"id":"brew","kind":"brew","formula":"antoniorodr/memo/memo","bins":["memo"],"label":"Install memo via Homebrew"}]}}
----
-
-# Apple Notes CLI
-
-Use `memo notes` to manage Apple Notes directly from the terminal. Create, view, edit, delete, search, move notes between folders, and export to HTML/Markdown.
-
-Setup
-- Install (Homebrew): `brew tap antoniorodr/memo && brew install antoniorodr/memo/memo`
-- Manual (pip): `pip install .` (after cloning the repo)
-- macOS-only; if prompted, grant Automation access to Notes.app.
-
-View Notes
-- List all notes: `memo notes`
-- Filter by folder: `memo notes -f "Folder Name"`
-- Search notes (fuzzy): `memo notes -s "query"`
-
-Create Notes
-- Add a new note: `memo notes -a`
-  - Opens an interactive editor to compose the note.
-- Quick add with title: `memo notes -a "Note Title"`
-
-Edit Notes
-- Edit existing note: `memo notes -e`
-  - Interactive selection of note to edit.
-
-Delete Notes
-- Delete a note: `memo notes -d`
-  - Interactive selection of note to delete.
-
-Move Notes
-- Move note to folder: `memo notes -m`
-  - Interactive selection of note and destination folder.
-
-Export Notes
-- Export to HTML/Markdown: `memo notes -ex`
-  - Exports selected note; uses Mistune for markdown processing.
-
-Limitations
-- Cannot edit notes containing images or attachments.
-- Interactive prompts may require terminal access.
-
-Notes
-- macOS-only.
-- Requires Apple Notes.app to be accessible.
-- For automation, grant permissions in System Settings > Privacy & Security > Automation.

package/templates/workspaces/olivia/skills/apple-notes/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn70pywhg0fyz996kpa8xj89s57yhv26",
-  "slug": "apple-notes",
-  "version": "1.0.0",
-  "publishedAt": 1767545294031
-}