SKILLEMALL.ai

CF four-core-documents

Produce the Part 3 Four Core Documents: business, segmentation, positioning, DMFlow. "produce the four core documents"

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

Produce the Part 3 Four Core Documents: business, segmentation, positioning, DMFlow.

As a process F 34/100 · No process to follow — References files that are not bundled: ../context-engine/four-core-documents-spec.md, ../context-engine/engagement-flow-methodology.md, ../context-engine/actionable-persona-format.md

GeneratorMarketingtype and topics are labelled automatically from the skill text
JSON
Technical rating
C
79/100
safety, quality, tests
Safety 60%
95
Quality 40%
55
Run on models
none yet
Process rating
F
34/100
No process to follow
References files that are not bundled: ../context-engine/four-core-documents-spec.md, ../context-engine/engagement-flow-methodology.md, ../context-engine/actionable-persona-format.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

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 Write Edit 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: ../context-engine/four-core-documents-spec.md
  • warning missing-ref reference to a missing file: ../context-engine/engagement-flow-methodology.md
  • warning missing-ref reference to a missing file: ../context-engine/actionable-persona-format.md
  • warning missing-ref reference to a missing file: ../context-engine/b2b-decision-making-unit.md
  • warning missing-ref reference to a missing file: ../context-engine/five-digital-markets.md
  • warning missing-ref reference to a missing file: ../context-engine/in-market-out-market.md
  • warning missing-ref reference to a missing file: ../context-engine/channel-families.md
  • warning missing-ref reference to a missing file: ../context-engine/decision-framework.md
  • warning missing-ref reference to a missing file: ../context-engine/unit-economics-framework.md
  • note frontmatter-key unknown frontmatter key "engagement-part"
  • note frontmatter-key unknown frontmatter key "view-preference"

Process rating: all ten parameters 34/100

Will not run. References files that are not bundled: ../context-engine/four-core-documents-spec.md, ../context-engine/engagement-flow-methodology.md, ../context-engine/actionable-persona-format.md
  • 0Tools and files. 9 referenced file(s) missing: ../context-engine/four-core-documents-spec.md, ../context-engine/engagement-flow-methodology.md, ../context-engine/actionable-persona-format.md
  • 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
  • 30Running it twice. 1 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 85Steps. 116 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3852 tokens
  • low 12 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)
  • +3Description length 118: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 116 items
  • +4Has examples (9 code blocks)

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