BB Fundraising Advisor
Professional fundraising advisory skill for startups - AI-powered project assessment, pitch deck generation, valuation analysis, investor matching, and PDF processing (financial statements, OCR, reports)
Professional fundraising advisory skill for startups - AI-powered project assessment, pitch deck generation, valuation analysis, investor matching, and PDF…
As a process B 66/100 · Nearly there — weak spots: inputs and preconditions, consistency, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenexamples/basic-usage.ts:237High-entropy token-like string (may be an id, hash or a credential) (placeholder value)async function exam…ons() {placeholder -
low Secrets in code
secret-high-entropy-tokenexamples/basic-usage.ts:279High-entropy token-like string (may be an id, hash or a credential) (placeholder value)await exam…ons();
placeholder
Files scanned: 61. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 66/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (Fundraising Advisor) differs from the folder (fundraising-advisor)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4942 tokens
- 85Steps. 125 steps, 2 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 3 branches, has a failure section
- 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)
- -216 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 203: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 125 items
- +3Output format is stated explicitly
- +4Has examples (23 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.