SKILLEMALL.ai

CC intake-from-codebase

Scan existing codebase and generate intake documents by analyzing code, dependencies, and infrastructure. Accepts optional guidance text to tailor analysis.

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

Scan existing codebase and generate intake documents by analyzing code, dependencies, and infrastructure.

As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerGitHubDockerStripePostgreSQLSoftware developmentInfrastructureSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
C
83/100
safety, quality, tests
Safety 60%
99
Quality 40%
60
Run on models
none yet
Process rating
C
58/100
Has gaps
Inputs and preconditions w 11
0
When it triggers w 12
20
Result and completion w 14
40
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: intake-from-codebase (jmagly/aiwg)

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Risky intent intent-offensive-security SKILL.md:934
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
    - {[x] if detected} Security requirements (penetration testing, audits) - {from guidance, customer contracts}
    detector

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 14502 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "namespace"
  • note frontmatter-key unknown frontmatter key "commandHint"
  • note edit-residue the text marks something as outdated (lines 654, 870, 929): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 58/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 40Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 14502 tokens: crowds the task out of the window
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 85Steps. 149 steps, 2 vague phrases
  • 100Failures and branches. 4 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress

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
  • +1No license
  • +2Single-language instructions
  • +3Description length 156: enough signal without eating the budget
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 149 items
  • +4Has examples (38 code blocks)

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