intel-discipline-advisor

Triage a competitive or market question into the right intelligence disciplines, cadence, and executing skill. Use when you know something needs researching but not which channel to run.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/intel-discipline-advisor/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized interactive triage skill with a concrete routing table, worked example, and clear adaptive-question workflow. The main gap is that referenced bundle files (template.md, examples/conversation-flow.md, examples/conversation-flow-industrial.md) are not present in the bundle to verify navigation.

Suggestions

Either include the referenced bundle files (template.md, examples/conversation-flow.md, examples/conversation-flow-industrial.md) or remove/qualify the links so progressive disclosure is verifiable.

Add one explicit validation/recovery checkpoint for the interactive flow (e.g., what to do when a user's answer doesn't map to any branch) to push workflow clarity to 5.

Trim a few rhetorical framing sentences (e.g., 'Running every discipline on every question is the failure mode; scoping to the decision is the craft.') to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence — it skips defining what OSINT/FININT are and routes via a tight table — but a few explanatory passages ('Running every discipline on every question is the failure mode') could be trimmed.	4 / 5
Actionability	Concrete routing table maps each situation to a discipline mix and named executing skill, plus a worked sample flow with specific free sources (patents.google.com, crt.sh, arXiv); it stops short of fully copy-paste commands because the skill is interactive/triage rather than script-driven.	4 / 5
Workflow Clarity	The 3-question adaptive flow is clearly sequenced with explicit branching by answer and a synthesis step, plus an off-ramp; missing one explicit validation/recovery checkpoint for the interactive turn-taking, hence just below 5.	4 / 5
Progressive Disclosure	Well-structured overview pointing one level deep to companion skills and an examples file (conversation-flow.md, conversation-flow-industrial.md), with a routing table inline that earns its place; however the referenced template.md and examples/*.md bundle files do not exist in this bundle, so navigation is only partially verifiable.	4 / 5
	Total	16 / 20 Passed

Description

63%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states both what the skill does and when to use it, with a distinct routing niche. It is held back by trigger-term coverage that leans on one phrasing rather than the natural vocabulary users actually say.

Suggestions

Add concrete natural trigger terms users would say, e.g. 'Use when a competitor seems to be making a move, when planning a battle card or TAM refresh, or when deciding where limited competitive-intel hours should go.'

Consider naming one or two artifacts the skill routes toward (battle card, TAM/SAM/SOM) in the description to sharpen the 'what' beyond the abstract triage framing.

Dimension	Reasoning	Score
Specificity	Quotes 'Triage a competitive or market question into the right intelligence disciplines, cadence, and executing skill' naming the triage domain plus three concrete routing actions (discipline, cadence, skill), though it omits the artifact-handoff detail found in the body.	4 / 5
Completeness	Explicitly answers 'what' (triage into disciplines/cadence/skill) and 'when' ('Use when you know something needs researching but not which channel to run'); the when clause is present and specific but could name more concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes some natural triggers like 'competitive or market question' and 'you know something needs researching but not which channel to run', but lacks common synonyms users would actually say (e.g., 'competitor analysis', 'competitive intel', 'battle card') found only in the body.	3 / 5
Distinctiveness Conflict Risk	The triage/routing niche ('knows something needs researching but not which channel') is distinct from the executing skills it routes to, with only minor overlap risk with the compendium skill it references.	4 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 missing, 31 suspicious	Warning

	Total	14 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/intel-discipline-advisor/SKILL.md
Commit: 1b5a524

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.