cowork-os 0.3.21

package/resources/skills/eightctl.json

@@ -0,0 +1,10 @@
+{
+  "id": "eightctl",
+  "name": "Eightctl",
+  "description": "Control Eight Sleep pods (status, temperature, alarms, schedules).",
+  "icon": "🎛️",
+  "category": "Tools",
+  "prompt": "# eightctl\n\nUse `eightctl` for Eight Sleep pod control. Requires auth.\n\nAuth\n\n- Config: `~/.config/eightctl/config.yaml`\n- Env: `EIGHTCTL_EMAIL`, `EIGHTCTL_PASSWORD`\n\nQuick start\n\n- `eightctl status`\n- `eightctl on|off`\n- `eightctl temp 20`\n\nCommon tasks\n\n- Alarms: `eightctl alarm list|create|dismiss`\n- Schedules: `eightctl schedule list|create|update`\n- Audio: `eightctl audio state|play|pause`\n- Base: `eightctl base info|angle`\n\nNotes\n\n- API is unofficial and rate-limited; avoid repeated logins.\n- Confirm before changing temperature or alarms.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/explain-code.json

@@ -0,0 +1,29 @@
+{
+  "id": "explain-code",
+  "name": "Explain Code",
+  "description": "Get a detailed explanation of how code works",
+  "icon": "📖",
+  "category": "Learning",
+  "prompt": "Please explain the code in {{path}} in detail.\n\nInclude:\n- What the code does at a high level\n- How it works step by step\n- Key concepts and patterns used\n- Any complex or tricky parts\n- How it fits into the larger system (if applicable)\n\nExplain at a {{level}} level.",
+  "parameters": [
+    {
+      "name": "path",
+      "type": "string",
+      "description": "Path to the file to explain",
+      "required": true
+    },
+    {
+      "name": "level",
+      "type": "select",
+      "description": "Explanation depth",
+      "required": true,
+      "default": "intermediate",
+      "options": [
+        "beginner",
+        "intermediate",
+        "advanced"
+      ]
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/extract-todos.json

@@ -0,0 +1,18 @@
+{
+  "id": "extract-todos",
+  "name": "Extract TODOs",
+  "description": "Find all TODO/FIXME comments in codebase",
+  "icon": "📌",
+  "category": "Utilities",
+  "prompt": "Please find all TODO, FIXME, HACK, and XXX comments in the codebase.\n\nSearch in {{path}} and provide:\n1. **Summary**: Total count by type\n2. **By File**: Group findings by file\n3. **By Priority**: If priority markers exist (e.g., TODO(high))\n4. **Old TODOs**: Identify TODOs that might be stale\n\nFor each TODO:\n- File path and line number\n- The full comment text\n- Surrounding context if helpful\n\nSuggest which TODOs should be prioritized based on:\n- Security implications\n- Bug-related issues\n- Technical debt impact",
+  "parameters": [
+    {
+      "name": "path",
+      "type": "string",
+      "description": "Path to search",
+      "required": true,
+      "default": "."
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/food-order.json

@@ -0,0 +1,10 @@
+{
+  "id": "food-order",
+  "name": "Food-order",
+  "description": "Reorder Foodora orders + track ETA/status with ordercli. Never confirm without explicit user approval. Triggers: order food, reorder, track ETA.",
+  "icon": "🥡",
+  "category": "Tools",
+  "prompt": "# Food order (Foodora via ordercli)\n\nGoal: reorder a previous Foodora order safely (preview first; confirm only on explicit user “yes/confirm/place the order”).\n\nHard safety rules\n\n- Never run `ordercli foodora reorder ... --confirm` unless user explicitly confirms placing the order.\n- Prefer preview-only steps first; show what will happen; ask for confirmation.\n- If user is unsure: stop at preview and ask questions.\n\nSetup (once)\n\n- Country: `ordercli foodora countries` → `ordercli foodora config set --country AT`\n- Login (password): `ordercli foodora login --email you@example.com --password-stdin`\n- Login (no password, preferred): `ordercli foodora session chrome --url https://www.foodora.at/ --profile \"Default\"`\n\nFind what to reorder\n\n- Recent list: `ordercli foodora history --limit 10`\n- Details: `ordercli foodora history show <orderCode>`\n- If needed (machine-readable): `ordercli foodora history show <orderCode> --json`\n\nPreview reorder (no cart changes)\n\n- `ordercli foodora reorder <orderCode>`\n\nPlace reorder (cart change; explicit confirmation required)\n\n- Confirm first, then run: `ordercli foodora reorder <orderCode> --confirm`\n- Multiple addresses? Ask user for the right `--address-id` (take from their Foodora account / prior order data) and run:\n  - `ordercli foodora reorder <orderCode> --confirm --address-id <id>`\n\nTrack the order\n\n- ETA/status (active list): `ordercli foodora orders`\n- Live updates: `ordercli foodora orders --watch`\n- Single order detail: `ordercli foodora order <orderCode>`\n\nDebug / safe testing\n\n- Use a throwaway config: `ordercli --config /tmp/ordercli.json ...`",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/gemini.json

@@ -0,0 +1,10 @@
+{
+  "id": "gemini",
+  "name": "Gemini",
+  "description": "Gemini CLI for one-shot Q&A, summaries, and generation.",
+  "icon": "♊️",
+  "category": "Tools",
+  "prompt": "# Gemini CLI\n\nUse Gemini in one-shot mode with a positional prompt (avoid interactive mode).\n\nQuick start\n\n- `gemini \"Answer this question...\"`\n- `gemini --model <name> \"Prompt...\"`\n- `gemini --output-format json \"Return JSON\"`\n\nExtensions\n\n- List: `gemini --list-extensions`\n- Manage: `gemini extensions <command>`\n\nNotes\n\n- If auth is required, run `gemini` once interactively and follow the login flow.\n- Avoid `--yolo` for safety.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/generate-readme.json

@@ -0,0 +1,10 @@
+{
+  "id": "generate-readme",
+  "name": "Generate README",
+  "description": "Create a README.md for a project",
+  "icon": "📄",
+  "category": "Project",
+  "prompt": "Please analyze this project and generate a comprehensive README.md.\n\nInclude:\n- Project title and description\n- Features list\n- Installation instructions\n- Usage examples\n- Configuration options\n- API documentation (if applicable)\n- Contributing guidelines\n- License information\n\nAnalyze the codebase to understand:\n- What the project does\n- How to install dependencies\n- How to run/build the project\n- Key configuration files\n\nSave the README.md in the project root.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/gifgrep.json

@@ -0,0 +1,10 @@
+{
+  "id": "gifgrep",
+  "name": "Gifgrep",
+  "description": "Search GIF providers with CLI/TUI, download results, and extract stills/sheets.",
+  "icon": "🧲",
+  "category": "Tools",
+  "prompt": "# gifgrep\n\nUse `gifgrep` to search GIF providers (Tenor/Giphy), browse in a TUI, download results, and extract stills or sheets.\n\nGIF-Grab (gifgrep workflow)\n\n- Search → preview → download → extract (still/sheet) for fast review and sharing.\n\nQuick start\n\n- `gifgrep cats --max 5`\n- `gifgrep cats --format url | head -n 5`\n- `gifgrep search --json cats | jq '.[0].url'`\n- `gifgrep tui \"office handshake\"`\n- `gifgrep cats --download --max 1 --format url`\n\nTUI + previews\n\n- TUI: `gifgrep tui \"query\"`\n- CLI still previews: `--thumbs` (Kitty/Ghostty only; still frame)\n\nDownload + reveal\n\n- `--download` saves to `~/Downloads`\n- `--reveal` shows the last download in Finder\n\nStills + sheets\n\n- `gifgrep still ./clip.gif --at 1.5s -o still.png`\n- `gifgrep sheet ./clip.gif --frames 9 --cols 3 -o sheet.png`\n- Sheets = single PNG grid of sampled frames (great for quick review, docs, PRs, chat).\n- Tune: `--frames` (count), `--cols` (grid width), `--padding` (spacing).\n\nProviders\n\n- `--source auto|tenor|giphy`\n- `GIPHY_API_KEY` required for `--source giphy`\n- `TENOR_API_KEY` optional (Tenor demo key used if unset)\n\nOutput\n\n- `--json` prints an array of results (`id`, `title`, `url`, `preview_url`, `tags`, `width`, `height`)\n- `--format` for pipe-friendly fields (e.g., `url`)\n\nEnvironment tweaks\n\n- `GIFGREP_SOFTWARE_ANIM=1` to force software animation\n- `GIFGREP_CELL_ASPECT=0.5` to tweak preview geometry",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/git-commit.json

@@ -0,0 +1,10 @@
+{
+  "id": "git-commit",
+  "name": "Git Commit",
+  "description": "Create a well-formatted commit message from staged changes",
+  "icon": "📝",
+  "category": "Development",
+  "prompt": "Please analyze the staged git changes and create a well-formatted commit message.\n\nSteps:\n1. Run `git diff --staged` to see the changes\n2. Analyze what was changed and why\n3. Create a commit message following conventional commits format:\n   - type(scope): description\n   - Types: feat, fix, docs, style, refactor, test, chore\n4. Include a brief body if the changes are complex\n5. Run `git commit -m \"message\"` with the generated message\n\nMake the commit message clear, concise, and descriptive.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/github.json

@@ -0,0 +1,10 @@
+{
+  "id": "github",
+  "name": "Github",
+  "description": "Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.",
+  "icon": "🐙",
+  "category": "Tools",
+  "prompt": "# GitHub Skill\n\nUse the `gh` CLI to interact with GitHub. Always specify `--repo owner/repo` when not in a git directory, or use URLs directly.\n\n## Pull Requests\n\nCheck CI status on a PR:\n\n```bash\ngh pr checks 55 --repo owner/repo\n```\n\nList recent workflow runs:\n\n```bash\ngh run list --repo owner/repo --limit 10\n```\n\nView a run and see which steps failed:\n\n```bash\ngh run view <run-id> --repo owner/repo\n```\n\nView logs for failed steps only:\n\n```bash\ngh run view <run-id> --repo owner/repo --log-failed\n```\n\n## API for Advanced Queries\n\nThe `gh api` command is useful for accessing data not available through other subcommands.\n\nGet PR with specific fields:\n\n```bash\ngh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'\n```\n\n## JSON Output\n\nMost commands support `--json` for structured output. You can use `--jq` to filter:\n\n```bash\ngh issue list --repo owner/repo --json number,title --jq '.[] | \"\\(.number): \\(.title)\"'\n```",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/gog.json

@@ -0,0 +1,10 @@
+{
+  "id": "gog",
+  "name": "Gog",
+  "description": "Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.",
+  "icon": "🎮",
+  "category": "Tools",
+  "prompt": "# gog\n\nUse `gog` for Gmail/Calendar/Drive/Contacts/Sheets/Docs. Requires OAuth setup.\n\nSetup (once)\n\n- `gog auth credentials /path/to/client_secret.json`\n- `gog auth add you@gmail.com --services gmail,calendar,drive,contacts,docs,sheets`\n- `gog auth list`\n\nCommon commands\n\n- Gmail search: `gog gmail search 'newer_than:7d' --max 10`\n- Gmail messages search (per email, ignores threading): `gog gmail messages search \"in:inbox from:ryanair.com\" --max 20 --account you@example.com`\n- Gmail send (plain): `gog gmail send --to a@b.com --subject \"Hi\" --body \"Hello\"`\n- Gmail send (multi-line): `gog gmail send --to a@b.com --subject \"Hi\" --body-file ./message.txt`\n- Gmail send (stdin): `gog gmail send --to a@b.com --subject \"Hi\" --body-file -`\n- Gmail send (HTML): `gog gmail send --to a@b.com --subject \"Hi\" --body-html \"<p>Hello</p>\"`\n- Gmail draft: `gog gmail drafts create --to a@b.com --subject \"Hi\" --body-file ./message.txt`\n- Gmail send draft: `gog gmail drafts send <draftId>`\n- Gmail reply: `gog gmail send --to a@b.com --subject \"Re: Hi\" --body \"Reply\" --reply-to-message-id <msgId>`\n- Calendar list events: `gog calendar events <calendarId> --from <iso> --to <iso>`\n- Calendar create event: `gog calendar create <calendarId> --summary \"Title\" --from <iso> --to <iso>`\n- Calendar create with color: `gog calendar create <calendarId> --summary \"Title\" --from <iso> --to <iso> --event-color 7`\n- Calendar update event: `gog calendar update <calendarId> <eventId> --summary \"New Title\" --event-color 4`\n- Calendar show colors: `gog calendar colors`\n- Drive search: `gog drive search \"query\" --max 10`\n- Contacts: `gog contacts list --max 20`\n- Sheets get: `gog sheets get <sheetId> \"Tab!A1:D10\" --json`\n- Sheets update: `gog sheets update <sheetId> \"Tab!A1:B2\" --values-json '[[\"A\",\"B\"],[\"1\",\"2\"]]' --input USER_ENTERED`\n- Sheets append: `gog sheets append <sheetId> \"Tab!A:C\" --values-json '[[\"x\",\"y\",\"z\"]]' --insert INSERT_ROWS`\n- Sheets clear: `gog sheets clear <sheetId> \"Tab!A2:Z\"`\n- Sheets metadata: `gog sheets metadata <sheetId> --json`\n- Docs export: `gog docs export <docId> --format txt --out /tmp/doc.txt`\n- Docs cat: `gog docs cat <docId>`\n\nCalendar Colors\n\n- Use `gog calendar colors` to see all available event colors (IDs 1-11)\n- Add colors to events with `--event-color <id>` flag\n- Event color IDs (from `gog calendar colors` output):\n  - 1: #a4bdfc\n  - 2: #7ae7bf\n  - 3: #dbadff\n  - 4: #ff887c\n  - 5: #fbd75b\n  - 6: #ffb878\n  - 7: #46d6db\n  - 8: #e1e1e1\n  - 9: #5484ed\n  - 10: #51b749\n  - 11: #dc2127\n\nEmail Formatting\n\n- Prefer plain text. Use `--body-file` for multi-paragraph messages (or `--body-file -` for stdin).\n- Same `--body-file` pattern works for drafts and replies.\n- `--body` does not unescape `\\n`. If you need inline newlines, use a heredoc or `$'Line 1\\n\\nLine 2'`.\n- Use `--body-html` only when you need rich formatting.\n- HTML tags: `<p>` for paragraphs, `<br>` for line breaks, `<strong>` for bold, `<em>` for italic, `<a href=\"url\">` for links, `<ul>`/`<li>` for lists.\n- Example (plain text via stdin):\n\n  ```bash\n  gog gmail send --to recipient@example.com \\\n    --subject \"Meeting Follow-up\" \\\n    --body-file - <<'EOF'\n  Hi Name,\n\n  Thanks for meeting today. Next steps:\n  - Item one\n  - Item two\n\n  Best regards,\n  Your Name\n  EOF\n  ```\n\n- Example (HTML list):\n  ```bash\n  gog gmail send --to recipient@example.com \\\n    --subject \"Meeting Follow-up\" \\\n    --body-html \"<p>Hi Name,</p><p>Thanks for meeting today. Here are the next steps:</p><ul><li>Item one</li><li>Item two</li></ul><p>Best regards,<br>Your Name</p>\"\n  ```\n\nNotes\n\n- Set `GOG_ACCOUNT=you@gmail.com` to avoid repeating `--account`.\n- For scripting, prefer `--json` plus `--no-input`.\n- Sheets values can be passed via `--values-json` (recommended) or as inline rows.\n- Docs supports export/cat/copy. In-place edits require a Docs API client (not in gog).\n- Confirm before sending mail or creating events.\n- `gog gmail search` returns one row per thread; use `gog gmail messages search` when you need every individual email returned separately.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/goplaces.json

@@ -0,0 +1,10 @@
+{
+  "id": "goplaces",
+  "name": "Goplaces",
+  "description": "Query Google Places API (New) via the goplaces CLI for text search, place details, resolve, and reviews. Use for human-friendly place lookup or JSON output for scripts.",
+  "icon": "📍",
+  "category": "Tools",
+  "prompt": "# goplaces\n\nModern Google Places API (New) CLI. Human output by default, `--json` for scripts.\n\nInstall\n\n- Homebrew: `brew install steipete/tap/goplaces`\n\nConfig\n\n- `GOOGLE_PLACES_API_KEY` required.\n- Optional: `GOOGLE_PLACES_BASE_URL` for testing/proxying.\n\nCommon commands\n\n- Search: `goplaces search \"coffee\" --open-now --min-rating 4 --limit 5`\n- Bias: `goplaces search \"pizza\" --lat 40.8 --lng -73.9 --radius-m 3000`\n- Pagination: `goplaces search \"pizza\" --page-token \"NEXT_PAGE_TOKEN\"`\n- Resolve: `goplaces resolve \"Soho, London\" --limit 5`\n- Details: `goplaces details <place_id> --reviews`\n- JSON: `goplaces search \"sushi\" --json`\n\nNotes\n\n- `--no-color` or `NO_COLOR` disables ANSI color.\n- Price levels: 0..4 (free → very expensive).\n- Type filter sends only the first `--type` value (API accepts one).",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/himalaya.json

@@ -0,0 +1,10 @@
+{
+  "id": "himalaya",
+  "name": "Himalaya",
+  "description": "CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).",
+  "icon": "📧",
+  "category": "Tools",
+  "prompt": "# Himalaya Email CLI\n\nHimalaya is a CLI email client that lets you manage emails from the terminal using IMAP, SMTP, Notmuch, or Sendmail backends.\n\n## References\n\n- `references/configuration.md` (config file setup + IMAP/SMTP authentication)\n- `references/message-composition.md` (MML syntax for composing emails)\n\n## Prerequisites\n\n1. Himalaya CLI installed (`himalaya --version` to verify)\n2. A configuration file at `~/.config/himalaya/config.toml`\n3. IMAP/SMTP credentials configured (password stored securely)\n\n## Configuration Setup\n\nRun the interactive wizard to set up an account:\n\n```bash\nhimalaya account configure\n```\n\nOr create `~/.config/himalaya/config.toml` manually:\n\n```toml\n[accounts.personal]\nemail = \"you@example.com\"\ndisplay-name = \"Your Name\"\ndefault = true\n\nbackend.type = \"imap\"\nbackend.host = \"imap.example.com\"\nbackend.port = 993\nbackend.encryption.type = \"tls\"\nbackend.login = \"you@example.com\"\nbackend.auth.type = \"password\"\nbackend.auth.cmd = \"pass show email/imap\"  # or use keyring\n\nmessage.send.backend.type = \"smtp\"\nmessage.send.backend.host = \"smtp.example.com\"\nmessage.send.backend.port = 587\nmessage.send.backend.encryption.type = \"start-tls\"\nmessage.send.backend.login = \"you@example.com\"\nmessage.send.backend.auth.type = \"password\"\nmessage.send.backend.auth.cmd = \"pass show email/smtp\"\n```\n\n## Common Operations\n\n### List Folders\n\n```bash\nhimalaya folder list\n```\n\n### List Emails\n\nList emails in INBOX (default):\n\n```bash\nhimalaya envelope list\n```\n\nList emails in a specific folder:\n\n```bash\nhimalaya envelope list --folder \"Sent\"\n```\n\nList with pagination:\n\n```bash\nhimalaya envelope list --page 1 --page-size 20\n```\n\n### Search Emails\n\n```bash\nhimalaya envelope list from john@example.com subject meeting\n```\n\n### Read an Email\n\nRead email by ID (shows plain text):\n\n```bash\nhimalaya message read 42\n```\n\nExport raw MIME:\n\n```bash\nhimalaya message export 42 --full\n```\n\n### Reply to an Email\n\nInteractive reply (opens $EDITOR):\n\n```bash\nhimalaya message reply 42\n```\n\nReply-all:\n\n```bash\nhimalaya message reply 42 --all\n```\n\n### Forward an Email\n\n```bash\nhimalaya message forward 42\n```\n\n### Write a New Email\n\nInteractive compose (opens $EDITOR):\n\n```bash\nhimalaya message write\n```\n\nSend directly using template:\n\n```bash\ncat << 'EOF' | himalaya template send\nFrom: you@example.com\nTo: recipient@example.com\nSubject: Test Message\n\nHello from Himalaya!\nEOF\n```\n\nOr with headers flag:\n\n```bash\nhimalaya message write -H \"To:recipient@example.com\" -H \"Subject:Test\" \"Message body here\"\n```\n\n### Move/Copy Emails\n\nMove to folder:\n\n```bash\nhimalaya message move 42 \"Archive\"\n```\n\nCopy to folder:\n\n```bash\nhimalaya message copy 42 \"Important\"\n```\n\n### Delete an Email\n\n```bash\nhimalaya message delete 42\n```\n\n### Manage Flags\n\nAdd flag:\n\n```bash\nhimalaya flag add 42 --flag seen\n```\n\nRemove flag:\n\n```bash\nhimalaya flag remove 42 --flag seen\n```\n\n## Multiple Accounts\n\nList accounts:\n\n```bash\nhimalaya account list\n```\n\nUse a specific account:\n\n```bash\nhimalaya --account work envelope list\n```\n\n## Attachments\n\nSave attachments from a message:\n\n```bash\nhimalaya attachment download 42\n```\n\nSave to specific directory:\n\n```bash\nhimalaya attachment download 42 --dir ~/Downloads\n```\n\n## Output Formats\n\nMost commands support `--output` for structured output:\n\n```bash\nhimalaya envelope list --output json\nhimalaya envelope list --output plain\n```\n\n## Debugging\n\nEnable debug logging:\n\n```bash\nRUST_LOG=debug himalaya envelope list\n```\n\nFull trace with backtrace:\n\n```bash\nRUST_LOG=trace RUST_BACKTRACE=1 himalaya envelope list\n```\n\n## Tips\n\n- Use `himalaya --help` or `himalaya <command> --help` for detailed usage.\n- Message IDs are relative to the current folder; re-list after folder changes.\n- For composing rich emails with attachments, use MML syntax (see `references/message-composition.md`).\n- Store passwords securely using `pass`, system keyring, or a command that outputs the password.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/imsg.json

@@ -0,0 +1,10 @@
+{
+  "id": "imsg",
+  "name": "Imsg",
+  "description": "iMessage/SMS CLI for listing chats, history, watch, and sending.",
+  "icon": "📨",
+  "category": "Tools",
+  "prompt": "# imsg\n\nUse `imsg` to read and send Messages.app iMessage/SMS on macOS.\n\nRequirements\n\n- Messages.app signed in\n- Full Disk Access for your terminal\n- Automation permission to control Messages.app (for sending)\n\nCommon commands\n\n- List chats: `imsg chats --limit 10 --json`\n- History: `imsg history --chat-id 1 --limit 20 --attachments --json`\n- Watch: `imsg watch --chat-id 1 --attachments`\n- Send: `imsg send --to \"+14155551212\" --text \"hi\" --file /path/pic.jpg`\n\nNotes\n\n- `--service imessage|sms|auto` controls delivery.\n- Confirm recipient + message before sending.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/karpathy-guidelines.json

@@ -0,0 +1,12 @@
+{
+  "id": "karpathy-guidelines",
+  "name": "Task Guidelines",
+  "description": "Best practices for high-quality task execution",
+  "icon": "🧠",
+  "category": "Guidelines",
+  "type": "guideline",
+  "priority": 1,
+  "prompt": "## Task Guidelines\n\n**1. Think Before Acting**\n- State assumptions explicitly. If uncertain, ask.\n- If multiple interpretations exist, present them - don't pick silently.\n- If a simpler approach exists, say so. Push back when warranted.\n- If something is unclear, stop. Name what's confusing. Ask.\n\n**2. Simplicity First**\n- Do only what was asked - no extra features or \"improvements\".\n- Keep outputs focused and minimal.\n- Don't add unnecessary complexity or options.\n- If the task can be done simply, do it simply.\n\n**3. Focused Changes**\n- Only modify what's directly relevant to the task.\n- Don't reorganize, rename, or \"improve\" unrelated things.\n- Match existing patterns and conventions.\n- If you notice unrelated issues, mention them - don't fix them unsolicited.\n\n**4. Goal-Driven Execution**\n- Transform tasks into verifiable goals.\n- For multi-step tasks, state a brief plan with verification steps.\n- Loop until success criteria are met.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/last30days.json

@@ -0,0 +1,26 @@
+{
+  "id": "last30days",
+  "name": "Last 30 Days",
+  "description": "Research topics across Reddit and X from the past month to generate working prompts",
+  "icon": "🔬",
+  "category": "Research",
+  "priority": 1,
+  "prompt": "Research \"{{topic}}\" across Reddit and X from the past 30 days.\n\nIMPORTANT: Use the EXACT search term \"{{topic}}\" as provided. Do NOT interpret, correct, or modify the search term in any way.\n\nGoal: Find real community discussions, patterns, and best practices to generate copy-paste-ready prompts that actually work.\n\nSteps:\n1. Search Reddit and X for discussions about \"{{topic}}\" (use this exact term) from the last 30 days\n2. Analyze engagement metrics (upvotes, likes, retweets) to identify what resonates\n3. Extract patterns and techniques that users report as effective\n4. Synthesize findings into actionable, domain-specific prompts\n\nTarget tool: {{tool}}\n\nOutput:\n- Summary of key findings from community discussions\n- 3-5 ready-to-use prompts based on what's working\n- Tips and techniques discovered from real users\n- Links to notable discussions for reference",
+  "parameters": [
+    {
+      "name": "topic",
+      "type": "string",
+      "description": "The topic to research (e.g., 'prompting techniques', 'iOS app mockups', 'animation effects')",
+      "required": true
+    },
+    {
+      "name": "tool",
+      "type": "select",
+      "description": "Target AI tool for the prompts",
+      "required": false,
+      "default": "Any",
+      "options": ["Any", "ChatGPT", "Claude", "Midjourney", "DALL-E", "Stable Diffusion", "Cursor", "Claude Code"]
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/local-places.json

@@ -0,0 +1,10 @@
+{
+  "id": "local-places",
+  "name": "Local-places",
+  "description": "Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.",
+  "icon": "📍",
+  "category": "Tools",
+  "prompt": "# 📍 Local Places\n\n_Find places, Go fast_\n\nSearch for nearby places using a local Google Places API proxy. Two-step flow: resolve location first, then search.\n\n## Setup\n\n```bash\ncd {baseDir}\necho \"GOOGLE_PLACES_API_KEY=your-key\" > .env\nuv venv && uv pip install -e \".[dev]\"\nuv run --env-file .env uvicorn local_places.main:app --host 127.0.0.1 --port 8000\n```\n\nRequires `GOOGLE_PLACES_API_KEY` in `.env` or environment.\n\n## Quick Start\n\n1. **Check server:** `curl http://127.0.0.1:8000/ping`\n\n2. **Resolve location:**\n\n```bash\ncurl -X POST http://127.0.0.1:8000/locations/resolve \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"location_text\": \"Soho, London\", \"limit\": 5}'\n```\n\n3. **Search places:**\n\n```bash\ncurl -X POST http://127.0.0.1:8000/places/search \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\n    \"query\": \"coffee shop\",\n    \"location_bias\": {\"lat\": 51.5137, \"lng\": -0.1366, \"radius_m\": 1000},\n    \"filters\": {\"open_now\": true, \"min_rating\": 4.0},\n    \"limit\": 10\n  }'\n```\n\n4. **Get details:**\n\n```bash\ncurl http://127.0.0.1:8000/places/{place_id}\n```\n\n## Conversation Flow\n\n1. If user says \"near me\" or gives vague location → resolve it first\n2. If multiple results → show numbered list, ask user to pick\n3. Ask for preferences: type, open now, rating, price level\n4. Search with `location_bias` from chosen location\n5. Present results with name, rating, address, open status\n6. Offer to fetch details or refine search\n\n## Filter Constraints\n\n- `filters.types`: exactly ONE type (e.g., \"restaurant\", \"cafe\", \"gym\")\n- `filters.price_levels`: integers 0-4 (0=free, 4=very expensive)\n- `filters.min_rating`: 0-5 in 0.5 increments\n- `filters.open_now`: boolean\n- `limit`: 1-20 for search, 1-10 for resolve\n- `location_bias.radius_m`: must be > 0\n\n## Response Format\n\n```json\n{\n  \"results\": [\n    {\n      \"place_id\": \"ChIJ...\",\n      \"name\": \"Coffee Shop\",\n      \"address\": \"123 Main St\",\n      \"location\": { \"lat\": 51.5, \"lng\": -0.1 },\n      \"rating\": 4.6,\n      \"price_level\": 2,\n      \"types\": [\"cafe\", \"food\"],\n      \"open_now\": true\n    }\n  ],\n  \"next_page_token\": \"...\"\n}\n```\n\nUse `next_page_token` as `page_token` in next request for more results.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/mcporter.json

@@ -0,0 +1,10 @@
+{
+  "id": "mcporter",
+  "name": "Mcporter",
+  "description": "Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.",
+  "icon": "📦",
+  "category": "Tools",
+  "prompt": "# mcporter\n\nUse `mcporter` to work with MCP servers directly.\n\nQuick start\n\n- `mcporter list`\n- `mcporter list <server> --schema`\n- `mcporter call <server.tool> key=value`\n\nCall tools\n\n- Selector: `mcporter call linear.list_issues team=ENG limit:5`\n- Function syntax: `mcporter call \"linear.create_issue(title: \\\"Bug\\\")\"`\n- Full URL: `mcporter call https://api.example.com/mcp.fetch url:https://example.com`\n- Stdio: `mcporter call --stdio \"bun run ./server.ts\" scrape url=https://example.com`\n- JSON payload: `mcporter call <server.tool> --args '{\"limit\":5}'`\n\nAuth + config\n\n- OAuth: `mcporter auth <server | url> [--reset]`\n- Config: `mcporter config list|get|add|remove|import|login|logout`\n\nDaemon\n\n- `mcporter daemon start|status|stop|restart`\n\nCodegen\n\n- CLI: `mcporter generate-cli --server <name>` or `--command <url>`\n- Inspect: `mcporter inspect-cli <path> [--json]`\n- TS: `mcporter emit-ts <server> --mode client|types`\n\nNotes\n\n- Config default: `./config/mcporter.json` (override with `--config`).\n- Prefer `--output json` for machine-readable results.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/model-usage.json

@@ -0,0 +1,10 @@
+{
+  "id": "model-usage",
+  "name": "Model-usage",
+  "description": "Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.",
+  "icon": "📊",
+  "category": "Tools",
+  "prompt": "# Model usage\n\n## Overview\n\nGet per-model usage cost from CodexBar's local cost logs. Supports \"current model\" (most recent daily entry) or \"all models\" summaries for Codex or Claude.\n\nTODO: add Linux CLI support guidance once CodexBar CLI install path is documented for Linux.\n\n## Quick start\n\n1. Fetch cost JSON via CodexBar CLI or pass a JSON file.\n2. Use the bundled script to summarize by model.\n\n```bash\npython {baseDir}/scripts/model_usage.py --provider codex --mode current\npython {baseDir}/scripts/model_usage.py --provider codex --mode all\npython {baseDir}/scripts/model_usage.py --provider claude --mode all --format json --pretty\n```\n\n## Current model logic\n\n- Uses the most recent daily row with `modelBreakdowns`.\n- Picks the model with the highest cost in that row.\n- Falls back to the last entry in `modelsUsed` when breakdowns are missing.\n- Override with `--model <name>` when you need a specific model.\n\n## Inputs\n\n- Default: runs `codexbar cost --format json --provider <codex|claude>`.\n- File or stdin:\n\n```bash\ncodexbar cost --provider codex --format json > /tmp/cost.json\npython {baseDir}/scripts/model_usage.py --input /tmp/cost.json --mode all\ncat /tmp/cost.json | python {baseDir}/scripts/model_usage.py --input - --mode current\n```\n\n## Output\n\n- Text (default) or JSON (`--format json --pretty`).\n- Values are cost-only per model; tokens are not split by model in CodexBar output.\n\n## References\n\n- Read `references/codexbar-cli.md` for CLI flags and cost JSON fields.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/nano-banana-pro.json

@@ -0,0 +1,10 @@
+{
+  "id": "nano-banana-pro",
+  "name": "Nano-banana-pro",
+  "description": "Generate or edit images via Gemini 3 Pro Image (Nano Banana Pro).",
+  "icon": "🍌",
+  "category": "Tools",
+  "prompt": "# Nano Banana Pro (Gemini 3 Pro Image)\n\nUse the bundled script to generate or edit images.\n\nGenerate\n\n```bash\nuv run {baseDir}/scripts/generate_image.py --prompt \"your image description\" --filename \"output.png\" --resolution 1K\n```\n\nEdit (single image)\n\n```bash\nuv run {baseDir}/scripts/generate_image.py --prompt \"edit instructions\" --filename \"output.png\" -i \"/path/in.png\" --resolution 2K\n```\n\nMulti-image composition (up to 14 images)\n\n```bash\nuv run {baseDir}/scripts/generate_image.py --prompt \"combine these into one scene\" --filename \"output.png\" -i img1.png -i img2.png -i img3.png\n```\n\nAPI key\n\n- `GEMINI_API_KEY` env var\n- Or set `skills.\"nano-banana-pro\".apiKey` / `skills.\"nano-banana-pro\".env.GEMINI_API_KEY` in `~/.CoWork-OSS/CoWork-OSS.json`\n\nNotes\n\n- Resolutions: `1K` (default), `2K`, `4K`.\n- Use timestamps in filenames: `yyyy-mm-dd-hh-mm-ss-name.png`.\n- The script prints a `MEDIA:` line for CoWork-OSS to auto-attach on supported chat providers.\n- Do not read the image back; report the saved path only.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/nano-pdf.json

@@ -0,0 +1,10 @@
+{
+  "id": "nano-pdf",
+  "name": "Nano-pdf",
+  "description": "Edit PDFs with natural-language instructions using the nano-pdf CLI.",
+  "icon": "📄",
+  "category": "Tools",
+  "prompt": "# nano-pdf\n\nUse `nano-pdf` to apply edits to a specific page in a PDF using a natural-language instruction.\n\n## Quick start\n\n```bash\nnano-pdf edit deck.pdf 1 \"Change the title to 'Q3 Results' and fix the typo in the subtitle\"\n```\n\nNotes:\n\n- Page numbers are 0-based or 1-based depending on the tool’s version/config; if the result looks off by one, retry with the other.\n- Always sanity-check the output PDF before sending it out.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/notion.json

@@ -0,0 +1,10 @@
+{
+  "id": "notion",
+  "name": "Notion",
+  "description": "Notion API for creating and managing pages, databases, and blocks.",
+  "icon": "📝",
+  "category": "Tools",
+  "prompt": "# notion\n\nUse the Notion API to create/read/update pages, data sources (databases), and blocks.\n\n## Setup\n\n1. Create an integration at https://notion.so/my-integrations\n2. Copy the API key (starts with `ntn_` or `secret_`)\n3. Store it:\n\n```bash\nmkdir -p ~/.config/notion\necho \"ntn_your_key_here\" > ~/.config/notion/api_key\n```\n\n4. Share target pages/databases with your integration (click \"...\" → \"Connect to\" → your integration name)\n\n## API Basics\n\nAll requests need:\n\n```bash\nNOTION_KEY=$(cat ~/.config/notion/api_key)\ncurl -X GET \"https://api.notion.com/v1/...\" \\\n  -H \"Authorization: Bearer $NOTION_KEY\" \\\n  -H \"Notion-Version: 2025-09-03\" \\\n  -H \"Content-Type: application/json\"\n```\n\n> **Note:** The `Notion-Version` header is required. This skill uses `2025-09-03` (latest). In this version, databases are called \"data sources\" in the API.\n\n## Common Operations\n\n**Search for pages and data sources:**\n\n```bash\ncurl -X POST \"https://api.notion.com/v1/search\" \\\n  -H \"Authorization: Bearer $NOTION_KEY\" \\\n  -H \"Notion-Version: 2025-09-03\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"query\": \"page title\"}'\n```\n\n**Get page:**\n\n```bash\ncurl \"https://api.notion.com/v1/pages/{page_id}\" \\\n  -H \"Authorization: Bearer $NOTION_KEY\" \\\n  -H \"Notion-Version: 2025-09-03\"\n```\n\n**Get page content (blocks):**\n\n```bash\ncurl \"https://api.notion.com/v1/blocks/{page_id}/children\" \\\n  -H \"Authorization: Bearer $NOTION_KEY\" \\\n  -H \"Notion-Version: 2025-09-03\"\n```\n\n**Create page in a data source:**\n\n```bash\ncurl -X POST \"https://api.notion.com/v1/pages\" \\\n  -H \"Authorization: Bearer $NOTION_KEY\" \\\n  -H \"Notion-Version: 2025-09-03\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\n    \"parent\": {\"database_id\": \"xxx\"},\n    \"properties\": {\n      \"Name\": {\"title\": [{\"text\": {\"content\": \"New Item\"}}]},\n      \"Status\": {\"select\": {\"name\": \"Todo\"}}\n    }\n  }'\n```\n\n**Query a data source (database):**\n\n```bash\ncurl -X POST \"https://api.notion.com/v1/data_sources/{data_source_id}/query\" \\\n  -H \"Authorization: Bearer $NOTION_KEY\" \\\n  -H \"Notion-Version: 2025-09-03\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\n    \"filter\": {\"property\": \"Status\", \"select\": {\"equals\": \"Active\"}},\n    \"sorts\": [{\"property\": \"Date\", \"direction\": \"descending\"}]\n  }'\n```\n\n**Create a data source (database):**\n\n```bash\ncurl -X POST \"https://api.notion.com/v1/data_sources\" \\\n  -H \"Authorization: Bearer $NOTION_KEY\" \\\n  -H \"Notion-Version: 2025-09-03\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\n    \"parent\": {\"page_id\": \"xxx\"},\n    \"title\": [{\"text\": {\"content\": \"My Database\"}}],\n    \"properties\": {\n      \"Name\": {\"title\": {}},\n      \"Status\": {\"select\": {\"options\": [{\"name\": \"Todo\"}, {\"name\": \"Done\"}]}},\n      \"Date\": {\"date\": {}}\n    }\n  }'\n```\n\n**Update page properties:**\n\n```bash\ncurl -X PATCH \"https://api.notion.com/v1/pages/{page_id}\" \\\n  -H \"Authorization: Bearer $NOTION_KEY\" \\\n  -H \"Notion-Version: 2025-09-03\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"properties\": {\"Status\": {\"select\": {\"name\": \"Done\"}}}}'\n```\n\n**Add blocks to page:**\n\n```bash\ncurl -X PATCH \"https://api.notion.com/v1/blocks/{page_id}/children\" \\\n  -H \"Authorization: Bearer $NOTION_KEY\" \\\n  -H \"Notion-Version: 2025-09-03\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\n    \"children\": [\n      {\"object\": \"block\", \"type\": \"paragraph\", \"paragraph\": {\"rich_text\": [{\"text\": {\"content\": \"Hello\"}}]}}\n    ]\n  }'\n```\n\n## Property Types\n\nCommon property formats for database items:\n\n- **Title:** `{\"title\": [{\"text\": {\"content\": \"...\"}}]}`\n- **Rich text:** `{\"rich_text\": [{\"text\": {\"content\": \"...\"}}]}`\n- **Select:** `{\"select\": {\"name\": \"Option\"}}`\n- **Multi-select:** `{\"multi_select\": [{\"name\": \"A\"}, {\"name\": \"B\"}]}`\n- **Date:** `{\"date\": {\"start\": \"2024-01-15\", \"end\": \"2024-01-16\"}}`\n- **Checkbox:** `{\"checkbox\": true}`\n- **Number:** `{\"number\": 42}`\n- **URL:** `{\"url\": \"https://...\"}`\n- **Email:** `{\"email\": \"a@b.com\"}`\n- **Relation:** `{\"relation\": [{\"id\": \"page_id\"}]}`\n\n## Key Differences in 2025-09-03\n\n- **Databases → Data Sources:** Use `/data_sources/` endpoints for queries and retrieval\n- **Two IDs:** Each database now has both a `database_id` and a `data_source_id`\n  - Use `database_id` when creating pages (`parent: {\"database_id\": \"...\"}`)\n  - Use `data_source_id` when querying (`POST /v1/data_sources/{id}/query`)\n- **Search results:** Databases return as `\"object\": \"data_source\"` with their `data_source_id`\n- **Parent in responses:** Pages show `parent.data_source_id` alongside `parent.database_id`\n- **Finding the data_source_id:** Search for the database, or call `GET /v1/data_sources/{data_source_id}`\n\n## Notes\n\n- Page/database IDs are UUIDs (with or without dashes)\n- The API cannot set database view filters — that's UI-only\n- Rate limit: ~3 requests/second average\n- Use `is_inline: true` when creating data sources to embed them in pages",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/obsidian.json

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

package/resources/skills/openai-image-gen.json

@@ -0,0 +1,10 @@
+{
+  "id": "openai-image-gen",
+  "name": "Openai-image-gen",
+  "description": "Batch-generate images via OpenAI Images API. Random prompt sampler + `index.html` gallery.",
+  "icon": "🖼️",
+  "category": "Tools",
+  "prompt": "# OpenAI Image Gen\n\nGenerate a handful of “random but structured” prompts and render them via the OpenAI Images API.\n\n## Run\n\n```bash\npython3 {baseDir}/scripts/gen.py\nopen ~/Projects/tmp/openai-image-gen-*/index.html  # if ~/Projects/tmp exists; else ./tmp/...\n```\n\nUseful flags:\n\n```bash\n# GPT image models with various options\npython3 {baseDir}/scripts/gen.py --count 16 --model gpt-image-1\npython3 {baseDir}/scripts/gen.py --prompt \"ultra-detailed studio photo of a lobster astronaut\" --count 4\npython3 {baseDir}/scripts/gen.py --size 1536x1024 --quality high --out-dir ./out/images\npython3 {baseDir}/scripts/gen.py --model gpt-image-1.5 --background transparent --output-format webp\n\n# DALL-E 3 (note: count is automatically limited to 1)\npython3 {baseDir}/scripts/gen.py --model dall-e-3 --quality hd --size 1792x1024 --style vivid\npython3 {baseDir}/scripts/gen.py --model dall-e-3 --style natural --prompt \"serene mountain landscape\"\n\n# DALL-E 2\npython3 {baseDir}/scripts/gen.py --model dall-e-2 --size 512x512 --count 4\n```\n\n## Model-Specific Parameters\n\nDifferent models support different parameter values. The script automatically selects appropriate defaults based on the model.\n\n### Size\n\n- **GPT image models** (`gpt-image-1`, `gpt-image-1-mini`, `gpt-image-1.5`): `1024x1024`, `1536x1024` (landscape), `1024x1536` (portrait), or `auto`\n  - Default: `1024x1024`\n- **dall-e-3**: `1024x1024`, `1792x1024`, or `1024x1792`\n  - Default: `1024x1024`\n- **dall-e-2**: `256x256`, `512x512`, or `1024x1024`\n  - Default: `1024x1024`\n\n### Quality\n\n- **GPT image models**: `auto`, `high`, `medium`, or `low`\n  - Default: `high`\n- **dall-e-3**: `hd` or `standard`\n  - Default: `standard`\n- **dall-e-2**: `standard` only\n  - Default: `standard`\n\n### Other Notable Differences\n\n- **dall-e-3** only supports generating 1 image at a time (`n=1`). The script automatically limits count to 1 when using this model.\n- **GPT image models** support additional parameters:\n  - `--background`: `transparent`, `opaque`, or `auto` (default)\n  - `--output-format`: `png` (default), `jpeg`, or `webp`\n  - Note: `stream` and `moderation` are available via API but not yet implemented in this script\n- **dall-e-3** has a `--style` parameter: `vivid` (hyper-real, dramatic) or `natural` (more natural looking)\n\n## Output\n\n- `*.png`, `*.jpeg`, or `*.webp` images (output format depends on model + `--output-format`)\n- `prompts.json` (prompt → file mapping)\n- `index.html` (thumbnail gallery)",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/openai-whisper-api.json

@@ -0,0 +1,10 @@
+{
+  "id": "openai-whisper-api",
+  "name": "Openai-whisper-api",
+  "description": "Transcribe audio via OpenAI Audio Transcriptions API (Whisper).",
+  "icon": "☁️",
+  "category": "Tools",
+  "prompt": "# OpenAI Whisper API (curl)\n\nTranscribe an audio file via OpenAI’s `/v1/audio/transcriptions` endpoint.\n\n## Quick start\n\n```bash\n{baseDir}/scripts/transcribe.sh /path/to/audio.m4a\n```\n\nDefaults:\n\n- Model: `whisper-1`\n- Output: `<input>.txt`\n\n## Useful flags\n\n```bash\n{baseDir}/scripts/transcribe.sh /path/to/audio.ogg --model whisper-1 --out /tmp/transcript.txt\n{baseDir}/scripts/transcribe.sh /path/to/audio.m4a --language en\n{baseDir}/scripts/transcribe.sh /path/to/audio.m4a --prompt \"Speaker names: Peter, Daniel\"\n{baseDir}/scripts/transcribe.sh /path/to/audio.m4a --json --out /tmp/transcript.json\n```\n\n## API key\n\nSet `OPENAI_API_KEY`, or configure it in `~/.CoWork-OSS/CoWork-OSS.json`:\n\n```json5\n{\n  skills: {\n    \"openai-whisper-api\": {\n      apiKey: \"OPENAI_KEY_HERE\",\n    },\n  },\n}\n```",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/openai-whisper.json

@@ -0,0 +1,10 @@
+{
+  "id": "openai-whisper",
+  "name": "Openai-whisper",
+  "description": "Local speech-to-text with the Whisper CLI (no API key).",
+  "icon": "🎙️",
+  "category": "Tools",
+  "prompt": "# Whisper (CLI)\n\nUse `whisper` to transcribe audio locally.\n\nQuick start\n\n- `whisper /path/audio.mp3 --model medium --output_format txt --output_dir .`\n- `whisper /path/audio.m4a --task translate --output_format srt`\n\nNotes\n\n- Models download to `~/.cache/whisper` on first run.\n- `--model` defaults to `turbo` on this install.\n- Use smaller models for speed, larger for accuracy.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/openhue.json

@@ -0,0 +1,10 @@
+{
+  "id": "openhue",
+  "name": "Openhue",
+  "description": "Control Philips Hue lights/scenes via the OpenHue CLI.",
+  "icon": "💡",
+  "category": "Tools",
+  "prompt": "# OpenHue CLI\n\nUse `openhue` to control Hue lights and scenes via a Hue Bridge.\n\nSetup\n\n- Discover bridges: `openhue discover`\n- Guided setup: `openhue setup`\n\nRead\n\n- `openhue get light --json`\n- `openhue get room --json`\n- `openhue get scene --json`\n\nWrite\n\n- Turn on: `openhue set light <id-or-name> --on`\n- Turn off: `openhue set light <id-or-name> --off`\n- Brightness: `openhue set light <id> --on --brightness 50`\n- Color: `openhue set light <id> --on --rgb #3399FF`\n- Scene: `openhue set scene <scene-id>`\n\nNotes\n\n- You may need to press the Hue Bridge button during setup.\n- Use `--room \"Room Name\"` when light names are ambiguous.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/oracle.json

@@ -0,0 +1,10 @@
+{
+  "id": "oracle",
+  "name": "Oracle",
+  "description": "Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).",
+  "icon": "🧿",
+  "category": "Tools",
+  "prompt": "# oracle — best use\n\nOracle bundles your prompt + selected files into one “one-shot” request so another model can answer with real repo context (API or browser automation). Treat output as advisory: verify against code + tests.\n\n## Main use case (browser, GPT‑5.2 Pro)\n\nDefault workflow here: `--engine browser` with GPT‑5.2 Pro in ChatGPT. This is the common “long think” path: ~10 minutes to ~1 hour is normal; expect a stored session you can reattach to.\n\nRecommended defaults:\n\n- Engine: browser (`--engine browser`)\n- Model: GPT‑5.2 Pro (`--model gpt-5.2-pro` or `--model \"5.2 Pro\"`)\n\n## Golden path\n\n1. Pick a tight file set (fewest files that still contain the truth).\n2. Preview payload + token spend (`--dry-run` + `--files-report`).\n3. Use browser mode for the usual GPT‑5.2 Pro workflow; use API only when you explicitly want it.\n4. If the run detaches/timeouts: reattach to the stored session (don’t re-run).\n\n## Commands (preferred)\n\n- Help:\n  - `oracle --help`\n  - If the binary isn’t installed: `npx -y @steipete/oracle --help` (avoid `pnpx` here; sqlite bindings).\n\n- Preview (no tokens):\n  - `oracle --dry-run summary -p \"<task>\" --file \"src/**\" --file \"!**/*.test.*\"`\n  - `oracle --dry-run full -p \"<task>\" --file \"src/**\"`\n\n- Token sanity:\n  - `oracle --dry-run summary --files-report -p \"<task>\" --file \"src/**\"`\n\n- Browser run (main path; long-running is normal):\n  - `oracle --engine browser --model gpt-5.2-pro -p \"<task>\" --file \"src/**\"`\n\n- Manual paste fallback:\n  - `oracle --render --copy -p \"<task>\" --file \"src/**\"`\n  - Note: `--copy` is a hidden alias for `--copy-markdown`.\n\n## Attaching files (`--file`)\n\n`--file` accepts files, directories, and globs. You can pass it multiple times; entries can be comma-separated.\n\n- Include:\n  - `--file \"src/**\"`\n  - `--file src/index.ts`\n  - `--file docs --file README.md`\n\n- Exclude:\n  - `--file \"src/**\" --file \"!src/**/*.test.ts\" --file \"!**/*.snap\"`\n\n- Defaults (implementation behavior):\n  - Default-ignored dirs: `node_modules`, `dist`, `coverage`, `.git`, `.turbo`, `.next`, `build`, `tmp` (skipped unless explicitly passed as literal dirs/files).\n  - Honors `.gitignore` when expanding globs.\n  - Does not follow symlinks.\n  - Dotfiles filtered unless opted in via pattern (e.g. `--file \".github/**\"`).\n  - Files > 1 MB rejected.\n\n## Engines (API vs browser)\n\n- Auto-pick: `api` when `OPENAI_API_KEY` is set; otherwise `browser`.\n- Browser supports GPT + Gemini only; use `--engine api` for Claude/Grok/Codex or multi-model runs.\n- Browser attachments:\n  - `--browser-attachments auto|never|always` (auto pastes inline up to ~60k chars then uploads).\n- Remote browser host:\n  - Host: `oracle serve --host 0.0.0.0 --port 9473 --token <secret>`\n  - Client: `oracle --engine browser --remote-host <host:port> --remote-token <secret> -p \"<task>\" --file \"src/**\"`\n\n## Sessions + slugs\n\n- Stored under `~/.oracle/sessions` (override with `ORACLE_HOME_DIR`).\n- Runs may detach or take a long time (browser + GPT‑5.2 Pro often does). If the CLI times out: don’t re-run; reattach.\n  - List: `oracle status --hours 72`\n  - Attach: `oracle session <id> --render`\n- Use `--slug \"<3-5 words>\"` to keep session IDs readable.\n- Duplicate prompt guard exists; use `--force` only when you truly want a fresh run.\n\n## Prompt template (high signal)\n\nOracle starts with **zero** project knowledge. Assume the model cannot infer your stack, build tooling, conventions, or “obvious” paths. Include:\n\n- Project briefing (stack + build/test commands + platform constraints).\n- “Where things live” (key directories, entrypoints, config files, boundaries).\n- Exact question + what you tried + the error text (verbatim).\n- Constraints (“don’t change X”, “must keep public API”, etc).\n- Desired output (“return patch plan + tests”, “give 3 options with tradeoffs”).\n\n## Safety\n\n- Don’t attach secrets by default (`.env`, key files, auth tokens). Redact aggressively; share only what’s required.\n\n## “Exhaustive prompt” restoration pattern\n\nFor long investigations, write a standalone prompt + file set so you can rerun days later:\n\n- 6–30 sentence project briefing + the goal.\n- Repro steps + exact errors + what you tried.\n- Attach all context files needed (entrypoints, configs, key modules, docs).\n\nOracle runs are one-shot; the model doesn’t remember prior runs. “Restoring context” means re-running with the same prompt + `--file …` set (or reattaching a still-running stored session).",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/ordercli.json

@@ -0,0 +1,10 @@
+{
+  "id": "ordercli",
+  "name": "Ordercli",
+  "description": "Foodora-only CLI for checking past orders and active order status (Deliveroo WIP).",
+  "icon": "🛵",
+  "category": "Tools",
+  "prompt": "# ordercli\n\nUse `ordercli` to check past orders and track active order status (Foodora only right now).\n\nQuick start (Foodora)\n\n- `ordercli foodora countries`\n- `ordercli foodora config set --country AT`\n- `ordercli foodora login --email you@example.com --password-stdin`\n- `ordercli foodora orders`\n- `ordercli foodora history --limit 20`\n- `ordercli foodora history show <orderCode>`\n\nOrders\n\n- Active list (arrival/status): `ordercli foodora orders`\n- Watch: `ordercli foodora orders --watch`\n- Active order detail: `ordercli foodora order <orderCode>`\n- History detail JSON: `ordercli foodora history show <orderCode> --json`\n\nReorder (adds to cart)\n\n- Preview: `ordercli foodora reorder <orderCode>`\n- Confirm: `ordercli foodora reorder <orderCode> --confirm`\n- Address: `ordercli foodora reorder <orderCode> --confirm --address-id <id>`\n\nCloudflare / bot protection\n\n- Browser login: `ordercli foodora login --email you@example.com --password-stdin --browser`\n- Reuse profile: `--browser-profile \"$HOME/Library/Application Support/ordercli/browser-profile\"`\n- Import Chrome cookies: `ordercli foodora cookies chrome --profile \"Default\"`\n\nSession import (no password)\n\n- `ordercli foodora session chrome --url https://www.foodora.at/ --profile \"Default\"`\n- `ordercli foodora session refresh --client-id android`\n\nDeliveroo (WIP, not working yet)\n\n- Requires `DELIVEROO_BEARER_TOKEN` (optional `DELIVEROO_COOKIE`).\n- `ordercli deliveroo config set --market uk`\n- `ordercli deliveroo history`\n\nNotes\n\n- Use `--config /tmp/ordercli.json` for testing.\n- Confirm before any reorder or cart-changing action.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/peekaboo.json

@@ -0,0 +1,10 @@
+{
+  "id": "peekaboo",
+  "name": "Peekaboo",
+  "description": "Capture and automate macOS UI with the Peekaboo CLI.",
+  "icon": "👀",
+  "category": "Tools",
+  "prompt": "# Peekaboo\n\nPeekaboo is a full macOS UI automation CLI: capture/inspect screens, target UI\nelements, drive input, and manage apps/windows/menus. Commands share a snapshot\ncache and support `--json`/`-j` for scripting. Run `peekaboo` or\n`peekaboo <cmd> --help` for flags; `peekaboo --version` prints build metadata.\nTip: run via `polter peekaboo` to ensure fresh builds.\n\n## Features (all CLI capabilities, excluding agent/MCP)\n\nCore\n\n- `bridge`: inspect Peekaboo Bridge host connectivity\n- `capture`: live capture or video ingest + frame extraction\n- `clean`: prune snapshot cache and temp files\n- `config`: init/show/edit/validate, providers, models, credentials\n- `image`: capture screenshots (screen/window/menu bar regions)\n- `learn`: print the full agent guide + tool catalog\n- `list`: apps, windows, screens, menubar, permissions\n- `permissions`: check Screen Recording/Accessibility status\n- `run`: execute `.peekaboo.json` scripts\n- `sleep`: pause execution for a duration\n- `tools`: list available tools with filtering/display options\n\nInteraction\n\n- `click`: target by ID/query/coords with smart waits\n- `drag`: drag & drop across elements/coords/Dock\n- `hotkey`: modifier combos like `cmd,shift,t`\n- `move`: cursor positioning with optional smoothing\n- `paste`: set clipboard -> paste -> restore\n- `press`: special-key sequences with repeats\n- `scroll`: directional scrolling (targeted + smooth)\n- `swipe`: gesture-style drags between targets\n- `type`: text + control keys (`--clear`, delays)\n\nSystem\n\n- `app`: launch/quit/relaunch/hide/unhide/switch/list apps\n- `clipboard`: read/write clipboard (text/images/files)\n- `dialog`: click/input/file/dismiss/list system dialogs\n- `dock`: launch/right-click/hide/show/list Dock items\n- `menu`: click/list application menus + menu extras\n- `menubar`: list/click status bar items\n- `open`: enhanced `open` with app targeting + JSON payloads\n- `space`: list/switch/move-window (Spaces)\n- `visualizer`: exercise Peekaboo visual feedback animations\n- `window`: close/minimize/maximize/move/resize/focus/list\n\nVision\n\n- `see`: annotated UI maps, snapshot IDs, optional analysis\n\nGlobal runtime flags\n\n- `--json`/`-j`, `--verbose`/`-v`, `--log-level <level>`\n- `--no-remote`, `--bridge-socket <path>`\n\n## Quickstart (happy path)\n\n```bash\npeekaboo permissions\npeekaboo list apps --json\npeekaboo see --annotate --path /tmp/peekaboo-see.png\npeekaboo click --on B1\npeekaboo type \"Hello\" --return\n```\n\n## Common targeting parameters (most interaction commands)\n\n- App/window: `--app`, `--pid`, `--window-title`, `--window-id`, `--window-index`\n- Snapshot targeting: `--snapshot` (ID from `see`; defaults to latest)\n- Element/coords: `--on`/`--id` (element ID), `--coords x,y`\n- Focus control: `--no-auto-focus`, `--space-switch`, `--bring-to-current-space`,\n  `--focus-timeout-seconds`, `--focus-retry-count`\n\n## Common capture parameters\n\n- Output: `--path`, `--format png|jpg`, `--retina`\n- Targeting: `--mode screen|window|frontmost`, `--screen-index`,\n  `--window-title`, `--window-id`\n- Analysis: `--analyze \"prompt\"`, `--annotate`\n- Capture engine: `--capture-engine auto|classic|cg|modern|sckit`\n\n## Common motion/typing parameters\n\n- Timing: `--duration` (drag/swipe), `--steps`, `--delay` (type/scroll/press)\n- Human-ish movement: `--profile human|linear`, `--wpm` (typing)\n- Scroll: `--direction up|down|left|right`, `--amount <ticks>`, `--smooth`\n\n## Examples\n\n### See -> click -> type (most reliable flow)\n\n```bash\npeekaboo see --app Safari --window-title \"Login\" --annotate --path /tmp/see.png\npeekaboo click --on B3 --app Safari\npeekaboo type \"user@example.com\" --app Safari\npeekaboo press tab --count 1 --app Safari\npeekaboo type \"supersecret\" --app Safari --return\n```\n\n### Target by window id\n\n```bash\npeekaboo list windows --app \"Visual Studio Code\" --json\npeekaboo click --window-id 12345 --coords 120,160\npeekaboo type \"Hello from Peekaboo\" --window-id 12345\n```\n\n### Capture screenshots + analyze\n\n```bash\npeekaboo image --mode screen --screen-index 0 --retina --path /tmp/screen.png\npeekaboo image --app Safari --window-title \"Dashboard\" --analyze \"Summarize KPIs\"\npeekaboo see --mode screen --screen-index 0 --analyze \"Summarize the dashboard\"\n```\n\n### Live capture (motion-aware)\n\n```bash\npeekaboo capture live --mode region --region 100,100,800,600 --duration 30 \\\n  --active-fps 8 --idle-fps 2 --highlight-changes --path /tmp/capture\n```\n\n### App + window management\n\n```bash\npeekaboo app launch \"Safari\" --open https://example.com\npeekaboo window focus --app Safari --window-title \"Example\"\npeekaboo window set-bounds --app Safari --x 50 --y 50 --width 1200 --height 800\npeekaboo app quit --app Safari\n```\n\n### Menus, menubar, dock\n\n```bash\npeekaboo menu click --app Safari --item \"New Window\"\npeekaboo menu click --app TextEdit --path \"Format > Font > Show Fonts\"\npeekaboo menu click-extra --title \"WiFi\"\npeekaboo dock launch Safari\npeekaboo menubar list --json\n```\n\n### Mouse + gesture input\n\n```bash\npeekaboo move 500,300 --smooth\npeekaboo drag --from B1 --to T2\npeekaboo swipe --from-coords 100,500 --to-coords 100,200 --duration 800\npeekaboo scroll --direction down --amount 6 --smooth\n```\n\n### Keyboard input\n\n```bash\npeekaboo hotkey --keys \"cmd,shift,t\"\npeekaboo press escape\npeekaboo type \"Line 1\\nLine 2\" --delay 10\n```\n\nNotes\n\n- Requires Screen Recording + Accessibility permissions.\n- Use `peekaboo see --annotate` to identify targets before clicking.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/project-structure.json

@@ -0,0 +1,10 @@
+{
+  "id": "project-structure",
+  "name": "Project Structure",
+  "description": "Analyze and explain project architecture",
+  "icon": "🏗️",
+  "category": "Project",
+  "prompt": "Please analyze this project's structure and architecture.\n\nProvide:\n1. **Directory Structure**: Visual tree of important directories\n2. **Architecture Overview**: How the project is organized\n3. **Key Files**: Entry points, configs, main modules\n4. **Data Flow**: How data moves through the system\n5. **Dependencies**: External libraries and their purposes\n6. **Design Patterns**: Patterns used in the codebase\n7. **Tech Stack**: Languages, frameworks, tools used\n\nFormat as a clear, well-organized document that would help a new developer understand the project.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/proofread.json

@@ -0,0 +1,17 @@
+{
+  "id": "proofread",
+  "name": "Proofread",
+  "description": "Check document for grammar and clarity",
+  "icon": "✏️",
+  "category": "Writing",
+  "prompt": "Please proofread the document at {{path}}.\n\nCheck for:\n- Spelling errors\n- Grammar mistakes\n- Punctuation issues\n- Awkward phrasing\n- Unclear sentences\n- Consistency (terminology, formatting)\n- Tone appropriateness\n\nFor each issue:\n1. Quote the original text\n2. Explain the problem\n3. Suggest a correction\n\nAt the end, provide:\n- Overall quality score (1-10)\n- Summary of common issues\n- General improvement suggestions",
+  "parameters": [
+    {
+      "name": "path",
+      "type": "string",
+      "description": "Path to the document",
+      "required": true
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/refactor-code.json

@@ -0,0 +1,31 @@
+{
+  "id": "refactor-code",
+  "name": "Refactor Code",
+  "description": "Improve code structure and readability",
+  "icon": "🔧",
+  "category": "Development",
+  "prompt": "Please refactor the code in {{path}} to improve its quality.\n\nFocus on:\n- {{focus}}\n- Maintaining the same functionality\n- Adding comments where helpful\n- Following best practices for the language\n\nExplain the changes you make and why.",
+  "parameters": [
+    {
+      "name": "path",
+      "type": "string",
+      "description": "Path to the file to refactor",
+      "required": true
+    },
+    {
+      "name": "focus",
+      "type": "select",
+      "description": "What to focus on",
+      "required": true,
+      "default": "readability",
+      "options": [
+        "readability",
+        "performance",
+        "modularity",
+        "error handling",
+        "all of the above"
+      ]
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/rename-symbol.json

@@ -0,0 +1,23 @@
+{
+  "id": "rename-symbol",
+  "name": "Rename Symbol",
+  "description": "Rename a variable/function across files",
+  "icon": "🏷️",
+  "category": "Utilities",
+  "prompt": "Please rename \"{{oldName}}\" to \"{{newName}}\" across the project.\n\nSteps:\n1. Find all occurrences of the symbol\n2. Distinguish between:\n   - The actual symbol (function, variable, class)\n   - String literals containing the name\n   - Comments mentioning the name\n3. Rename only the actual symbol references\n4. Update imports/exports as needed\n5. Check for naming conflicts\n\nReport:\n- Files modified\n- Number of replacements\n- Any manual review needed (strings, comments)\n\nBe careful not to rename unrelated code that happens to have the same name.",
+  "parameters": [
+    {
+      "name": "oldName",
+      "type": "string",
+      "description": "Current name of the symbol",
+      "required": true
+    },
+    {
+      "name": "newName",
+      "type": "string",
+      "description": "New name for the symbol",
+      "required": true
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/sag.json

@@ -0,0 +1,10 @@
+{
+  "id": "sag",
+  "name": "Sag",
+  "description": "ElevenLabs text-to-speech with mac-style say UX.",
+  "icon": "🗣️",
+  "category": "Tools",
+  "prompt": "# sag\n\nUse `sag` for ElevenLabs TTS with local playback.\n\nAPI key (required)\n\n- `ELEVENLABS_API_KEY` (preferred)\n- `SAG_API_KEY` also supported by the CLI\n\nQuick start\n\n- `sag \"Hello there\"`\n- `sag speak -v \"Roger\" \"Hello\"`\n- `sag voices`\n- `sag prompting` (model-specific tips)\n\nModel notes\n\n- Default: `eleven_v3` (expressive)\n- Stable: `eleven_multilingual_v2`\n- Fast: `eleven_flash_v2_5`\n\nPronunciation + delivery rules\n\n- First fix: respell (e.g. \"key-note\"), add hyphens, adjust casing.\n- Numbers/units/URLs: `--normalize auto` (or `off` if it harms names).\n- Language bias: `--lang en|de|fr|...` to guide normalization.\n- v3: SSML `<break>` not supported; use `[pause]`, `[short pause]`, `[long pause]`.\n- v2/v2.5: SSML `<break time=\"1.5s\" />` supported; `<phoneme>` not exposed in `sag`.\n\nv3 audio tags (put at the entrance of a line)\n\n- `[whispers]`, `[shouts]`, `[sings]`\n- `[laughs]`, `[starts laughing]`, `[sighs]`, `[exhales]`\n- `[sarcastic]`, `[curious]`, `[excited]`, `[crying]`, `[mischievously]`\n- Example: `sag \"[whispers] keep this quiet. [short pause] ok?\"`\n\nVoice defaults\n\n- `ELEVENLABS_VOICE_ID` or `SAG_VOICE_ID`\n\nConfirm voice + speaker before long output.\n\n## Chat voice responses\n\nWhen Peter asks for a \"voice\" reply (e.g., \"crazy scientist voice\", \"explain in voice\"), generate audio and send it:\n\n```bash\n# Generate audio file\nsag -v CoWork-OSS -o /tmp/voice-reply.mp3 \"Your message here\"\n\n# Then include in reply:\n# MEDIA:/tmp/voice-reply.mp3\n```\n\nVoice character tips:\n\n- Crazy scientist: Use `[excited]` tags, dramatic pauses `[short pause]`, vary intensity\n- Calm: Use `[whispers]` or slower pacing\n- Dramatic: Use `[sings]` or `[shouts]` sparingly\n\nDefault voice for CoWork-OSS: `lj2rcrvANS3gaWWnczSX` (or just `-v CoWork-OSS`)",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/security-audit.json

@@ -0,0 +1,18 @@
+{
+  "id": "security-audit",
+  "name": "Security Audit",
+  "description": "Check code for common security vulnerabilities",
+  "icon": "🔒",
+  "category": "Development",
+  "prompt": "Please perform a security audit on {{path}}.\n\nCheck for:\n- SQL injection vulnerabilities\n- XSS (Cross-Site Scripting) risks\n- Command injection possibilities\n- Insecure data handling\n- Hardcoded secrets or credentials\n- Insecure dependencies\n- Authentication/authorization issues\n- Input validation problems\n- Sensitive data exposure\n\nFor each issue found:\n1. Describe the vulnerability\n2. Explain the potential impact\n3. Provide a fix with code example\n4. Rate severity (Critical/High/Medium/Low)",
+  "parameters": [
+    {
+      "name": "path",
+      "type": "string",
+      "description": "Path to file or folder to audit",
+      "required": true,
+      "default": "."
+    }
+  ],
+  "enabled": true
+}