AC partnerships-ecosystem
World-Class Partnerships & Ecosystem Playbook. Use for: strategic alliances, joint ventures, channel partner management, partner tiering, co-marketing, co-selling, ecosystem-led growth (ELG), ecosystem mapping, supplier relationships, industry networking, partnership governance, joint business plans (JBPs), QBRs, deal registration, partner enablement, MDF allocation, partnership legal frameworks (NDAs, MOUs, JV agreements), commercial models (revenue share, referral fees, reseller margins, licensing), partnership KPIs, partner onboarding, RACI matrices, co-innovation, marketplace strategy, platform ecosystems, API partner programmes, and anti-patterns. Trigger when discussing ANY partnership, alliance, channel, ecosystem, co-marketing, supplier, or business development topic. Also trigger for GTM strategy involving partners or indirect sales. If in doubt, use this skill.
As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 16 mutating operations with no state check
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4753 tokens
- 100Tools and files. No external tools needed
- 100Steps. 57 steps
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 18 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 883: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +4Structure: 40 headings
- +3Step-by-step instructions: 57 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.