CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with a clear sequenced workflow and concrete routing logic. It is held back by verbosity in the framing sections and by progressive-disclosure gaps: several referenced files are missing and substantial reference-worthy content (the routing table, full examples) is inlined.

Suggestions

Tighten the Purpose and Key Concepts sections by removing rhetorical restatement (e.g., "Running every discipline on every question is the failure mode; scoping to the decision is the craft") to improve conciseness without losing the routing logic.

Create the referenced bundle files (template.md, examples/conversation-flow.md, examples/conversation-flow-industrial.md) so the signaled references actually resolve, or remove the links if the files will not be shipped.

Consider moving the full routing quick-reference table into a separate reference file linked from the Application section, keeping SKILL.md as a lean overview that points one level deep.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence (no explaining what OSINT/FININT mean), but at ~160 lines it includes rhetorical padding ("Running every discipline on every question is the failure mode; scoping to the decision is the craft") and restates the framing across Purpose and Key Concepts, fitting the score-2 anchor of mostly efficient but could be tightened.

2 / 3

Actionability

Provides literal question scripts, a situation→discipline-mix→executing-skill routing table, and a sample flow citing exact free sources (patents.google.com, crt.sh, Wayback); the guidance is concrete and actionable, which the scoring notes exempt from code requirements for instruction-only skills.

3 / 3

Workflow Clarity

Sequences Q1 → adaptive Q2 branches → Q3 → numbered recommendations with explicit handling of combinations and "tell me more," and involves no destructive/batch operations requiring validation, matching the score-3 anchor of a clear sequenced process.

3 / 3

Progressive Disclosure

References are one-level-deep and clearly signaled, but the referenced bundle files (template.md, examples/conversation-flow.md, examples/conversation-flow-industrial.md) do not exist on disk, and the full routing table plus extended examples are inlined rather than split out, fitting the score-2 anchor of some structure but content that should be separate is inline.

2 / 3

Total

10

/

12

Passed

Description

85%

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 is specific, complete, and distinctive, with an explicit Use-when trigger and third-person voice. Its only weakness is trigger-term quality: the vocabulary is somewhat specialized and misses the plainer phrasings a non-specialist user might say.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Triage a competitive or market question into the right intelligence disciplines, cadence, and executing skill" — matching the score-3 anchor for listing several specific actions, not merely naming a domain.

3 / 3

Completeness

Explicitly answers both what (triage into disciplines/cadence/executing skill) and when ("Use when you know something needs researching but not which channel to run"), matching the score-3 anchor with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes relevant natural terms ("competitive or market question," "needs researching") but leans on specialized jargon ("channel," "disciplines") and misses common lay variations, fitting the score-2 anchor of some relevant keywords but missing variations.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — intelligence-discipline triage routing — with distinct triggers unlikely to fire for an unrelated skill, matching the score-3 anchor.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 missing, 30 suspicious

Warning

Total

14

/

16

Passed

Repository
deanpeters/Product-Manager-Skills
Reviewed

Table of Contents

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.