tool-market-scout
Skill1 starsChanged 17 days agoMITView on GitHub
JTBD brief to community scan to scoring to verdict Buy / Build / Hybrid / Defer. Triggers tool-market-scout, buy vs build, tool market scan. Delegates scan to tool-scout.
In this repository6 other files it gives its agents.
- canvas-to-htmlSkill
- criticSkill
- human-doc-voiceSkill
- local-llmSkill
- pipelineSkill
- prompt-engineerSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 9 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
If the user named a package and only wants docs/API → stop, wrong skill.
- Distinctive: line 38
If trigger = product to replace → Step 1a, not alternatives search.
- Very specific: line 51
Do not: run your own WebSearch/multi-source scan.
- Very specific: line 56
If tool-scout is not installed → ask once: npx skills add LpcPaul/tool-scout-skill.
- Distinctive: line 70
If stake = no → shortlist only.
- Very specific: line 74
If the user wants a note: Research/Tooling/{topic-slug}.md from references/output-template.md (or path they name).
- Distinctive: line 78
No scan without confirmed JTBD brief
- Distinctive: line 79
No primary «alternatives to {brand}»
- Distinctive: line 80
No reimplementing tool-scout scan
- Distinctive: line 81
No verdict without scoring when buy-or-build stake
- Distinctive: line 82
No auto-Buy; verdict waits for ack
- Distinctive: line 88
When stake: scoring with evidence + verdict with ack
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Scan: https://github.com/LpcPaul/tool-scout-skill (LpcPaul) --><!-- Verdict rubric: https://mm.dreamineering.com/playbook/applications/select-tech/ (Dreamineering) -->Tool Market Scout
JTBD brief → community scan (tool-scout) → scoring → verdict Buy / Build / Hybrid / Defer.
{SKILL_DIR} = directory of this SKILL.md.
Scope
In: choosing SaaS, desktop/mobile, OSS lib, MCP/skill; constraints (platform, budget, OSS-only, data sovereignty)
Out: docs lookup for an already named package, product strategy for a whole market, customer interviews, internal service TDR
Fallback: if candidates <2 → Build or widen JTBD
Gotchas
- JTBD brief + ack before scan –
references/jtbd-decompose.md - No primary «alternatives to {brand}» – capability queries from functional jobs
- Do not reimplement scan – delegate to
tool-scout(Step 2) - Scoring + verdict – only when ≥2 candidates and buy-or-build stake
- No auto-Buy – verdict waits for ack
- Stars ≠ quality –
references/scoring-rubric.md
Algorithm
Step 0: Intake + scope gate
Collect trigger, constraints, must-have capabilities, buy-or-build stake (yes/no).
If the user named a package and only wants docs/API → stop, wrong skill.
If trigger = product to replace → Step 1a, not alternatives search.
Step 1a: Native audit (if a product is named)
Official docs/features → functional jobs, not marketing. Format – references/jtbd-decompose.md.
Step 1b: JTBD brief (gate)
Job statement, functional jobs, constraints, out of scope, buy-or-build stake.
STOP. Show the user. Wait for «ok» / edits. No ack – no scan.
Step 2: Community scan (tool-scout)
Do not run your own WebSearch/multi-source scan. Invoke / run the installed tool-scout skill with capability queries from the brief.
- Query = capability-first from functional jobs (
references/search-sources.md) - Supplementary
{brand} alternatives– max 1, after brief only - CLI, flags, and scripts for
tool-scoutlive in LpcPaul/tool-scout-skill only; do not duplicate here - If
tool-scoutis not installed → ask once:npx skills add LpcPaul/tool-scout-skill; then rerun via the skill. Fallback: minimal capability search (no full scan reimplementation)
Normalize to candidate table (name, type, OSS/paid, source URL, covers jobs).
Step 3: Score (conditional)
Only if ≥2 candidates and buy-or-build stake = yes.
Rubric – references/scoring-rubric.md. ≥3 candidates + Build yourself row. Evidence required per score.
Step 4: Verdict (gate)
Only if Step 3 ran. Buy | Build | Hybrid | Defer; top pick; risks; next step; how to start.
STOP. Show scoring + verdict. Wait for ack. No auto-Buy.
If stake = no → shortlist only; offer verdict on request.
Step 5: Writeback (optional)
If the user wants a note: Research/Tooling/{topic-slug}.md from references/output-template.md (or path they name). Skip if chat-only.
Hard Stop Rules
- No scan without confirmed JTBD brief
- No primary «alternatives to {brand}»
- No reimplementing tool-scout scan
- No verdict without scoring when buy-or-build stake
- No auto-Buy; verdict waits for ack
Definition of Done
- JTBD brief confirmed
- Scan via tool-scout (or install prompt + fallback)
- When stake: scoring with evidence + verdict with ack
- URLs are markdown links to primary sources
Check commands
SKILL_DIR="<path-to-this-skill>"
ls "$SKILL_DIR/references"/*.mdDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

