AC ditto-workflow
Creates, configures, and deploys on-chain automation workflows using the Ditto Network SDK. Use when the user asks to "create a workflow", "automate on-chain", "schedule transactions", "deploy a workflow", "set up recurring transfers", "swap tokens on a schedule", "automate DeFi", "create a cron job on-chain", "trigger on event", or mentions "Ditto Network". Handles workflow building, IPFS upload, on-chain registration, simulation, and cancellation. Do NOT use for general smart contract development unrelated to Ditto workflows.
As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:98High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const ecdsaValidator = await signerToEcdsaValidator(publicClient, { signer: owner, entryPoint: { address: '0x00…032', version: '0.7' } });quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:99High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const kernelAccount = await createKernelAccount(publicClient, { plugins: { sudo: ecdsaValidator }, entryPoint: { address: '0x00…032', version: '0.7' } });quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:498High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)target: '0x69…306', // Chainlink ETH/USD on Sepolia
detector -
low Secrets in code
secret-high-entropy-tokenSKILL.md:509High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)target: '0x69…306',
detector
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6860 tokens (recommended < 5000); move details to references/
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
- 40Consistency. Frontmatter name (ditto-workflow) differs from the folder (workflow-automation-evm-wallets)
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70Execution cost. Instruction body is 6860 tokens
- 100Steps. 37 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 5 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- 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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 10 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 533: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 37 items
- +4Has examples (19 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.