SKILLEMALL.ai

AC byterover

You MUST use this for gathering contexts before any work. This is a Knowledge management for AI agents. Use `brv` to store and retrieve project patterns, decisions, and architectural rules in .brv/context-tree. Uses a configured LLM provider (default: ByteRover, no API key needed) for query and curate operations.

ClawHub Agent Skills author: gasgangrene v1.0.0 MIT-0 3 files body ≈ 4 946 tokens Open the sourceclawhub.ai analyzed 21 h ago

You MUST use this for gathering contexts before any work.

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

IntegrationObsidianAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
C
55/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
50
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: byterover (ClawHub)

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: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 172): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 55/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
    • 70Execution cost. Instruction body is 4946 tokens
    • 100Steps. 68 steps
    • 100Consistency. Name and required fields are in place
    • 100Running it twice. Mutating operations check current state
    • 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
    • -4Absolute local paths (C:\Users, /home/…): not portable
    • +1No license
    • +2Single-language instructions
    • +3Description length 314: enough signal without eating the budget
    • +4Structure: 21 headings
    • +3Step-by-step instructions: 68 items
    • +4Has examples (57 code blocks)

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

    External checks

    ClawHub: suspicious
    This skill is mostly a knowledge-management helper, but it pushes agents toward broad memory access and external processing in ways users should review before installing.
    LLM: suspicious (high) · VirusTotal: · 2 Aug 2026