ck

Persistent per-project memory for Claude Code. Auto-loads project context on session start, tracks sessions with git activity, and writes to native memory. Commands run deterministic Node.js scripts — behavior is consistent across model versions.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

The canonical home for this skill is tdg-personal/ck

Quality

Content

100%

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 strong, lean operational spec: executable commands, exact JSON schemas, and explicit confirmation/validation checkpoints for every risky operation. It assumes Claude's competence and delegates script logic one level deep, with no bundle files needed.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: short sections, executable code blocks, terse rules, and no padded explanations of concepts Claude already knows — every token earns its place.	3 / 3
Actionability	Fully executable commands with exact paths, exact JSON schemas for piping, and concrete confirmation drafts — copy-paste ready with no pseudocode.	3 / 3
Workflow Clarity	Multi-step commands are clearly sequenced with explicit validation/confirmation checkpoints (init approval, save draft confirmation, forget confirmation, migrate --dry-run with backup note), providing feedback loops for risky operations.	3 / 3
Progressive Disclosure	Content is well-organized into clearly signaled per-command sections, with actual logic delegated one level deep to Node.js scripts under ~/.claude/skills/ck/commands/; no monolithic wall or nested-reference problem.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 specific and distinctive with several concrete capabilities, but it omits explicit 'when to use' trigger guidance, which caps completeness and weakens trigger-term quality. Adding a 'Use when...' clause naming natural user phrasings would lift both dimensions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when starting a session on a project, resuming prior work, or when the user asks to remember/save project context.'

Include natural trigger phrasings a user would actually say (e.g. 'remember this project', 'save my session', 'where did I leave off') to improve trigger-term coverage.

Keep the concrete action list as-is — it already scores well on specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Auto-loads project context on session start', 'tracks sessions with git activity', 'writes to native memory', 'Commands run deterministic Node.js scripts' — matching the multiple-specific-actions anchor.	3 / 3
Completeness	It clearly answers 'what does this do' but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant keywords like 'memory', 'project context', 'session start', and 'git activity' are present, but common natural phrasings a user would actually say (e.g. 'remember this project', 'save session state') are missing.	2 / 3
Distinctiveness Conflict Risk	The 'Persistent per-project memory for Claude Code' niche with session-start auto-loading and git-activity tracking is distinct and unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/ck/SKILL.md
Commit: 754b8dd

Reviewed: 2 days 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.