Menu
Canonical datum authoring conventions: [b00t] required fields, [b00t.skill] tags, tail-map footer.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Canonical b00t reviewer capability — adversarial multi-framework code/datum review. Shared across all harnesses (Claude Code, opencode, Hermes, b00t-cli). Loaded via: b00t learn reviewer, or by harness-specific role supplements.
Remove AI-generated artifacts from code. Three-phase certainty-graded cleanup. Use after any AI implementation session or before PR creation.
8-phase agile workflow — strategy→ideate→brainstorm→plan→work→review→compound→pulse. State machine with FOL-guarded transitions, gh-issues backlog, executable just harness. Inspired by everyinc/compound-engineering-plugin.
Australian crypto tax treatment per ATO guidance QC 53725. Crypto assets are CGT assets under ITAA 1997 s 108-5. Each disposal triggers CGT event A1. Covers personal-use exception, trading stock test, and the 50% CGT discount.
Australian R&D Tax Incentive (RDTI) — ITAA 1997 Division 355. Covers eligibility criteria for core and supporting R&D activities, registration with AusIndustry/IP Australia, expenditure categories, offset rates, and the company size threshold test.
Evidence graph construction for tax audit trails. Each Satisfies check emits EvidenceNode structs with Blake3 content hashes. Evidence chains are tamper-evident and link legislative citations to factual findings.
| name | datum-authoring |
| type | skill |
| hint | Canonical datum schema reference — required fields, tail-map format, forbidden fields |
| version | 1.0.0 |
| tags | ["datum","authoring","schema","blessing","prerequisite"] |
| tier | ch0nky |
| complexity | 6 |
| description | Canonical datum authoring conventions: [b00t] required fields, [b00t.skill] tags, tail-map footer. |
The datum-authoring skill defines the canonical conventions for authoring b00t datums. Required [b00t] fields are: name (unique kebab-case identifier), type (one of the datum types), and hint (≤120 chars). Skill datums use [b00t.skill] with tags (not type_tags — that field is deprecated). Every datum must include the # b00t:map v1 tail section with summary, tags, tier, cmds, and complexity. Forbidden patterns include [b00t.version] — use [b00t.schema] instead.
This skill depends on datum-schema and tomllm-format, and unlocks _b00t_-write capability. It applies to all _b00t_/*.toml and _b00t_/*.datum.toml files.
Load this skill before authoring or editing any b00t datum file. It is a prerequisite for writing datums that will be consumed by the b00t ecosystem.
datum-schema and tomllm-format first._b00t_/<name>.toml (or .tomllm/.tomllmd).[b00t] with name, type, and hint.[b00t.skill] with tags, depends_on, unlocks as needed.# b00t:map v1 tail-map as the footer.[b00t.version], no type_tags.