菜单
Developer-experience review for plugin onboarding. Use when evaluating a plugin's fresh-clone setup, README flow, local testing instructions, prerequisites, bundled CLIs, confusing paths, or contributor experience. Inspired by GStack devex-review and QA workflows.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | plugin-devex-review |
| version | 0.1.0 |
| description | Developer-experience review for plugin onboarding. Use when evaluating a plugin's fresh-clone setup, README flow, local testing instructions, prerequisites, bundled CLIs, confusing paths, or contributor experience. Inspired by GStack devex-review and QA workflows. |
| triggers | ["plugin devex review","review plugin onboarding","fresh clone plugin test","make plugin easier to use","check plugin quickstart"] |
| allowed-tools | ["Read","Bash","Grep","Glob"] |
| mutating | true |
| writes_pages | false |
| writes_to | ["plugins/","README.md"] |
| disable-model-invocation | false |
A devex review produces:
scripts/devex_check.py
(README/skill coverage, --plugin-dir docs, script resolution/compile,
frontmatter name match).Scope
README.md, manifest, and visible skills.git status --short --branch before editing.Fresh-user path
Run the bundled onboarding checker first — it mechanizes the checks below
(README names every real skill and no phantom skills, --plugin-dir is
documented, referenced .py scripts resolve and compile, frontmatter
name matches its directory):
python3 "${CLAUDE_PLUGIN_ROOT}/skills/plugin-devex-review/scripts/devex_check.py" --plugin <plugin-name>
Exit 0 = onboarding mechanics pass; exit 1 = fix each FAIL: line
before continuing. NOTE: lines (e.g. non-executable scripts) are hints,
not blockers.
Verify install command appears in root and plugin docs.
Verify local testing command:
claude --plugin-dir ./plugins/<plugin-name>.
Verify expected first skill invocation is named.
For bundled CLIs, run <tool> --help or the wrapper help command when
safe and available.
Validation path
claude plugin validate plugins/<plugin-name> when available./plugin-manager:plugin-health or its script:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/plugin-health/scripts/plugin_audit.py" --plugin <plugin-name> --json.Experience review
Fix or file
PLUGIN DEVEX REVIEW
Plugin: <name>
Fresh-user path: pass|fail
Time to first success: <duration or not measured>
Validation:
- <command>: pass|fail|not-run
Findings:
- <issue and fix/status>
Docs changed:
- <path>
Follow-up issues:
- <url or none>
Use when the user wants to measure the impact of a campaign that promotes a NEW product to existing customers — phrases like "cross-sell analysis", "cross-sell campaign results", "product attach rate", "account open rate", "new product adoption from campaign", "second product campaign", "add-a-product campaign", "checking-to-savings campaign", "credit card cross-sell", "did the campaign drive new account opens", "attach campaign", or any review of a campaign whose primary goal is to get current customers to take on a product they don't already have. Also trigger on "what was our conversion rate on the X campaign to existing customers" and "compare treated vs holdout for new account opens". Cross-sell differs from up-sell: the headline outcome is a binary CONVERSION (did they open the new product?), and value lift is the revenue or balance from the new product, not growth on existing accounts. Handles both holdout-controlled designs (statistical testing on conversion rate AND value) and uncontrolled designs (d
Use when the user wants to measure the impact of a marketing campaign on existing clients, account owners, or current customers — phrases like "up-sell analysis", "did the campaign move balances", "expansion campaign results", "wallet share lift", "AUM lift", "deposit growth from campaign", "existing customer campaign", "customer growth campaign", "upgrade campaign", "in-book campaign", or any review of a campaign targeted at people who are already customers (so there is no acquisition or conversion-rate question). Also trigger on "how much did balances/sales/revenue go up for treated clients" and "compare treated vs holdout for existing customers". Handles both holdout-controlled designs (statistical testing on the difference) and uncontrolled pre/post designs (descriptive lift only, clearly flagged as non-causal).
Use when initializing, maintaining, validating, searching, documenting, or assembling context from a file-based knowledge base with the bundled vaultli CLI. Trigger on knowledge vaults, KB setup, .kbroot, YAML frontmatter, sidecar markdown, INDEX.jsonl, documenting SQL/templates/configs/scripts, validating stale or broken KB state, searching vault metadata, hydrating source assets, assembling retrieval context, or federated lookup across multiple vault roots.
Manage a file-based knowledge vault with YAML frontmatter, sidecar markdown, and JSONL indexing. Use when initializing or maintaining a knowledge base, attaching metadata to markdown or non-markdown assets, rebuilding or validating INDEX.jsonl, or searching vault records by metadata. Trigger on: "knowledge base", "vault", "frontmatter", "sidecar", "INDEX.jsonl", "document this query/template/skill", "search the vault", or "set up KB docs".
Use this skill when the user wants to plan an analysis before running it, scope analytical work, design an investigation, write an analysis plan, decide what data or metrics are needed, or turn a vague metric/business question into an executable analyst workplan. Trigger on phrases like "analysis planning", "plan this analysis", "how should we analyze", "what data do we need", "design the analysis", "scope this analysis", "analysis plan", "investigation plan", "before we pull data", or "senior analyst, help me plan this".
Use when the user wants to extract data, pull data from a source, load a CSV or JSON export into the workspace, connect a data source, refresh data, ingest raw platform exports, or normalize raw data for the marketing-analytics skills. Trigger on 'extract data', 'pull data from <platform>', 'load CSV/JSON into workspace', 'connect a data source', 'refresh data', 'normalize raw data', 'import my ad export', 'get the campaign data in', or 'set up the workspace'. This is the upstream skill every other marketing-analytics skill depends on: it lands source exports in workspace/raw/ and writes validated, normalized files to workspace/processed/. Run this first when a downstream skill reports a missing or malformed workspace input. When the user wants analysis, modeling, or reporting rather than getting data in, route to the matching analytics skill instead (see references/skill-index.md).