AB web3-b2b-positioning
Expert system for positioning Web3, blockchain, and crypto-native products and services for enterprise (B2B) buyers. Use this skill whenever the user needs to explain a Web3 product to traditional companies, develop messaging for a blockchain security service, build a pitch deck or one-pager for enterprise clients, translate technical Web3 features into business value, or create sales collateral for a protocol targeting institutional buyers. Also trigger for phrases like "enterprise pitch", "B2B messaging for crypto", "positioning for traditional companies", "explain blockchain to enterprises", "security product messaging", "institutional buyers", "how to pitch Web3 to brands", "corporate Web3 adoption", "crypto company sales materials", or any task that bridges Web3 products with traditional business buyers, compliance teams, or enterprise decision-makers.
As a process B 66/100 · Nearly there — 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securitySKILL.md:211Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)> Response: "That's exactly who we want in the conversation. We have a technical package specifically for security teams that covers [architecture, audit reports, penetration testing results]. Most IT
quoted
Files scanned: 3. 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 66/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. 9 mutating operations with no state check
- 60Failures and branches. 2 branches
- 100Tools and files. No external tools needed
- 100Steps. 35 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3737 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- high The skill tells the model to perform an irreversible action with no human approval
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 869: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 9 example trigger phrases
- +4Structure: 22 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.