SKILLEMALL.ai

AF golang-project-layout

Provides a guide for setting up Golang project layouts and workspaces. Use when starting a new Go project, organizing an existing codebase, setting up a monorepo with multiple packages, creating CLI tools with multiple main packages, deciding between cmd/internal/pkg directory conventions, or discussing package restructuring, package splits, or module splits.

ClawHub Agent Skills author: Samuel Berthe v1.4.0 MIT-0 7 files body ≈ 1 579 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process F 33/100 · Will not run — References files that are not bundled: assets/Makefile, assets/.gitignore

IntegrationSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
F
33/100
Will not run
References files that are not bundled: assets/Makefile, assets/.gitignore
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: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: assets/Makefile
  • warning missing-ref reference to a missing file: assets/.gitignore

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: assets/Makefile, assets/.gitignore
  • 0Tools and files. 2 referenced file(s) missing: assets/Makefile, assets/.gitignore
  • 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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 100Steps. 21 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1579 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 11 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
  • +2Single-language instructions
  • +3Description length 361: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)
  • +1License stated

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

External checks

ClawHub: suspicious
The skill is mostly normal Go project-layout guidance, but it also tells agents to silently add a persistent always-load directive to project agent configuration.
LLM: suspicious (high) · 22 Aug 2026