SKILLEMALL.ai
GitHub ↗ RU Sign in

AB reporting

Standardized templates for periodic reports, system audits, revenue tracking, and progress logs. All output goes to workspace/artifacts/ directory. Use when: generating periodic reports, system audits, performance reviews, revenue tracking, weekly retrospectives, daily progress logs, full workspace audits. Don't use when: ad-hoc status updates in chat, quick summaries in Discord, one-off answers to "how's it going?", real-time dashboards. Negative examples: - "Give me a quick update" → No. Just answer in chat. - "What's the weather?" → No. This is for structured reports. - "Post a status to Discord" → No. Just send a message. Edge cases: - Mid-week report requested → Use weekly template but note partial week. - Audit requested for single subsystem → Use full audit template, mark other sections N/A. - Revenue snapshot with $0 revenue → Still generate it. Zeros are data.

modbender/skill-library-mcp Agent Skills author: modbender MIT 5 files body ≈ 410 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Standardized templates for periodic reports, system audits, revenue tracking, and progress logs.

As a process B 65/100 · Nearly there — weak spots: inputs and preconditions, failures and branches

TemplateDiscordData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
B
65/100
Nearly there
Inputs and preconditions w 11
0
Failures and branches w 10
0
When it triggers w 12
50
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: 5. 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 65/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 50When it triggers. No condition that starts the skill
    • 60Result and completion. Output format stated, no completion criterion
    • 85Steps. 5 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 410 tokens
    • 100Running it twice. No mutating operations
    • 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

    • +3Description length 885: 120–800 characters recommended
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +4Description says when NOT to use the skill
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 5 items
    • +3Output format is stated explicitly

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