SKILLEMALL.ai
GitHub ↗ RU Sign in

CB team-assign

Assign marketing tasks to team members by role fit and workload. "who should write the Q2 email sequence"

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

Assign marketing tasks to team members by role fit and workload.

As a process B 71/100 · Nearly there — weak spots: when it triggers

ProcedureAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
68
Run on models
none yet
Process rating
B
71/100
Nearly there
When it triggers w 12
20
Tools and files w 18
60
Result and completion w 14
60
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 71/100

  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 65Failures and branches. 3 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 42 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3179 tokens
  • 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)
  • +3Description length 105: 120–800 characters recommended
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 42 items
  • +3Output format is stated explicitly

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