CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

audit

Perform a deep evidence-backed PsychSift repository audit and produce severity-ranked, reproducible findings without mutating code unless fixes are requested. Use for repo-wide audits, risk assessments, or exhaustive review requests.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

An exceptionally lean, well-sequenced audit protocol that delegates detail to a protocol document and includes genuine checkpoints (existing-record dedup, evidence-backed findings). Its main weakness is actionability: the severity ranking scheme, the findings output format, and what a 'focused check' looks like are never specified, leaving the executor to improvise the deliverable's shape.

Suggestions

Define the severity scale inline (e.g., Critical/High/Medium/Low with one-line criteria) or point to where it is defined, so 'Rank findings by severity' is executable rather than improvised.

Specify the findings output format — a short template listing the required fields per finding (file, line, trigger, impact, focused check) — so 'Prove findings with exact files, lines, triggers, impact' yields a consistent deliverable.

Add an explicit verification step before reporting, e.g., re-confirming each finding's line numbers against the current HEAD after analysis, to close the workflow's validation gap.

DimensionReasoningScore

Conciseness

Six one-line numbered steps with zero padding and no explanation of concepts Claude already knows — every token earns its place, matching anchor 5; anchor 4 would require trimmable over-explanation, which is absent.

5 / 5

Actionability

Concrete artifacts are named (docs/codex-review-protocol.md, the 'Review record', findings with 'exact files, lines, triggers, impact'), but key execution details are missing: no severity scale for 'Rank findings by severity', no findings output format, and no example of a 'focused check'. This is incomplete concrete guidance (anchor 3), not mostly-executable guidance with minor gaps (anchor 4).

3 / 5

Workflow Clarity

A clear 6-step sequence with most checkpoints present — step 1's check for an existing 'Review record' at the same head/scope and step 4's requirement to prove findings with focused checks. The skill is read-only so the destructive-operation cap does not apply; the minor gap is the absence of an explicit re-verification loop before reporting, matching anchor 4.

4 / 5

Progressive Disclosure

A ~10-line skill with no bundle files, well-organized as a numbered list, and clearly signaled one-level-deep references to docs/codex-review-protocol.md and the pull-request workflow Records section — per the simple-skill guideline this matches anchor 5.

5 / 5

Total

17

/

20

Passed

Description

83%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.

A strong description: it states concrete capabilities with qualifiers, includes an explicit 'Use for...' trigger clause with natural phrases, and defines a clear niche. The only weaknesses are slightly incomplete keyword coverage (no 'security review'/'code review' synonyms) and modest overlap risk from the broad 'risk assessments' trigger.

DimensionReasoningScore

Specificity

Names the domain ('PsychSift repository audit') and several concrete, qualified actions ('evidence-backed', 'severity-ranked, reproducible findings', 'without mutating code unless fixes are requested'), but coverage of what the audit examines is left to the body rather than the description — minor gaps, matching anchor 4 rather than comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both 'what' (deep evidence-backed audit producing severity-ranked, reproducible findings, read-only by default) and 'when' ('Use for repo-wide audits, risk assessments, or exhaustive review requests') with concrete trigger phrases, matching anchor 5; anchor 4 would require the 'when' clause to be less explicit.

5 / 5

Trigger Term Quality

'audit', 'repo-wide audits', 'risk assessments', and 'exhaustive review requests' are natural phrases users would say, but common synonyms like 'security review' or 'code review' are missing — good coverage with a few natural terms absent, matching anchor 4.

4 / 5

Distinctiveness Conflict Risk

'PsychSift repository audit' carves a clear niche, but the trigger terms 'risk assessments' and 'exhaustive review requests' are broad enough to overlap with generic code-review skills — mostly distinct with minor overlap risk, matching anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

17

/

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

BigSimmo/PsychSift

Path

.agents/skills/audit/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.