opencode-skills-collection 3.1.0 → 3.1.2

package/bundled-skills/.antigravity-install-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-06-19T02:46:58.138Z",
+  "updatedAt": "2026-06-21T02:30:50.258Z",
   "entries": [
     "00-andruia-consultant",
     "007",
@@ -78,6 +78,7 @@
     "android-cli",
     "android-dev",
     "android-jetpack-compose-expert",
+    "android-ui-journey-testing",
     "android_ui_verification",
     "angular",
     "angular-best-practices",
@@ -128,6 +129,7 @@
     "arm-cortex-expert",
     "article-illustrations",
     "asana-automation",
+    "ask-matt",
     "ask-questions-if-underspecified",
     "astro",
     "astropy",
@@ -314,6 +316,7 @@
     "browser-automation",
     "browser-extension-builder",
     "bug-hunter",
+    "bugs-are-annoying",
     "build",
     "building-native-ui",
     "bulletmind",
@@ -393,6 +396,7 @@
     "codebase-cleanup-deps-audit",
     "codebase-cleanup-refactor-clean",
     "codebase-cleanup-tech-debt",
+    "codebase-design",
     "codebase-to-wordpress-converter",
     "codex-fable5",
     "codex-review",
@@ -401,6 +405,7 @@
     "commit",
     "competitive-landscape",
     "competitor-alternatives",
+    "competitor-analysis",
     "complexity-cuts",
     "composition-patterns",
     "comprehensive-review-full-review",
@@ -510,6 +515,55 @@
     "deployment-pipeline-design",
     "deployment-procedures",
     "deployment-validation-config-validate",
+    "design-it",
+    "design-it/3d-ui",
+    "design-it/ai-native-ui",
+    "design-it/aurora-ui",
+    "design-it/bento-ui",
+    "design-it/brutalism",
+    "design-it/brutalist-typography",
+    "design-it/card-based-design",
+    "design-it/claymorphism",
+    "design-it/color-blocking",
+    "design-it/command-center-ui",
+    "design-it/cyber-y2k",
+    "design-it/cyberpunk-ui",
+    "design-it/dark-mode",
+    "design-it/dashboard-design",
+    "design-it/data-dense-design",
+    "design-it/duotone-design",
+    "design-it/editorial-design",
+    "design-it/flat-design",
+    "design-it/flat-design-2",
+    "design-it/floating-ui",
+    "design-it/frutiger-aero",
+    "design-it/glassmorphism",
+    "design-it/gradient-design",
+    "design-it/high-contrast",
+    "design-it/holographic-ui",
+    "design-it/isometric-design",
+    "design-it/layered-design",
+    "design-it/material-design",
+    "design-it/maximalism",
+    "design-it/minimalism",
+    "design-it/monochromatic-ui",
+    "design-it/neo-brutalism",
+    "design-it/neumorphism",
+    "design-it/retro-design",
+    "design-it/retro-futurism",
+    "design-it/sci-fi-interface",
+    "design-it/skeuomorphism",
+    "design-it/soft-pastel",
+    "design-it/spatial-computing-ui",
+    "design-it/spatial-design",
+    "design-it/swiss-design",
+    "design-it/synthwave",
+    "design-it/tile-design",
+    "design-it/typography-first",
+    "design-it/vaporwave",
+    "design-it/vibrant-maximalism",
+    "design-it/widget-based-design",
+    "design-it/y2k-design",
     "design-md",
     "design-orchestration",
     "design-spells",
@@ -519,6 +573,7 @@
     "development",
     "devops-deploy",
     "devops-troubleshooter",
+    "diagnosing-bugs",
     "diary",
     "differential-review",
     "discord-automation",
@@ -540,6 +595,7 @@
     "docusign-automation",
     "docx-official",
     "domain-driven-design",
+    "domain-modeling",
     "dos-verify-done-claims",
     "dotnet-architect",
     "dotnet-backend",
@@ -719,8 +775,12 @@
     "grafana-dashboards",
     "graphql",
     "graphql-architect",
+    "grill-me",
+    "grill-with-docs",
+    "grilling",
     "growth-engine",
     "grpc-golang",
+    "handoff",
     "hasdata",
     "hasdata-cli",
     "haskell-pro",
@@ -777,8 +837,10 @@
     "idor-testing",
     "ii-commons",
     "ilya-sutskever",
+    "image-generator",
     "image-studio",
     "imagen",
+    "improve-codebase-architecture",
     "incident-responder",
     "incident-response-incident-response",
     "incident-response-smart-fix",
@@ -842,6 +904,7 @@
     "latex-paper-conversion",
     "launch-strategy",
     "lead-magnets",
+    "learn",
     "legacy-modernizer",
     "legal-advisor",
     "leiloeiro-avaliacao",
@@ -851,6 +914,7 @@
     "leiloeiro-mercado",
     "leiloeiro-risco",
     "lemmaly",
+    "lesson-generator",
     "lex",
     "libreoffice/base",
     "libreoffice/calc",
@@ -875,6 +939,7 @@
     "llm-application-dev-ai-assistant",
     "llm-application-dev-langchain-agent",
     "llm-application-dev-prompt-optimize",
+    "llm-council",
     "llm-evaluation",
     "llm-ops",
     "llm-prompt-optimizer",
@@ -887,6 +952,7 @@
     "longbridge",
     "lookdev",
     "lookdev-auto",
+    "loop-library",
     "loss-aversion-designer",
     "lovable-cleanup",
     "m365-agents-dotnet",
@@ -899,6 +965,10 @@
     "magic-animator",
     "magic-ui-generator",
     "mailchimp-automation",
+    "mailtrap-managing-contacts",
+    "mailtrap-sending-emails",
+    "mailtrap-setting-up-sending-domain",
+    "mailtrap-testing-with-sandbox",
     "make-automation",
     "makepad-animation",
     "makepad-basics",
@@ -1136,6 +1206,7 @@
     "prompt-library",
     "protect-mcp-governance",
     "protocol-reverse-engineering",
+    "prototype",
     "pubmed-database",
     "puzzle-activity-planner",
     "pydantic-ai",
@@ -1292,6 +1363,7 @@
     "server-management",
     "service-mesh-expert",
     "service-mesh-observability",
+    "setup-matt-pocock-skills",
     "sexual-health-analyzer",
     "shadcn",
     "shader-programming-glsl",
@@ -1392,6 +1464,7 @@
     "super-code/typescript",
     "superpowers-lab",
     "supply-chain-risk-auditor",
+    "survey-generator",
     "sveltekit",
     "swift-concurrency-expert",
     "swiftui-expert-skill",
@@ -1408,6 +1481,7 @@
     "task-intelligence",
     "tavily-web",
     "tcm-constitution-analyzer",
+    "tdd",
     "tdd-orchestrator",
     "tdd-workflow",
     "tdd-workflows",
@@ -1415,6 +1489,7 @@
     "tdd-workflows-tdd-green",
     "tdd-workflows-tdd-red",
     "tdd-workflows-tdd-refactor",
+    "teach",
     "team-collaboration-issue",
     "team-collaboration-standup-notes",
     "team-composition-analysis",
@@ -1452,15 +1527,19 @@
     "threejs-textures",
     "tiktok-automation",
     "tmux",
+    "to-issues",
+    "to-prd",
     "todoist-automation",
     "tokenwise",
     "tool-design",
     "tool-use-guardian",
+    "tools-page-seo-optimizer",
     "top-web-vulnerabilities",
     "track-management",
     "transformers-js",
     "travel-health-analyzer",
     "trello-automation",
+    "triage",
     "trigger-dev",
     "trpc-fullstack",
     "trust-calibrator",
@@ -1552,6 +1631,7 @@
     "whatsapp-automation",
     "whatsapp-cloud-api",
     "wiki-architect",
+    "wiki-builder",
     "wiki-changelog",
     "wiki-onboarding",
     "wiki-page-writer",
@@ -1571,6 +1651,7 @@
     "workflow-orchestration-patterns",
     "workflow-patterns",
     "wrike-automation",
+    "writing-great-skills",
     "writing-plans",
     "writing-skills",
     "x-article-publisher-skill",
@@ -1584,10 +1665,12 @@
     "yann-lecun-debate",
     "yann-lecun-filosofia",
     "yann-lecun-tecnico",
+    "yao-meta-skill",
     "yes-md",
     "yield-intelligence",
     "youtube-automation",
     "youtube-full",
+    "youtube-notetaker",
     "youtube-seo-optimizer",
     "youtube-summarizer",
     "zapier-make-patterns",

package/bundled-skills/2slides-ppt-generator/SKILL.md

@@ -47,7 +47,14 @@ Users must have a 2slides API key and credits:
 3. **Set API Key:** Store the key in environment variable: `SLIDES_2SLIDES_API_KEY`
 
 ```bash
-export SLIDES_2SLIDES_API_KEY="your_api_key_here"
+read -r -s SLIDES_2SLIDES_API_KEY
+export SLIDES_2SLIDES_API_KEY
+```
+
+4. **Install Script Dependencies:** From this skill directory, install the pinned local requirements before using the Python scripts:
+
+```bash
+python -m pip install -r requirements.txt
 ```
 
 **Credit Costs:**
@@ -274,12 +281,6 @@ Section 2: [Subtopic]
 
 Use the `create_pdf_slides.py` script:
 
-Install the Python dependency first if it is not already available:
-
-```bash
-python -m pip install -r requirements.txt
-```
-
 ```bash
 # Basic generation
 python scripts/create_pdf_slides.py --content "Your content here"

package/bundled-skills/android-cli/SKILL.md

@@ -2,17 +2,23 @@
 name: android-cli
 description: Orchestrates Android development tasks including project creation, deployment, SDK management, and environment diagnostics using the `android` command-line tool.
 category: tools
-risk: safe
+risk: critical
 source: self
 source_type: self
 date_added: "2026-06-15"
 author: Owais
 tags: [android, cli, adb, mobile, build, emulator]
 tools: [claude, cursor, gemini, antigravity]
+plugin:
+  targets:
+    codex: blocked
+    claude: blocked
+  setup:
+    type: manual
+    summary: "Installer guidance executes remote Android CLI setup scripts; keep out of plugin-safe bundles."
+    docs: SKILL.md
 ---
 
-<!-- security-allowlist: curl-pipe-bash -->
-
 # Android CLI Specialist
 
 This skill provides instructions for using the `android` CLI tool. The tool includes various commands for creating projects, running applications, interacting with devices, and managing the CLI environment.
@@ -26,11 +32,17 @@ This skill provides instructions for using the `android` CLI tool. The tool incl
 
 ## Installation
 
-If the `android` tool is not in the path, install it. To install, run the following command:
+If the `android` tool is not in the path, download the platform installer to a private temporary directory, inspect it, then run it only after the user confirms the source and contents:
+
+```bash
+tmpdir="$(mktemp -d "${TMPDIR:-/tmp}/android-cli.XXXXXX")" || exit 1
+curl -fsSL https://dl.google.com/android/cli/latest/linux_x86_64/install.sh -o "$tmpdir/install.sh"
+sed -n '1,160p' "$tmpdir/install.sh"
+# After review and explicit user confirmation:
+bash "$tmpdir/install.sh"
+```
 
-- **Linux:** `curl -fsSL https://dl.google.com/android/cli/latest/linux_x86_64/install.sh | bash`
-- **macOS:** `curl -fsSL https://dl.google.com/android/cli/latest/darwin_arm64/install.sh | bash`
-- **Windows:** `curl.exe -fsSL https://dl.google.com/android/cli/latest/windows_x86_64/install.cmd -o "%TEMP%\i.cmd" && "%TEMP%\i.cmd"`
+Use the matching `darwin_arm64/install.sh` or `windows_x86_64/install.cmd` URL for macOS or Windows. Do not pipe mutable network installer scripts directly into a shell.
 
 ## SDK Management
 

package/bundled-skills/android-ui-journey-testing/SKILL.md

@@ -0,0 +1,191 @@
+---
+name: android-ui-journey-testing
+description: "XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting."
+category: testing
+risk: critical
+source: self
+source_type: self
+date_added: "2026-06-18"
+author: Owais
+tags: [android, journey-testing, ui-verification, testing, adb, automation]
+tools: [claude, cursor, gemini, antigravity]
+---
+
+# Android UI Journey Testing
+
+## Overview
+
+This skill outlines the standard workflow for running XML-specified User Journey tests on Android applications. A "journey" is a sequenced set of user actions and state assertions designed to verify end-to-end functionality. The journey XML acts as the source of truth for the app's behavior. The executor proceeds sequentially, performing UI interactions, checking state assertions, and writing a standardized JSON outcome report.
+
+## When to Use
+
+- Use when evaluating an Android application's UI behavior against an XML test specification.
+- Use when automating multi-step user flows (e.g., login, checkout, navigation) and verifying expectations.
+- Use when running verification tests and generating standardized JSON test reports.
+- Use when debugging application flows on physical devices or emulators using ADB commands.
+
+## How It Works
+
+```mermaid
+graph TD
+    A[Parse Journey XML] --> B[Execute Action / Interaction]
+    B --> C{Success?}
+    C -- Yes --> D[Verify State Expectation / Assertion]
+    C -- No/Crash --> G[Mark FAILED & Exit]
+    D -- Passed --> E{More Steps?}
+    D -- Failed --> G
+    E -- Yes --> B
+    E -- No --> F[Output JSON Summary]
+```
+
+### Step 1: Parse the Journey Specification
+Read and parse the XML test suite structure. The root node `<journey>` defines the test case name, and the `<actions>` block contains the sequence of test steps.
+
+```xml
+<journey name="Search and Cart Flow">
+   <description>Verify that searching for an item and adding it to the cart succeeds.</description>
+   <actions>
+      <action>Search for soda</action>
+      <action>Tap the first search result</action>
+      <action>Verify that the product detail screen is shown</action>
+   </actions>
+</journey>
+```
+
+### Step 2: Sequential Step Evaluation
+Process each `<action>` element in the exact order specified. Test steps are classified into two groups:
+
+#### A. Interactive Actions (Taps, Swipes, Text Input)
+Perform the physical UI interaction using ADB.
+- **Tapping**: Tap the center of the target element's bounds:
+  ```bash
+  adb shell input tap <x> <y>
+  ```
+- **Swiping/Scrolling**: Swipe from coordinate to coordinate with a duration:
+  ```bash
+  adb shell input swipe <x1> <y1> <x2> <y2> <duration_ms>
+  ```
+- **Text Typing**: Type text into the active input field:
+  ```bash
+  adb shell input text "<string>"
+  ```
+If the element is missing or the action cannot be performed, the action and the journey fail.
+
+#### B. State Assertions (Expectation Verification)
+Steps beginning with "verify", "check", or "ensure" represent state assertions. 
+- Inspect the current screen (using screenshots or `uiautomator dump`) without interacting or scrolling.
+- Confirm all sub-assertions are met. For example, *"Verify that the app is on the Home screen and the logo is visible"* fails if the home screen is not displayed **or** the logo is missing.
+
+### Step 3: Handle Failures and Crashes
+If the application crashes, exits, freezes, or fails an assertion:
+1. Immediately stop journey execution.
+2. Mark the failed step as `FAILED`.
+3. Mark any subsequent steps as `SKIPPED`.
+4. Document the exact reason for failure.
+
+### Step 4: Generate JSON Report
+Format the execution results into a standardized JSON schema and write it to the output log.
+
+---
+
+## Examples
+
+### Example 1: Full Journey XML Specification
+
+```xml
+<journey name="Login and Profile Edit">
+   <description>Logs into the app, navigates to settings, and changes user profile information.</description>
+   <actions>
+      <action>Verify that the username input field is visible</action>
+      <action>Tap the username input field</action>
+      <action>Type "testuser" into the input</action>
+      <action>Tap the password input field</action>
+      <action>Type a redacted test password into the input</action>
+      <action>Tap the "Login" button</action>
+      <action>Verify that the Home dashboard is visible and user profile photo is shown</action>
+   </actions>
+</journey>
+```
+
+### Example 2: Standard JSON Outcome Report
+
+```json
+{
+  "journey": "Login and Profile Edit",
+  "results": [
+    {
+      "action": "Verify that the username input field is visible",
+      "status": "PASSED",
+      "commands": [],
+      "comment": "Username input detected at bounds [100,200][980,300] via UI dump."
+    },
+    {
+      "action": "Tap the username input field",
+      "status": "PASSED",
+      "commands": [
+        "adb shell input tap 540 250"
+      ],
+      "comment": "Tapped center coordinates of username input."
+    },
+    {
+      "action": "Type \"testuser\" into the input",
+      "status": "PASSED",
+      "commands": [
+        "adb shell input text \"testuser\""
+      ],
+      "comment": "Username typed successfully."
+    },
+    {
+      "action": "Tap the password input field",
+      "status": "PASSED",
+      "commands": [
+        "adb shell input tap 540 370"
+      ],
+      "comment": "Tapped center of password input."
+    },
+    {
+      "action": "Type a redacted test password into the input",
+      "status": "PASSED",
+      "commands": [
+        "adb shell input text \"[REDACTED_PASSWORD]\""
+      ],
+      "comment": "Password typed successfully. The actual input value was not stored in the report."
+    },
+    {
+      "action": "Tap the \"Login\" button",
+      "status": "PASSED",
+      "commands": [
+        "adb shell input tap 540 500"
+      ],
+      "comment": "Login button clicked."
+    },
+    {
+      "action": "Verify that the Home dashboard is visible and user profile photo is shown",
+      "status": "FAILED",
+      "commands": [],
+      "comment": "Dashboard loaded but profile photo was missing from the UI header."
+    }
+  ]
+}
+```
+
+---
+
+## Best Practices
+
+- ✅ **Calculate Centers for Taps**: When parsing element bounds like `[x1,y1][x2,y2]`, always compute the middle coordinate:
+  $$x_{center} = \frac{x_1 + x_2}{2}, \quad y_{center} = \frac{y_1 + y_2}{2}$$
+- ✅ **Include Sleep Buffers**: Always add a short delay (e.g., 1-2 seconds) after interactive actions (like button taps) to let layouts and transitions render before executing assertions.
+- ✅ **Fail Fast**: Stop the test immediately upon encountering the first failure. Continuing after a failure leads to invalid results.
+- ✅ **Log Precise Commands Safely**: Include non-sensitive raw commands (such as `adb shell input tap`) in the JSON output list for diagnostics. Redact text entered into password, OTP, token, payment, or personal-data fields; never persist the literal secret in reports, CI logs, or shared artifacts.
+
+## Limitations
+
+- The parser only evaluates the static screen hierarchy (e.g. `uiautomator dump`). Elements that require scrolling are marked as not visible unless a scrolling action is explicitly performed.
+- Non-standard UI components (like custom OpenGL canvas views) cannot be read via standard accessibility trees and may require screenshot analysis or hardcoded click maps.
+- Key events and text typing via ADB do not trigger standard soft keyboard events on all emulator images, which can lead to input validation issues.
+
+## Related Skills
+
+- `@android-cli` - General CLI tool syntax, package install, and device queries.
+- `@android_ui_verification` - Direct ADB script templates for general UI checks.

package/bundled-skills/apple-notes-search/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: apple-notes-search
 description: "Semantic + keyword search and connection-discovery across the user's own Apple Notes via the apple-notes MCP server. Use when the user wants to find, recall, or synthesize something from their notes, or surface non-obvious bridges/related notes. macOS, on-device."
-risk: safe
+risk: critical
 source: community
 source_repo: connerkward/mcp-apple-notes
 source_type: community
@@ -11,6 +11,14 @@ tags: [apple-notes, search, mcp, macos, semantic-search, knowledge]
 tools: [claude-code]
 license: "MIT"
 license_source: "https://github.com/connerkward/mcp-apple-notes/blob/main/LICENSE"
+plugin:
+  targets:
+    codex: blocked
+    claude: blocked
+  setup:
+    type: manual
+    summary: "Requires third-party MCP setup and macOS Full Disk Access; keep out of plugin-safe bundles."
+    docs: SKILL.md
 ---
 
 # Apple Notes search & connection-discovery
@@ -50,7 +58,9 @@ Disk Access. Steps, in order:
 2. **Clone + install deps:**
    ```bash
    git clone https://github.com/connerkward/mcp-apple-notes
-   cd mcp-apple-notes && bun install
+   cd mcp-apple-notes
+   git checkout <reviewed-tag-or-commit>
+   bun install
    ```
 3. **Grant Full Disk Access to bun.** Run `which bun`, then open System Settings →
    Privacy & Security → Full Disk Access, click `+`, and add that exact `bun` binary

package/bundled-skills/ask-matt/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: ask-matt
+description: Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
+disable-model-invocation: true
+category: "productivity"
+risk: "safe"
+source: "community"
+source_repo: "mattpocock/skills"
+source_type: "community"
+date_added: "2026-06-19"
+author: "Matt Pocock"
+license: "MIT"
+license_source: "https://github.com/mattpocock/skills/blob/main/LICENSE"
+tags:
+  - productivity
+  - workflow
+  - coding-agents
+tools:
+  - claude-code
+  - codex-cli
+  - cursor
+---
+
+# Ask Matt
+
+## When to Use
+
+Use when this workflow matches the user request: Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
+
+
+_Source: [mattpocock/skills](https://github.com/mattpocock/skills) (MIT)._
+
+You don't remember every skill, so ask.
+
+A **flow** is a path through the skills. Most paths run along one **main flow**, and two **on-ramps** merge onto it. Everything else is standalone.
+
+## The main flow: idea → ship
+
+The route most work travels. You have an idea and want it built.
+
+1. **`/grill-with-docs`** — sharpen the idea by interview. Start here when you **have a codebase**: it's stateful, retaining what it learns in `CONTEXT.md` and ADRs. (No codebase? Use `/grill-me` — see Standalone.)
+2. **Branch — can you settle every question in conversation?** If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by **`/handoff`** in both directions (see Crossing sessions):
+   - **`/handoff`** out, then open a fresh session against that file,
+   - **`/prototype`** to answer the question with throwaway code,
+   - **`/handoff`** back what you learned, and reference it from the original idea thread.
+3. **Branch — is this a multi-session build?**
+   - **Yes** → **`/to-prd`** (turn the thread into a PRD) → **`/to-issues`** (split the PRD into independently-grabbable issues). Because the issues are independent, **clear context between each one**: start a fresh session per issue and kick off **`/implement`** by passing it the PRD and the single issue to work on.
+   - **No** → **`/implement`** right here, in the same context window.
+
+### Context hygiene
+
+Keep steps 1–3 in **one unbroken context window** — don't compact or clear until after `/to-issues` — so the grilling, PRD, and issues all build on the same thinking. Each `/implement` then starts fresh, working from the issue.
+
+The limit on this is the **[smart zone](https://www.aihero.dev/ai-coding-dictionary/smart-zone)**: the window (~120k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before `/to-issues`, don't push on degraded — `/handoff` and continue in a fresh thread.
+
+## On-ramps
+
+A starting situation that generates work, then merges onto the main flow.
+
+- **Bugs and requests piling up** → **`/triage`**. It moves issues through triage roles and produces agent-ready issues, which **`/implement`** later picks up.
+
+  Triage is only for issues **you didn't create** — bug reports, incoming feature requests, anything that arrives raw. Issues that `/to-issues` produced are already agent-ready, so **don't triage them**.
+
+## Codebase health
+
+Not feature work — upkeep.
+
+- **`/improve-codebase-architecture`** — run whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces deepening opportunities; picking one _generates an idea_ you can take into the main flow at `/grill-with-docs`.
+
+## Crossing sessions
+
+- **`/handoff`** — when a thread is full or you need to branch off (e.g. into a `/prototype` session), this compacts the conversation into a markdown file. You don't continue in place — you **open a new session and reference that file** to carry the context across. It's the bridge between context windows, in either direction. Use it when you want a **fresh session** but need the **current conversation preserved**.
+- **`/compact`** (built-in) — stay in the **same conversation**, letting the earlier turns be summarized. Use it at **intentional breaks between phases**, when you don't mind losing the verbatim history. Don't compact mid-phase — the agent can lose its way. `/handoff` forks; `/compact` continues.
+
+## Standalone
+
+Off the main flow entirely.
+
+- **`/grill-me`** — the same relentless interview as `/grill-with-docs`, but for when you have **no codebase**. Stateless: it saves nothing locally, builds no `CONTEXT.md`. Reach for it to sharpen any plan or design that doesn't live in a repo.
+- **`/teach`** — learn a concept over multiple sessions, using the current directory as a stateful workspace.
+- **`/writing-great-skills`** — reference for writing and editing skills well.
+
+## Precondition
+
+**`/setup-matt-pocock-skills`** — run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.
+
+
+## Limitations
+
+- Requires the upstream tool, account, API key, or local setup when the workflow names one.
+- Does not authorize destructive, production, paid, or external-message actions without explicit user approval.
+- Validate generated artifacts or recommendations against the user's real sources before treating them as final.

package/bundled-skills/atlas-ledger/SKILL.md

@@ -12,6 +12,14 @@ metadata:
   version: "2.2.0"
   author: wede-wx
   repository: https://github.com/wede-wx/atlas
+plugin:
+  targets:
+    codex: blocked
+    claude: blocked
+  setup:
+    type: manual
+    summary: "Writes durable Atlas.md project memory after confirmation; keep out of plugin-safe bundles."
+    docs: SKILL.md
 ---
 
 # Atlas Ledger v2.2