CtrlK
BlogDocsLog inGet started
Tessl Logo

audit

Use when the user asks to audit a memex (long-term knowledge bank for AI agents) for orphans, dead SALP REFs, missing sections, contradictions or index drift. Runs a structural check, layers LLM-judgement findings, auto-fixes trivia with `--fix`.

68

Quality

84%

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

76%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 highly actionable and well-structured, delegating deterministic logic to a bundled script and keeping concrete commands and templates inline. Its main weakness is workflow_clarity: the batch auto-fix stage has no explicit re-validation step after fixes are applied.

Suggestions

Add a validation feedback loop after the auto-fix stage: re-run 'deno run --allow-read scripts/audit.ts <memex-root>/pages/' with --fix and confirm DEAD_LINK/INDEX_MISSING/MISSING_SECTION counts dropped to zero before writing the report, fixing and re-running if any remain.

Reference scripts/audit_test.ts explicitly (e.g., a one-line note that it documents expected output formats) so the bundled test file is discoverable rather than orphaned in scripts/.

Tighten the report markdown template and the per-issue format enumeration in step 1 to the minimum needed to reproduce the output, trimming redundant detail.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence: a concrete script command, a compact issue-kind table, an auto-fix table, and a report template, with no padding about what a memex or SALP REF is. It is not a 5 because the report markdown template and per-issue format lines could be trimmed slightly without losing actionability.

4 / 5

Actionability

Provides fully executable, copy-paste-ready guidance: 'deno run --allow-read scripts/audit.ts <memex-root>/pages/', grep commands, an exact stub-body template for DEAD_LINK fixes, and a full audit-report markdown skeleton. Matches the score-5 anchor of fully executable guidance covering the common cases; above score 4 because the examples are complete and specific rather than having minor gaps.

5 / 5

Workflow Clarity

Steps are clearly numbered 1-6 and gated by --fix with a Constraints section, but the batch auto-fix stage (creating stubs, appending sections, editing index.md) lacks an explicit re-run/re-validate feedback loop to confirm fixes resolved the original issues. The rubric caps batch/destructive workflows without validation at 3, so this stays at 3 even though the sequence itself is well-ordered; it is not a 2 because the sequence and checkpoints are largely present.

3 / 5

Progressive Disclosure

The body is organized into clear sections (When to invoke, Memex Resolution, Audit Steps, Constraints) and delegates the bulk deterministic logic to the one-level-deep bundled scripts/audit.ts, which is referenced by an executable command. It is not a 5 because scripts/audit_test.ts is unreferenced and there is no explicit 'see the script for detail' pointer beyond the command itself, leaving minor organization gaps.

4 / 5

Total

16

/

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 specific, complete, and highly distinctive, explicitly pairing a 'Use when' trigger with a concrete catalog of audit actions and issue types. Its only gap is that a few natural user phrasings ('check the memex', 'dead links') live in the body rather than the description itself.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and a comprehensive issue catalog: 'audit a memex ... for orphans, dead SALP REFs, missing sections, contradictions or index drift', plus 'Runs a structural check, layers LLM-judgement findings, auto-fixes trivia with --fix'. This matches the score-5 anchor of multiple specific concrete actions with comprehensive coverage; it is above score 4 because the enumeration is thorough rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both 'what' (the audit actions and issue types) and 'when' via a concrete 'Use when the user asks to audit a memex ...' trigger clause. This matches the score-5 anchor of clearly and explicitly answering both what AND when with concrete trigger phrases; it is above score 4 because the when-clause is explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

Includes the natural trigger 'Use when the user asks to audit a memex' and issue terms a user might say ('orphans', 'dead SALP REFs', 'contradictions', 'index drift'), but common phrasings like 'check the memex', 'memex health check', and 'dead links' appear only in the body, not the description. Good coverage with a few natural terms missing, so score 4 rather than 5; not a 3 because several natural terms are present, not just one or two generic ones.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply defined by domain-specific tokens ('memex', 'SALP REFs', 'index drift'), making conflict with other skills minimal. Matches the score-5 anchor of a clear niche with distinct triggers and minimal conflict risk; it is above score 4 because the specialized vocabulary leaves almost no overlap with generic 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
korchasa/flowai-plugins
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.