CtrlK
BlogDocsLog inGet started
Tessl Logo

simplify-and-harden

Post-completion self-review for coding agents that runs simplify, harden, re-verification, and micro-documentation passes on non-trivial code or high-impact configuration changes. Use when a task is complete in a general agent session and you want a bounded quality and security sweep before signaling done. For CI pipeline execution, use simplify-and-harden-ci.

68

Quality

83%

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

73%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 content is highly actionable and clearly sequenced with strong validation feedback loops, but it is padded with philosophical and design-rationale prose that inflates token cost. Progressive disclosure is reasonable with one real reference file, though the body itself carries content that could be externalized.

Suggestions

Move the full example output-schema YAML and the programmatic/prompt-based integration code blocks into reference files, keeping only a minimal inline example in SKILL.md.

Tighten or remove the 'Rationale and Philosophy' and 'Design Decisions' prose sections, or relocate them to a separate references/DESIGN.md, retaining only the operational rules.

Trim the 'Future Considerations' section or move it to a reference, since it does not guide execution of the skill.

DimensionReasoningScore

Conciseness

The body is noticeably verbose — the 'Rationale and Philosophy', 'Design Decisions', and 'Future Considerations' sections are prose-heavy motivational/justification padding (e.g. 'Most agents solve the ticket and stop. This skill turns done into done well.'), and the full example YAML output schema is large, several of which could be trimmed without losing operational value.

2 / 5

Actionability

Provides copy-paste-ready concrete artifacts covering common cases: detailed simplify/harden checklists, action categories with examples, an interactive refactor stop-hook prompt, a full output-schema YAML, a config YAML, and a programmatic integration code block.

5 / 5

Workflow Clarity

The four passes (Simplify, Harden, Document, Re-verify) are clearly sequenced, with an explicit validation checkpoint and feedback loop in Pass 4 ('If verification fails, return to implementation with the diagnostics') plus not-run handling, and checklists for each review pass.

5 / 5

Progressive Disclosure

Structure is good with clear section headers and one well-signaled one-level-deep reference (references/agent-context-snippets.md, confirmed to exist, with 'Load only the snippet for your active agent to keep context lean'), though large blocks like the full output-schema example and integration notes remain inlined rather than split out.

4 / 5

Total

16

/

20

Passed

Description

92%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 is strong: it states concrete actions, gives an explicit 'Use when' trigger, and cleanly separates the interactive general-session skill from its CI variant. The only minor gap is breadth of natural trigger synonyms, keeping trigger_term_quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "runs simplify, harden, re-verification, and micro-documentation passes" — giving comprehensive coverage of what the skill does, matching the level-5 anchor of multiple specific concrete actions.

5 / 5

Completeness

Explicitly answers both what ("runs simplify, harden, re-verification, and micro-documentation passes on non-trivial code or high-impact configuration changes") and when ("Use when a task is complete in a general agent session and you want a bounded quality and security sweep before signaling done"), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases such as "task is complete", "quality and security sweep", "signaling done", and "non-trivial code" that a user might say, with good keyword coverage, though it lacks the breadth of synonyms/extensions seen in the level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (post-completion self-review with bounded scope for general agent sessions) and explicitly distinguishes from the CI variant ("For CI pipeline execution, use simplify-and-harden-ci"), minimizing conflict risk.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (571 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
pskoett/pskoett-ai-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.