SKILLEMALL.ai

CC validate-profile

Validate the brand profile is production-ready: fields, compliance, connectors. "is the brand setup correct"

indranilbanerjee/digital-marketing-pro Agent Skills author: indranilbanerjee 1 file body ≈ 3 108 tokens Open the sourcegithub.com↗ analyzed 11 h ago

Validate the brand profile is production-ready: fields, compliance, connectors.

As a process C 51/100 · Has gaps — References files that are not bundled: ../brand-setup/SKILL.md, ../import-guidelines/SKILL.md, ../status/SKILL.md

AnalyzerSlackMarketingtype and topics are labelled automatically from the skill text
JSON
Technical rating
C
80/100
safety, quality, tests
Safety 60%
95
Quality 40%
57
Run on models
none yet
Process rating
C
51/100
Has gaps
References files that are not bundled: ../brand-setup/SKILL.md, ../import-guidelines/SKILL.md, ../status/SKILL.md
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Bash Glob Grep

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 missing-ref reference to a missing file: ../brand-setup/SKILL.md
  • warning missing-ref reference to a missing file: ../import-guidelines/SKILL.md
  • warning missing-ref reference to a missing file: ../status/SKILL.md
  • warning missing-ref reference to a missing file: ../check/SKILL.md
  • warning missing-ref reference to a missing file: ../switch-brand/SKILL.md
  • warning missing-ref reference to a missing file: scripts/connector-status.py
  • warning missing-ref reference to a missing file: scripts/resolve_model.py
  • note edit-residue the text marks something as outdated (lines 25, 26, 108): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 51/100

Will not run. References files that are not bundled: ../brand-setup/SKILL.md, ../import-guidelines/SKILL.md, ../status/SKILL.md
  • 0Tools and files. 7 referenced file(s) missing: ../brand-setup/SKILL.md, ../import-guidelines/SKILL.md, ../status/SKILL.md
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 20 steps, 1 vague phrases
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3108 tokens
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (5 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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 108: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 20 items
  • +4Has examples (8 code blocks)

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