CtrlK
BlogDocsLog inGet started
Tessl Logo

create-devlog

Append a verbatim entry to a personal, per-repo, gitignored devlog (DEVLOG.md), and seed talking-point nudges from recent git/PR activity and unresolved threads in the previous entry. Use when the user says "create devlog", "devlog", "add a devlog", "dev log entry", "log this", "/create-devlog", or wants to record what they are working on / rant about progress. The user usually dictates via speech-to-text, so the log is recorded WORD-FOR-WORD with only obvious typo and speech-to-text fixes, never summarized, reworded, or analyzed.

70

Quality

85%

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 well-structured, actionable instruction skill that keeps heavy git logic in a referenced script and gives clear workflow steps with validation checkpoints. Its main weakness is mild redundancy where the two hard rules are restated across sections.

Suggestions

Consolidate the verbatim/no-analysis rules so they are stated once (e.g. in a single 'Hard rules' section) and only referenced elsewhere, reducing repetition between Overview, Writing an entry, and Correction policy.

Consider moving the detailed Fix/Never correction lists into a short reference file or collapsing them into a compact table to slim the inline body further.

Add a one-line explicit fallback for when devlog-context.sh or gh is unavailable mid-workflow, so the entry-writing path is unambiguous even if nudges cannot be seeded.

DimensionReasoningScore

Conciseness

Largely lean and assumes Claude's competence, but the two hard rules stated in the Overview are restated in the Correction policy and Writing-an-entry sections, adding mild redundancy that could be tightened.

4 / 5

Actionability

Provides concrete, executable commands (find for locating DEVLOG.md, git check-ignore -v, the devlog-context.sh invocation) and a precise entry format, with only minor placeholders like <skill-dir> remaining.

4 / 5

Workflow Clarity

Clear sequence (detect mode, seed nudges if empty, write entry) with explicit checkpoints — confirming the path is gitignored before writing and echoing the entry back to catch bad corrections — leaving only minor validation gaps.

4 / 5

Progressive Disclosure

Well-organized into labeled sections with a single one-level-deep, clearly signaled reference to scripts/devlog-context.sh (a real file) that holds the bulk of the git logic; minor organization gaps keep it just below the top anchor.

4 / 5

Total

16

/

20

Passed

Description

95%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 capabilities, provides a rich set of natural trigger phrases, and explicitly covers both 'what' and 'when' in third person. It is specific and distinctive with no over-claims.

DimensionReasoningScore

Specificity

Names concrete actions — 'Append a verbatim entry to a personal, per-repo, gitignored devlog' and 'seed talking-point nudges from recent git/PR activity and unresolved threads in the previous entry' — covering several specific behaviors with only minor gaps in full coverage.

4 / 5

Completeness

Explicitly answers both what (append verbatim entry, seed nudges) and when ('Use when the user says...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms and the slash form: 'create devlog', 'devlog', 'add a devlog', 'dev log entry', 'log this', '/create-devlog', plus the descriptive 'record what they are working on / rant about progress'.

5 / 5

Distinctiveness Conflict Risk

Clear niche — a personal, gitignored, verbatim devlog dictated via speech-to-text — with distinct triggers and minimal realistic overlap with other skills.

5 / 5

Total

19

/

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.