CtrlK
BlogDocsLog inGet started
Tessl Logo

advisor-workflow

Cost-and-speed-optimized development workflow for a cheap fast implementing model consulting expensive advisor subagents (design-advisor, principal-advisor, quality-reviewer). Use for design-bearing or high-risk implementation - new/changed public contracts, schemas, state/lifecycle, concurrency, security, persistence, compatibility - or after repeated failed attempts. Do not invoke for trivial edits or solely because a change touches multiple files.

69

Quality

84%

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

81%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-structured, actionable workflow with strong sequencing and validation checkpoints tailored to high-risk work. Conciseness and progressive disclosure are good but not maximal, given dense prose and the absence of any split-out reference material.

Suggestions

Tighten a few compound sentences in 'Workflow' and 'Cost and latency principles' (e.g., the long principal-advisor mode paragraph) to lift conciseness toward 5.

Add one concrete Task-tool invocation example showing the blocking-vs-background launch to make actionability copy-paste ready.

Consider extracting the context-packet template into a referenced file or a tighter fenced block so the core workflow reads leaner.

DimensionReasoningScore

Conciseness

Dense and information-rich, assuming Claude's competence without explaining basic concepts, though a few compound sentences could be tightened without losing meaning.

4 / 5

Actionability

Provides a literal context-packet template, a triage taxonomy with explicit routing, an advisor table with default consult counts, and concrete rules ('stash your diff and re-run'); absent exact Task-tool invocation syntax is the main gap.

4 / 5

Workflow Clarity

A clearly sequenced six-step workflow with time budgets, explicit validation checkpoints (runtime evidence in step 5, mandatory end review in step 6), an escalation valve after two failed hypotheses, and re-review/re-validation feedback loops for high-risk changes.

5 / 5

Progressive Disclosure

Well-organized into clear sections with no nested references and no bundle files to mismanage; sits just above the simple-skill line, so a couple of dense inline sections keep it from a perfect score.

4 / 5

Total

17

/

20

Passed

Description

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

A strong description that clearly states what the skill does and when to use it, with concrete trigger contexts and explicit negative guidance. Minor room to sharpen the distinct capabilities versus the when-to-use framing.

DimensionReasoningScore

Specificity

Names the domain and several concrete contexts (consulting design-advisor/principal-advisor/quality-reviewer; new/changed public contracts, schemas, state/lifecycle, concurrency, security, persistence, compatibility) with comprehensive trigger coverage, but the stated actions lean more toward when-to-use than distinct capabilities.

4 / 5

Completeness

Explicitly answers both what (a cost-and-speed-optimized workflow consulting advisor subagents) and when ('Use for design-bearing or high-risk implementation... or after repeated failed attempts'), plus an explicit negative trigger ('Do not invoke for trivial edits...').

5 / 5

Trigger Term Quality

Includes natural developer-facing terms like 'design-bearing', 'high-risk implementation', 'failed attempts', 'schemas', 'concurrency', and 'security' that users would plausibly say, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (advisor-consultation workflow under a specific model-cost regime) with distinct positive triggers and explicit anti-triggers that minimize overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
reactive/data-client
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.