SKILLEMALL.ai

AF logic-review

Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy).

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 2 files body ≈ 3 345 tokens Open the sourcegithub.com analyzed 2 d ago

Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy).

As a process F 53/100 · Will not run — References files that are not bundled: scripts/grade-iteration.py

AnalyzerSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
98
Quality 40%
79
Run on models
none yet
Process rating
F
53/100
Will not run
References files that are not bundled: scripts/grade-iteration.py
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Risky intent intent-offensive-security logic-review-guide.md:140
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    ## Step 5.5: Adversarial Red Team
  • low Risky intent intent-offensive-security SKILL.md:84
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    **Step 5.5. Adversarial Red Team** (guide Step 5.5) — for each candidate finding, attempt to disprove it by answering three rebuttal questions (premise rebuttal, path rebuttal, consequence rebuttal). 

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: scripts/grade-iteration.py
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_repo"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "license_source"

Process rating: all ten parameters 53/100

Will not run. References files that are not bundled: scripts/grade-iteration.py
  • 0Tools and files. 1 referenced file(s) missing: scripts/grade-iteration.py
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 60Failures and branches. 2 branches
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 9 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3345 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)
  • +2Single-language instructions
  • +3Description length 130: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 9 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)
  • +1License stated

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