SKILLEMALL.ai

CD intake

Intake protocol — the craft of turning a vague brief into an approved production plan. Runs phases 1-7 of the agent production contract: 3-5 clarifying questions sized to the user's skill band, content-mode classification, format/template match, memory recall, the reference gate, the style lock, and the plan the user approves before any paid generation. USE WHEN a request opens a NEW project or carries more than one unknown — "make a video about X", "I want one like this <url>", "launch project Y", audience / brand / aesthetic / duration unstated. FIRES BEFORE any other content route. DO NOT FIRE on a follow-up inside a project already scoped, or on an explicit template remix (@template:<slug>) where only the swap is new.

alecs5am/ralphy Agent Skills author: alecs5am 1 file body ≈ 7 694 tokens Open the sourcegithub.com↗ analyzed 11 h ago

Intake protocol — the craft of turning a vague brief into an approved production plan.

As a process D 35/100 · Unfinished process — References files that are not bundled: ../../../docs/playbooks/agent-production-contract.md, ../researcher/references/site-grounding.md, ../researcher/references/research-bootstrap.md

ProcedureMarketingAI and agentsMedia and videotype and topics are labelled automatically from the skill text
JSON
Technical rating
C
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
D
35/100
Unfinished process
References files that are not bundled: ../../../docs/playbooks/agent-production-contract.md, ../researcher/references/site-grounding.md, ../researcher/references/research-bootstrap.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
This is a copy of a skill from another catalog; the rating counts the canonical one: intake (alecs5am/ralphy)

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. 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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 7694 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../../../docs/playbooks/agent-production-contract.md
  • warning missing-ref reference to a missing file: ../researcher/references/site-grounding.md
  • warning missing-ref reference to a missing file: ../researcher/references/research-bootstrap.md
  • warning missing-ref reference to a missing file: ../researcher/SKILL.md
  • warning missing-ref reference to a missing file: ../art-director/references/location-plate.md
  • warning missing-ref reference to a missing file: ../../../docs/skills-vs-templates.md
  • note frontmatter-key unknown frontmatter key "namespace"
  • note edit-residue the text marks something as outdated (lines 9, 162): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: ../../../docs/playbooks/agent-production-contract.md, ../researcher/references/site-grounding.md, ../researcher/references/research-bootstrap.md
  • 0Tools and files. 6 referenced file(s) missing: ../../../docs/playbooks/agent-production-contract.md, ../researcher/references/site-grounding.md, ../researcher/references/research-bootstrap.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 17 mutating operations with no state check
  • 60Steps. 68 steps, 4 vague phrases
  • 70Execution cost. Instruction body is 7694 tokens
  • 100Failures and branches. 6 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 16 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (20 tags): a typed call is more reliable

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

  • +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
  • +5Description quotes 3 example trigger phrases
  • +3Description length 731: enough signal without eating the budget
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 68 items
  • +4Has examples (2 code blocks)

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