CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

unslopify

Use when you need focused cleanup audits, safe removals, scoped quality-risk reductions, and evidence-backed cleanup plans before touching code.

Quality

70%

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 ./Infrastructure/references/deferred-skill-context/agent-ops-unslopify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 runbook: the six-phase workflow is sequenced with explicit per-batch validation and fail-fast feedback loops, and bundle references are real, one level deep, and clearly signaled. The main weaknesses are duplicated gating/fail-fast sections and ambiguous placement of the pre-execution proof requirements relative to the phase sequence.

Suggestions

Deduplicate the fail-fast rule and the resolve/handles gate commands, which appear in both 'Failure mode'/'Invocation and Visibility Proof Requirements' and 'Baseline validation to confirm first' — merge them into one gating section.

State explicitly where the five invocation-proof commands run within the phase sequence (e.g., 'Phase 0: gates, before Phase 1') since both late sections claim to run 'first'.

DimensionReasoningScore

Conciseness

The body doesn't explain concepts Claude already knows, but it is noticeably redundant: the fail-fast rule appears verbatim in both 'Failure mode' and 'Baseline validation to confirm first', and the 'skills resolve'/'handles --check' gate commands are listed twice across 'Invocation and Visibility Proof Requirements' and the baseline section. This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

Concrete executable commands are given throughout (`./bin/ask repo status`, `rg`, `fd`, `git status`, five exact gating commands with flags, `./bin/ask repo validate --ephemeral`), plus a four-category decision matrix and an ordered batch plan, fitting 'Mostly executable guidance; concrete code or commands with minor gaps'. Not 5 because several directives remain high-level ('Run a short orientation pass', 'capture evidence, confidence, and risks') without a concrete pattern for what to record.

4 / 5

Workflow Clarity

The six phases are clearly sequenced with explicit validation checkpoints and a real feedback loop ('stop at the first failed gate ... rerun the failed gate only after the blocker is fixed', 'Re-run relevant validation after each batch'), so the destructive/batch cap of 3 does not apply. Not 5 because the two post-workflow gate sections both claim to run before everything ('Baseline validation to confirm first', 'Before execution') yet appear after Phase 6 in document order, leaving ambiguity about where they sit in the sequence.

4 / 5

Progressive Disclosure

The SKILL.md is a genuine overview with a dedicated 'Progressive Disclosure' section pointing one level deep to references/contract.yaml, references/evals.yaml, and references/task-profile.json — all of which exist in the bundle and match their stated purposes (machine-readable contract, benchmark/adversarial cases, evaluator thresholds). This matches 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'.

5 / 5

Total

16

/

20

Passed

Description

57%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 has a clear structure with an explicit 'Use when' clause, but its actions are abstract buzz-adjacent phrasings rather than concrete cleanup operations, it uses second-person voice, and it lacks the natural trigger terms (dead code, unused exports, stale dependencies) users would actually say. It lands just above the midpoint overall.

Suggestions

Replace abstract phrases like 'scoped quality-risk reductions' with concrete actions users recognize: e.g., 'Find unused/dead code, stale exports, duplicate artifacts, and fragile error handling, and produce an evidence-backed cleanup plan.'

Add concrete trigger situations to the when-clause: 'Use when the user mentions dead code, unused exports, stale dependencies, or asks what can be safely removed before touching code.'

Rewrite in third person to avoid the second-person penalty: 'Performs focused cleanup audits and safe removals with evidence-backed plans...' instead of 'Use when you need...'.

DimensionReasoningScore

Specificity

The description names the cleanup domain and lists several actions ('focused cleanup audits, safe removals, scoped quality-risk reductions, and evidence-backed cleanup plans'), but each action is generic or abstract rather than concrete, matching 'Names the domain but actions are minimal or generic'. The second-person phrasing 'Use when you need' triggers the rubric's 1-point specificity penalty, lowering the base of 3 to 2.

2 / 5

Completeness

Both what (the action list) and when (explicit 'Use when you need ... before touching code') are present, fitting 'Has both what and when; when could be more explicit or specific'. Not 5 because the when-clause is self-referential (it restates the skill's outputs) instead of naming concrete user situations or trigger phrases.

4 / 5

Trigger Term Quality

'cleanup', 'removals', and 'code' are relevant natural keywords, but common variations users actually say — 'dead code', 'unused code', 'stale exports', 'what can be safely removed' — are absent, matching 'Some relevant keywords but missing common variations or synonyms'. Not 4 because the natural-term coverage is thin for a cleanup skill.

3 / 5

Distinctiveness Conflict Risk

The pre-edit, evidence-first cleanup-audit niche ('cleanup plans before touching code') is mostly distinct with only minor overlap risk against closely related code-review/refactor skills. Not 5 because phrases like 'quality-risk reductions' are broad enough to compete with generic code-quality 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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Infrastructure/references/deferred-skill-context/agent-ops-unslopify/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.