SKILLEMALL.ai
GitHub ↗ RU Sign in

BB address-feedback

Triage feedback from docs, issues, Slack threads, or pasted notes into verified bugs, UX proposals, unclear questions, and skipped noise. Use when a user asks you to address product feedback or investigate a reported workflow.

BuilderIO/agent-native Agent Skills author: BuilderIO 1 file body ≈ 4 341 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Triage feedback from docs, issues, Slack threads, or pasted notes into verified bugs, UX proposals, unclear questions, and skipped noise.

As a process B 77/100 · Nearly there — weak spots: result and completion, progress reporting

ProcedureSlackGitHubNotionData and analyticsDesigntype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
83
Run on models
none yet
Process rating
B
77/100
Nearly there
Progress reporting w 2
0
Result and completion w 14
40
Tools and files w 18
60
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "scope"
    • note edit-residue the text marks something as outdated (lines 98, 243, 250): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 77/100

    • 0Progress reporting. Says nothing while it works
    • 40Result and completion. Does not say what the result is
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 70Execution cost. Instruction body is 4341 tokens
    • 100Steps. 69 steps
    • 100When it triggers. States when to use and when not to
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Running it twice. Mutating operations check current state
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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
    • +1No license
    • +2Single-language instructions
    • +3Description length 226: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 69 items
    • +4Has examples (1 code blocks)

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