impl

Implement a feature. Tirgger when "implement" in the prompt

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/impl/SKILL.md

Quality

Content

85%

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 well-structured, lean orchestration playbook with a clear phased workflow and a validation/fixup feedback loop. Its main weakness is actionability: several core agent instructions remain abstract despite concrete model and timeout specifics.

Suggestions

Tighten the abstract agent instructions — e.g. specify what 'following the project guidelines' means (run lint/build/test commands) and what 'targeted local testing' the Fixup agent should perform.

Clarify how the orchestrator creates/updates the PR draft (e.g. naming convention, base branch) so step 2 is executable rather than implied.

Fix minor typos ("revelant", "sumarized", "reponse") that slightly undercut the otherwise tight instruction quality.

Dimension	Reasoning	Score
Conciseness	The body is lean (~40 lines) with no concept-padding — it assumes Claude knows git/PR basics and every section (Agents, Rules, Orchestrator response) earns its place. Matches the 'lean and efficient; assumes Claude's competence' anchor.	3 / 3
Actionability	Quotes concrete specifics like model "gpt-5.6-sol", "low reasoning", and "minimum of 60000 ms_timeout", but core actions stay abstract — "implement the feature following the project guidelines", "solve the root cause of the issue". Not score 3 because key instructions lack executable detail; not score 1 because models, timeouts, and required response contents are specified.	2 / 3
Workflow Clarity	Quotes a numbered 5-phase sequence with an explicit Validation agent checkpoint and a Fixup-agent feedback loop returning to step 2. Matches the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor.	3 / 3
Progressive Disclosure	Under 50 lines, single-purpose, with well-organized sections (# Agents, # Rules, # Orchestrator response) and no need for external references. Per the simple-skills note, well-organized sections alone warrant a 3 here.	3 / 3
	Total	11 / 12 Passed

Description

42%

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 names a concrete action and includes an explicit trigger, but is thin and generic: a single keyword trigger, a tautological 'what', and a typo. It is unlikely to distinguish this skill from the many that involve 'implementing'.

Suggestions

Expand the trigger to natural variations users actually say, e.g. 'Use when the user asks to implement, build, add, or develop a feature'.

Make the 'what' concrete and distinct, e.g. 'Orchestrates end-to-end feature implementation via subagents — implementation, PR creation, validation, and fixup until ready to merge'.

Fix the typo 'Tirgger' → 'Trigger' and use a 'Use when...' clause for clearer trigger guidance.

Dimension	Reasoning	Score
Specificity	Quotes "Implement a feature" — a concrete verb and domain are named, but only a single generic action with no breadth. Not score 1 because a real action is stated; not score 3 because it lacks the multiple specific actions the top anchor requires.	2 / 3
Completeness	Quotes "Implement a feature" (what) and "Tirgger when 'implement' in the prompt" (when) — both are present and explicit, but the 'what' is nearly tautological with the trigger and conveys little scope. Not score 1 because both what and an explicit trigger exist; not score 3 because the what is too generic to clearly answer what the skill does.	2 / 3
Trigger Term Quality	Quotes "implement" as the sole keyword — it is a natural term a user would say, but no common variations (build, add, create) are covered and it is misspelled "Tirgger". Not score 3 due to thin coverage; not score 1 because the term is genuinely natural.	2 / 3
Distinctiveness Conflict Risk	Quotes "implement" — an extremely common word that would fire for coding, refactoring, bug-fixing, and many other skills, creating high conflict risk. Matches the 'very generic; would conflict with many skills' anchor; not score 2 because nothing narrows the niche.	1 / 3
	Total	7 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: tympanix/Electorrent
Path: .agents/skills/impl/SKILL.md
Commit: 89eb958

Reviewed: 1 day 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.