SKILLEMALL.ai
GitHub ↗ RU Sign in

AA elite-rfc-writer

Write decision-oriented engineering RFCs with strict template enforcement. Use when the user asks for an RFC, architecture decision proposal, or structured decision document that must follow the exact headings: Zusammenfassung, Motivation, Ziele, Nicht-Ziele, Vorschlag, Anhang.

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

Write decision-oriented engineering RFCs with strict template enforcement.

As a process A 83/100 · Runs to the end — weak spots: consistency, running it twice, progress reporting

GeneratorCustomer supportOperations and projectstype 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
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
A
83/100
Runs to the end
Progress reporting w 2
0
Running it twice w 4
30
Consistency w 8
40
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: 3. 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 83/100

    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 1 mutating operations with no state check
    • 40Consistency. Frontmatter name (elite-rfc-writer) differs from the folder (elite-rfc-writer-safe)
    • 50Failures and branches. 0 branches, has a failure section
    • 85Steps. 53 steps, 2 vague phrases
    • 100Tools and files. No external tools needed
    • 100Result and completion. Output format and completion criterion are stated
    • 100When it triggers. States when to use and when not to
    • 100Inputs and preconditions. Inputs and preconditions are listed
    • 100Execution cost. Instruction body is 949 tokens

    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)
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 278: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 53 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (2 of 2)

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