CF business-ops
Business operations: strategy, technology, growth, competitive intelligence, support, finance, HR, legal, operations, sales, productivity, product management.
Business operations: strategy, technology, growth, competitive intelligence, support, finance, HR, legal, operations, sales, productivity, product management.
As a process F 56/100 · Will not run — References files that are not bundled: references/customer-support/*.md, references/finance/*.md, references/hr/*.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Bash Grep Glob Edit
-
low Risky intent
intent-offensive-securityreferences/operations.md:144Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Security posture (SOC 2, penetration testing, incident history)
-
low Risky intent
intent-offensive-securityreferences/operations/risk-assessment.md:105Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- When was the last penetration test?
-
low Risky intent
intent-offensive-securityreferences/operations/vendor-management.md:119Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Penetration test results | Request directly (summary) | Never conducted. Findings not remediated. Won't share summary. |
Files scanned: 66. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/customer-support/*.md - warning
missing-refreference to a missing file: references/finance/*.md - warning
missing-refreference to a missing file: references/hr/*.md - warning
missing-refreference to a missing file: references/legal/*.md - warning
missing-refreference to a missing file: references/operations/*.md - warning
missing-refreference to a missing file: references/sales/*.md - warning
missing-refreference to a missing file: references/productivity/*.md - warning
missing-refreference to a missing file: references/product-management/*.md - note
frontmatter-keyunknown frontmatter key "routing"
Process rating: all ten parameters 56/100
- 0Tools and files. 8 referenced file(s) missing: references/customer-support/*.md, references/finance/*.md, references/hr/*.md
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 4 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2086 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 158: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 4 items
- +4Reference files are cited in the instructions (24 of 24)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.