SKILLEMALL.ai
GitHub ↗ RU Sign in

BD output-mode-guide

Configure, use, troubleshoot, or extend AIWG composable output modes (also called output masks), including Wittgenstein-inspired clarity, engineering controlled language, and personal syntax profiles

jmagly/aiwg Agent Skills author: jmagly 1 file body ≈ 734 tokens Open the sourcegithub.com↗ analyzed 9 h ago

Configure, use, troubleshoot, or extend AIWG composable output modes (also called output masks), including Wittgenstein-inspired clarity, engineering…

As a process D 41/100 · Unfinished process — References files that are not bundled: ../../docs/writing-workflows.md

GeneratorSoftware developmentAI and agentsWriting 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%
75
Run on models
none yet
Process rating
D
41/100
Unfinished process
References files that are not bundled: ../../docs/writing-workflows.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
This is a copy of a skill from another catalog; the rating counts the canonical one: output-mode-guide (jmagly/aiwg)

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: ../../docs/writing-workflows.md
  • note frontmatter-key unknown frontmatter key "namespace"
  • note frontmatter-key unknown frontmatter key "triggers"

Process rating: all ten parameters 41/100

Will not run. References files that are not bundled: ../../docs/writing-workflows.md
  • 0Tools and files. 1 referenced file(s) missing: ../../docs/writing-workflows.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 16 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 734 tokens
  • 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)
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 199: enough signal without eating the budget
  • +4Structure: 5 headings
  • +3Step-by-step instructions: 16 items
  • +3Output format is stated explicitly

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