mcp-opportunity-pipeline
Automatically invoke MCP opportunity discovery and publication pipeline when discussing marketplace opportunities, automation tools, or MCP server development
What this skill does
# MCP Opportunity Pipeline Skill
Automatically activate when the user asks about:
- Finding MCP or automation tool opportunities
- Validating product ideas against Reddit/forums
- Building MCP servers for Apify or similar platforms
- Analyzing marketplace gaps
- Publishing to Apify, Smithery, or other MCP marketplaces
## When to Invoke
### Discovery & Research
**Triggers:** "find opportunities", "market research", "what should I build", "MCP ideas"
**Action:** Use `/mcp-pipeline:discover` to scrape marketplaces
### Gap Analysis
**Triggers:** "analyze gaps", "score opportunities", "which is best"
**Action:** Use `/mcp-pipeline:analyze-gaps` on discovery results
### Validation
**Triggers:** "validate idea", "check Reddit", "real demand", "people want"
**Action:** Use `/mcp-pipeline:validate` against Reddit pain signals
### Specification
**Triggers:** "write spec", "plan build", "what features"
**Action:** Use `/mcp-pipeline:spec` for validated opportunities
### Building
**Triggers:** "build it", "implement", "create actor", "scaffold"
**Action:** Use `/mcp-pipeline:build` from spec
### Testing
**Triggers:** "test it", "QA", "does it work", "verify"
**Action:** Use `/mcp-pipeline:qa` on built code
### Publishing
**Triggers:** "publish", "deploy", "ship it", "launch"
**Action:** Use `/mcp-pipeline:package` then `/mcp-pipeline:publish`
### Full Pipeline
**Triggers:** "full pipeline", "end-to-end", "run everything"
**Action:** Use `/mcp-pipeline:run` with appropriate parameters
## Pre-Check Behavior
Before running expensive operations:
1. **Check for existing outputs:**
```
outputs/discover/ → Skip discover if recent data exists
outputs/analyze/ → Skip analyze if recent analysis exists
outputs/validate/ → Skip validate if recent validation exists
```
2. **Suggest incremental runs:**
- If discovery exists but not analysis, suggest `/mcp-pipeline:analyze-gaps`
- If validation exists but not spec, suggest `/mcp-pipeline:spec`
3. **Warn about costs:**
- Discovery scrapes multiple sites (rate limits)
- Validation searches Reddit (API usage)
- Building creates deployable code
## Configuration Reference
Load from `.claude-plugin/config.json`:
- Marketplace settings
- Subreddit lists
- Scoring weights
- QA thresholds
- Publishing settings
## Output Locations
| Stage | Output Path |
|-------|------------|
| Discover | `outputs/discover/raw-opportunities-{date}.json` |
| Analyze | `outputs/analyze/gap-opportunities-{date}.json` |
| Validate | `outputs/validate/validated-opportunities-{date}.json` |
| Spec | `outputs/spec/{name}-spec.md` |
| Build | `outputs/build/{name}/` |
| QA | `outputs/qa/{name}-qa-report.json` |
| Package | `outputs/package/{name}/` |
| Publish | `outputs/publish/publication-log.json` |
## Example Conversations
### "I want to find MCP opportunities"
→ Check if recent discovery exists
→ If not, run `/mcp-pipeline:discover --phase casual`
→ Then suggest `/mcp-pipeline:analyze-gaps`
### "Which opportunity should I build?"
→ Check if analysis exists
→ Present top opportunities with scores
→ Suggest validation for top picks
### "Build the Notion sync tool"
→ Check if spec exists
→ If not, generate spec first
→ Run `/mcp-pipeline:build --name notion-sync`
→ Then run QA
### "I want to ship something to Apify this week"
→ Run full pipeline: `/mcp-pipeline:run --phase casual --target apify`
→ Stop at each stage for approval
→ End with publish (dry-run first)
## Error Recovery
| Error | Recovery |
|-------|----------|
| No discover data | Run discover first |
| Low validation scores | Pivot to different opportunity |
| QA failures | Fix issues, re-run build + QA |
| Publish failure | Check credentials, retry |
## Important Notes
- Always check existing outputs before re-running stages
- Validate ideas before building (save time)
- Use dry-run before actual publish
- Marketing posts require manual review/submission
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.