BB candidate-talent-pool
Candidate and prospect pool: contact details, experience, skills, consent status and date, referral source and last contact. Use for talent pipelines and re-engagement.
Candidate pool management skill: contacts, experience, skills, consent status with date, referral source, last contact. Promises to organize talent pipeline and re-engagement workflow.
Files intact, no critical errors. Quality score 79 is mid-range for a workflow. Process score 66 signals gaps in logic or docs. No sandbox or model runs—actual behavior untested. Supports Claude and Hermes.
Worth installing if you need basic CRM structure. Before production use, verify how it handles consent records and filters contacts—that's where HR systems typically break.
Candidate and prospect pool: contact details, experience, skills, consent status and date, referral source and last contact.
As a process B 66/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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-long-hermesdescription is 168 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "source_repo"
Process rating: all ten parameters 66/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 4 mutating operations with no state check
- 60Failures and branches. 2 branches
- 70Execution cost. Instruction body is 4355 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 40 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 168: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.