SKILLEMALL.ai

BF project-execution

Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement

ClawHub Agent Skills author: athola v1.9.19 MIT-0 2 files body ≈ 2 642 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process F 33/100 · Will not run — References files that are not bundled: references/mission-report.md

AnalyzerInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
F
33/100
Will not run
References files that are not bundled: references/mission-report.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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: references/mission-report.md
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_plugin"

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: references/mission-report.md
  • 0Tools and files. 1 referenced file(s) missing: references/mission-report.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. 6 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 40Consistency. Frontmatter name (project-execution) differs from the folder (nm-attune-project-execution)
  • 100Steps. 84 steps
  • 100Execution cost. Instruction body is 2642 tokens
  • low 14 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
  • -212 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 159: enough signal without eating the budget
  • +4Structure: 29 headings
  • +3Step-by-step instructions: 84 items
  • +4Has examples (12 code blocks)

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

External checks

ClawHub: clean
This skill is a disclosed project-execution workflow that guides coding, testing, progress tracking, and local checkpoint reporting without hidden install steps or unrelated data access.
LLM: benign (high) · VirusTotal: · 26 Aug 2026