name	technical-scope-forum
description	Use when you need to discover Sky Forum technical scope posts from forum.skyeco.com, map them to the title-first template catalog, or update templates while enforcing technical-scope tags, auditor PDF links, SHA-pinned GitHub provenance, checksummed addresses, and explorer links.

Technical Scope Forum

Use this skill to maintain the technical scope template library in this repo.

Run skills/technical-scope-forum/scripts/discover_topics.sh.
Read templates/catalog.yaml, templates/template-metadata.yaml, and agents.md.
Match each discovered topic to one template family.
If an existing family fits, update only the catalog mapping.
If both title and heading patterns are new, add a new human-facing template under templates/ and a new metadata entry in templates/template-metadata.yaml.

Primary source: https://forum.skyeco.com/search.json?q=%22technical%20scope%22%20in%3Atitle
Keep only titles that contain technical scope case-insensitively.
Secondary source: https://forum.skyeco.com/tag/technical-scope/1444.json
Add only tag-only outliers whose headings clearly match technical-scope structure.
Missing technical-scope is a compliance issue, not a reason to drop the topic.

Every draft must require the technical-scope forum tag.
Every template should read like a forum post draft and link to a best-in-class example near the top.
Audit links must resolve directly to PDF files hosted by the auditor.
Every audit PDF must have a matching SHA-pinned GitHub blob, tree, or commit link.
EVM addresses must be EIP-55 checksummed.
EVM deployments should link to Etherscan when available.
Non-EVM identifiers still need an appropriate explorer link.

technical-scope-forum