SKILLEMALL.ai

AC agent-context-kb

Manage and explain a repository's `.agent-kb/` knowledge base (KB) for coding agents. Use when the user works with the KB — asks how the KB or its commands behave, sets up project memory, records durable knowledge, refreshes the KB runtime protocol, validates routes/links, compiles inbox notes into topics, or trims stale content.

ClawHub Agent Skills author: lesliebiubiubiu v0.1.0 MIT-0 7 files body ≈ 925 tokens Open the sourceclawhub.ai analyzed 3 d ago

Manage and explain a repository's .agent-kb/ knowledge base (KB) for coding agents. Use when the user works with the KB — asks how the KB or its commands…

As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

ProcedureAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
81
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 59/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 2 mutating operations with no state check
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 13 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 925 tokens
    • 100Progress reporting. Reports progress

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -32 of 3 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 331: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 13 items
    • +4Has examples (2 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.

    External checks

    ClawHub: suspicious
    The skill mostly manages a project knowledge base, but its stats tooling reads local agent conversation logs by default and stores derived activity metadata, so it should be reviewed before installation.
    LLM: suspicious (high) · 2 Aug 2026