SKILLEMALL.ai
GitHub ↗ RU Sign in

BB openspec-propose

Propose a new OpenSpec change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation. Also use when the user says "openspec propose" or "opsx propose".

jamro/tiny-engineer Agent Skills author: jamro NOASSERTION 1 file body ≈ 4 049 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Propose a new OpenSpec change with all artifacts generated in one step.

As a process B 73/100 · Nearly there — weak spots: result and completion, inputs and preconditions

GeneratorSoftware developmentData and analyticsWriting and documentstype 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%
76
Run on models
none yet
Process rating
B
73/100
Nearly there
Inputs and preconditions w 11
0
Result and completion w 14
40
When it triggers w 12
70
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: tiny-engineer

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

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 73/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 40Result and completion. Does not say what the result is
    • 70When it triggers. States when to use, but not when not to
    • 70Execution cost. Instruction body is 4049 tokens
    • 85Steps. 36 steps, 1 vague phrases
    • 100Tools and files. Tools declared in frontmatter
    • 100Failures and branches. 8 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low The response is described with custom markup (12 tags): a typed call is more reliable

    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

    • +4Description does not say when NOT to use the skill (false activations)
    • +4Structure: 0 headings, hard to scan
    • +3Output format is not stated: the model decides each time
    • -5Long text without headings
    • -5TODO / placeholder text left in the skill
    • +2Single-language instructions
    • +5Description quotes 2 example trigger phrases
    • +3Description length 289: enough signal without eating the budget
    • +3Step-by-step instructions: 36 items
    • +4Has examples (5 code blocks)
    • +1License stated

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