SKILLEMALL.ai

BF technology-radar

Build and maintain technology radars for adoption, trial, assessment, and hold decisions, and choose proportionate architecture-governance paths for technology portfolios. Use when governing technology choices, build-versus-buy decisions, architecture standards, exceptions, or engineering portfolio risk. Do not use for enterprise capability or target-state architecture, writing ADRs, implementing systems, security engineering, or operational incident/runbook work.

magnus919/agent-skills Agent Skills author: magnus919 MIT 8 files body ≈ 1 502 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Build and maintain technology radars for adoption, trial, assessment, and hold decisions, and choose proportionate architecture-governance paths for…

As a process F 36/100 · Will not run — References files that are not bundled: ../enterprise-architecture/SKILL.md, ../software-architecture/SKILL.md

AnalyzerInfrastructureFinancetype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
F
36/100
Will not run
References files that are not bundled: ../enterprise-architecture/SKILL.md, ../software-architecture/SKILL.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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
  • 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: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../enterprise-architecture/SKILL.md
  • warning missing-ref reference to a missing file: ../software-architecture/SKILL.md
  • note edit-residue the text marks something as outdated (lines 34): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 36/100

Will not run. References files that are not bundled: ../enterprise-architecture/SKILL.md, ../software-architecture/SKILL.md
  • 0Tools and files. 2 referenced file(s) missing: ../enterprise-architecture/SKILL.md, ../software-architecture/SKILL.md
  • 0Result and completion. Does not say what the result is
  • 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
  • 30Running it twice. 1 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 100Steps. 23 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1502 tokens
  • low No test case covers injection arriving through data

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
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 468: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 23 items
  • +4Reference files are cited in the instructions (4 of 5)
  • +1License stated

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