CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fic-implement-plan

Execute an approved implementation plan phase by phase with verification. Use when the user asks to implement a plan file from thoughts/shared/plans.

Quality

87%

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

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

The body is a lean, well-structured instruction skill with an explicit phased workflow and verification checkpoints. The only notable gaps are the unspecified progress-marker format and the missing failure-handling loop when a phase's verification fails.

DimensionReasoningScore

Conciseness

The ~30-line body is entirely directive with no padding and no explanations of concepts Claude already knows (e.g., "Treat the plan as intent; adapt when reality differs"), so every token earns its place.

5 / 5

Actionability

For an instruction-only skill the guidance is mostly executable — concrete steps, a concrete completion checklist, and a specific command (`fic-validate-plan <plan-path>`) — with the minor gap that "Update progress markers in the plan" does not specify the marker format (e.g., checkboxes).

4 / 5

Workflow Clarity

The 5-step sequence is clear with explicit per-phase validation checkpoints ("Run verification for each phase before moving on", "Do not skip verification between phases") and a pause-and-report rule for plan/reality conflicts, but the recovery path when verification fails is left implicit.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and its content is organized into clear, well-separated sections (Workflow, Rules, Verification, Completion), satisfying the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

82%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 and explicitly states both capability and trigger conditions with a distinctive scope. Its main weakness is limited action coverage and a slightly narrow trigger vocabulary that misses common synonyms like "execute" or "follow the plan".

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions ("Execute an approved implementation plan phase by phase", "with verification") but omits other capabilities the skill performs (resuming partial plans, updating progress markers), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

It explicitly answers both what ("Execute an approved implementation plan phase by phase with verification") and when ("Use when the user asks to implement a plan file from thoughts/shared/plans") with a concrete trigger clause, matching the top anchor.

5 / 5

Trigger Term Quality

It includes several natural, relevant terms ("implement", "implementation plan", "plan file") plus the distinctive path "thoughts/shared/plans", but misses common variations users might say such as "execute the plan", "follow the plan", or "work through the plan".

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — executing approved plans from a specific shared location — with distinct trigger phrasing, so conflict with generic coding or document skills is minimal.

5 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

saski/arnesto

Path

.agents/skills/fic-implement-plan/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.