CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

methodology-advisor

Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./examples/skills/methodology-advisor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

This is a strong, highly actionable skill body: every phase is driven by executable commands, concrete signal tables, and exact question text, with a clean four-phase sequence and a user-input checkpoint before the recommendation. The only real improvements are marginal trimming of the output template and optionally splitting the stack reference or question bank into a reference file.

DimensionReasoningScore

Conciseness

The body is efficient throughout — terse bash commands with one-line comments, a signal table, and a question bank with no explanations of concepts Claude already knows — though the Phase 4 output template and repeated "pick the most relevant" phrasing could be trimmed slightly.

4 / 5

Actionability

Everything is copy-paste ready: executable bash commands for each analysis step, concrete fit signals per stack in the scoring table, exact question wording in the bank, and a filled-in output template with per-stack quick-start mappings in the reference section.

5 / 5

Workflow Clarity

The four phases are clearly sequenced (silent analysis → scoring → ask exactly 3 questions → recommend) with an explicit user checkpoint in Phase 3 (present a preliminary picture before finalizing), but there is no validation or re-scoring feedback loop for the stack-selection decision itself.

4 / 5

Progressive Disclosure

The body is well organized into one-level, clearly headed phases with no nested references, and no bundle files exist to misnavigate; the minor gap is that the "(internal)" stack reference and question bank — ~190 lines total — could be externalized to keep SKILL.md leaner.

4 / 5

Total

17

/

20

Passed

Description

53%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 communicates a clear, fairly specific capability (codebase analysis plus exactly 3 questions leading to a methodology recommendation), but it omits any "Use when..." trigger guidance and uses second-person voice ("your codebase"), both of which the rubric penalizes. Its natural-keyword coverage is adequate but thin on the synonyms users would realistically utter.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks which AI development methodology, workflow, or stack to adopt, or mentions spec-driven development, TDD setup, or team process for AI coding."

Include natural synonyms users would say, such as "development workflow", "AI coding process", or "methodology quiz", to broaden trigger-term coverage.

Rewrite in third person ("Analyzes the codebase and asks 3 targeted questions...") to avoid the second-person voice penalty.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("Analyzes your codebase", "asks 3 targeted questions", "recommend the right AI-assisted development methodology stack"), which matches the several-specific-actions level, but the second-person phrasing "your codebase" triggers the rubric's mandated 1-point voice penalty, landing it at the domain-plus-actions level.

3 / 5

Completeness

The "what" is clear (analyze codebase, ask 3 questions, recommend a stack), but there is no "Use when..." clause or equivalent trigger guidance, which the rubric explicitly caps at 3.

3 / 5

Trigger Term Quality

It includes some relevant keywords ("codebase", "AI-assisted development", "methodology stack") but misses the natural phrases and synonyms a user would actually say, such as "development workflow", "spec-driven development", or "which process should we use".

3 / 5

Distinctiveness Conflict Risk

"AI-assisted development methodology stack" carves out a mostly distinct niche with only minor overlap risk against adjacent process/architecture advisory skills; it is not fully distinct because the absent trigger guidance weakens separation from related skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

FlorianBruniaux/claude-code-ultimate-guide

Path

examples/skills/methodology-advisor/SKILL.md

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.