CtrlK
BlogDocsLog inGet started
Tessl Logo

project-skill-audit

Analyze a project's past Codex sessions, memory files, and existing local skills to recommend the highest-value skills to create or update. Use when a user asks what skills a project needs, wants skill ideas grounded in real project history, wants an audit of current project-local skills, or wants recommendations for updating stale or incomplete skills instead of creating duplicates.

72

Quality

89%

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

86%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 an actionable, well-structured audit workflow with concrete paths and commands and strong guardrails. Main improvement is reducing redundant path listings across sections and adding an explicit evidence-verification checkpoint.

Suggestions

Consolidate the repeated path/location listings (Workflow, Session Analysis, What To Scan) into one canonical 'What To Scan' section and reference it to remove redundancy.

Add an explicit validation checkpoint in the workflow (e.g., 'confirm the pattern recurred across N sessions before recommending') so evidence strength is verified, not implied.

Replace the hardcoded absolute path in the Follow-up link (/Users/dimillian/.codex/...) with a $CODEX_HOME-relative path so the skill is portable.

DimensionReasoningScore

Conciseness

Lean and free of concept-padding, but path listings recur across Workflow, Session Analysis, and What To Scan sections, creating redundancy that could be consolidated.

4 / 5

Actionability

Provides concrete paths ($CODEX_HOME/memories/MEMORY.md, .agents/skills, .codex/skills), specific tooling (rg with repo name/basename/cwd), and explicit file-pairs to read (SKILL.md and agents/openai.yaml), yielding copy-ready executable guidance.

5 / 5

Workflow Clarity

A clear numbered 7-step sequence with explicit ordering and fallback rules, plus Failure Shields as guardrails; validation checkpoints (e.g., confirm evidence strength before recommending) are implicit rather than explicit, keeping it just below anchor 5.

4 / 5

Progressive Disclosure

No external bundle files exist and the body is a self-contained, well-organized set of clearly headed sections, meeting the simple-skill exception for full marks without file references.

5 / 5

Total

18

/

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: concrete actions, explicit trigger guidance, and a distinct niche with low conflict risk. Minor trim opportunity on the trigger clause verbosity, but it comprehensively covers what and when.

DimensionReasoningScore

Specificity

Names multiple concrete actions (analyze past Codex sessions, memory files, and existing local skills; recommend skills to create or update) with comprehensive coverage of both input sources and the create-vs-update decision.

5 / 5

Completeness

Explicitly answers both 'what' (analyze sessions/memory/skills and recommend highest-value skills to create or update) and 'when' (a concrete 'Use when...' clause with several trigger scenarios).

5 / 5

Trigger Term Quality

Includes natural phrasings users would say ('what skills a project needs', 'skill ideas grounded in real project history', 'audit of current project-local skills', 'updating stale or incomplete skills'), though somewhat more verbose than the leanest anchor-5 keyword lists.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (project-skill auditing and recommendation) with distinct triggers and a create-vs-update framing that minimizes overlap with general skill-creation skills.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
Dimillian/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.