CtrlK
BlogDocsLog inGet started
Tessl Logo

add-tech-debt

Append a tech debt entry to a project tech-debt log (docs/tech-debt-log.md) based on the current conversation. Use when: (1) the user says 'add tech debt', 'log tech debt', 'log this as tech debt', 'note this for the tech debt log', '/add-tech-debt', (2) the user wants to record an architectural smell, coding-practice issue, or non-blocking design flaw discovered while working on something else, (3) the user describes a self-healing or workaround-able issue that signals a deeper design mistake worth logging. Triggers on tech debt logging, architectural smell capture, code quality issue recording.

68

Quality

82%

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

75%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 tight, well-structured instruction skill with a concrete entry template and clear workflow. It would reach the top band with a worked filled-in example, an explicit append-verification step, and slightly tighter prose.

Suggestions

Add one short worked example showing a completed entry (with realistic file path, symptom, smell, right-shape bullets, and severity) so the template is unambiguously copy-paste ready.

Insert an explicit post-append verification checkpoint in step 4 (e.g., re-read the file to confirm the entry landed and the trailing separator is intact).

Trim minor redundant prose such as 'that's the whole point of the entry' and the repeated docs-location parenthetical to push conciseness to the top band.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence (no padded explanation of what tech debt is, no library tutorials), with only minor trimmable prose such as the parenthetical 'that's the whole point of the entry'.

4 / 5

Actionability

Provides a complete, copy-paste-ready entry template with concrete field semantics and explicit rules (global monotonic numbering, lowercase paths, YYYY-MM-DD dates), but lacks a worked filled-in example that would seal it as fully copy-paste ready.

4 / 5

Workflow Clarity

Clear five-step sequence with embedded guards (duplicate detection in step 2, insufficient-context question in step 1); the operation is an append so the destructive/batch validation cap does not apply, but there is no explicit post-append verification checkpoint.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Workflow, Notes on style, When NOT to use) with no bundle files and no content that clearly belongs in a separate file; sits just above the simple-skill line at ~85 lines, keeping it at 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

90%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 exemplary: it states one concrete action, provides comprehensive natural-language and slash-command triggers, and explicitly separates what the skill does from when to use it. Its only limitation is that the single-purpose nature leaves it with one concrete action rather than several.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ('Append a tech debt entry to a project tech-debt log (docs/tech-debt-log.md)'), but it is a single-purpose skill with only one action rather than several, so it does not reach the 'several specific actions' bar of 4.

3 / 5

Completeness

Explicitly answers what ('Append a tech debt entry ... based on the current conversation') and when (a numbered 'Use when:' list with concrete trigger phrases), matching the top anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms and the slash command ('add tech debt', 'log tech debt', 'log this as tech debt', 'note this for the tech debt log', '/add-tech-debt') plus descriptive triggers users would naturally voice.

5 / 5

Distinctiveness Conflict Risk

Clear niche (non-blocking design flaws and architectural smells written to a specific docs/tech-debt-log.md file) with distinct triggers and minimal overlap with general issue-tracking 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
mayank-arora/agent-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.