Imported from drewstone/dotfiles (
claude/skills/tangle-blockchain-blueprint/SKILL.md). Install upstream withnpx skills add drewstone/dotfiles --skill tangle-blockchain-blueprint. Copyright stays with the author.
Tangle Blockchain Blueprint
Use this for on-chain Blueprint protocol and service behavior. Agent apps and general sandbox infrastructure have different ownership and are outside this skill.
Resolve protocol and product evidence
Start with the maintained Blueprint documentation and Blueprint SDK. Read the current introduction, service lifecycle, and relevant operator or application guide. Follow their contract links to the protocol implementation used by the product. Check the selected chain and deployed contracts before claiming behavior is live.
Inspect the product repository before claiming it supplies an indexer, operator API, TEE, settlement process, or hosted application. A roadmap or shared protocol component does not establish that the product implements it.
Preserve the domain boundaries
- A blueprint defines the template, metadata, jobs, artifacts, and application policy.
- Operator registration advertises ability to serve the blueprint.
- A service creation flow selects operators and parameters under the protocol's current request or quote contract.
- The service instance is the live configured unit the user interacts with.
- Jobs change service state; ordinary reads use contracts, protocol indexing, or an operator API as appropriate.
Distinguish on-chain enforcement from hosted behavior and protocol state from runtime health. Document which repository owns each claimed artifact. For stateful or custodial services, inspect expiry, operator changes, renewal, and exit behavior before assuming execution continues indefinitely.
Validate the changed behavior
For protocol or runtime changes, use the repository's current checks and a production-like deploy, register, create-service, and job flow. Exercise the creation path actually used by the product, including request approval or quotes where relevant. Test tenant authorization when the service spans users or accounts. For UI changes, build and click through the actual contract or operator integration. For documentation changes, verify each substantive claim against source and run the owning docs checks.
Report source and deployment evidence, exact checks, retained domain boundaries, and any behavior not exercised.
Log the run
skill-run-log /tangle-blockchain-blueprint --target "<target>" --verdict <VERDICT> --next /<next-skill-or-stop>Then consider
convergewhen the required checks fail.hardenwhen a changed tenant, operator, custody, or contract boundary needs adversarial tests.docs-slop-auditwhen product documentation needs claim-by-claim review.ui-testwhen visible service flows need broader interaction coverage.verifywhen implementation is complete and release proof remains.