SKILLEMALL.ai
GitHub ↗ RU Sign in

BF frame-a-proposal

Frame a new design proposal (RFC-shape) under proposals/ — problem before solution, named beneficiary and observable change, real alternatives, honest drawbacks, and a live open-questions backlog. Read when asked to frame a proposal, write an RFC, propose a design, pitch a change, draft a PRD-style design doc, or open a design proposal for review. Do NOT read to record a decision after it is accepted (use record-a-decision), to write an implementation spec (use write-a-spec), to write a postmortem (use write-a-postmortem), or to review or critique an existing design (use review-a-design).

inkeep/open-knowledge Agent Skills author: inkeep GPL-3.0 1 file body ≈ 3 331 tokens Open the sourcegithub.com↗ analyzed 15 h ago

Frame a new design proposal (RFC-shape) under proposals/ — problem before solution, named beneficiary and observable change, real alternatives, honest…

As a process F 43/100 · Will not run — References files that are not bundled: decisions/0004-export-boundary.md, decisions/0004-x.md

AnalyzerOperations and projectstype 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
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
F
43/100
Will not run
References files that are not bundled: decisions/0004-export-boundary.md, decisions/0004-x.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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

  • warning missing-ref reference to a missing file: decisions/0004-export-boundary.md
  • warning missing-ref reference to a missing file: decisions/0004-x.md

Process rating: all ten parameters 43/100

Will not run. References files that are not bundled: decisions/0004-export-boundary.md, decisions/0004-x.md
  • 0Tools and files. 2 referenced file(s) missing: decisions/0004-export-boundary.md, decisions/0004-x.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 40Result and completion. Does not say what the result is
  • 100Steps. 48 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3331 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 12 top-level sections: this looks like several domains in one skill

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 595: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 48 items
  • +4Has examples (6 code blocks)

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