Imported from octavehq/lfgtm-codex (
skills/octave-digest/SKILL.md). Install upstream withnpx skills add octavehq/lfgtm-codex --skill octave-digest. Copyright stays with the author.
/octave-digest - GTM Insight Digest
Run the task
Read the task method before selecting context, claims, or output. It is the execution method for this skill. Supporting templates supply structure and styling; populate them from the task method and current evidence, not their illustrative figures or assertions.
Use completed reports and preserve evidence depth, source scope and uncertainty. Actions and timelines are task-dependent. Authorized recurring runs reuse saved scope; broadened distribution pauses dependent publication. Use workspace-bound durable state, lock and consumed-report checkpoint after verified output. Render-only handoffs select the actual format gate.
Use GTM context for strategic tasks and evidence and inputs for material claims and missing facts. A narrow list/get or a render-only handoff does not require unrelated research. Read host runtime for available tools, portable resource paths, routing, and review fallback.
Resolve current tool schemas before execution; use returned IDs and pagination. Inventory rows locate records; hydrate selected entities/resources before relying on their contents. Reuse supplied or inherited context and authorization. Ask grouped questions only for material unresolved inputs, continue independent work, incorporate replies, and recheck affected output.
Usage
Use /octave-digest with the requested task, target, and output.
References by task
Read only the reference for the selected mode, then the format/layout references when rendering. Do not repeat intake or change approved claims when routing to a renderer.
Delivery and changes
Apply output readiness to text and artifacts. HTML also uses the review protocol and the matching format checks. A working preview can be shared with its status; unrun checks are NOT RUN. Reviewers return findings on an immutable version; one author applies edits and rechecks the final version.
For visual output, inherit the selected sender/workspace brand through brand kit usage; honor an explicit override and avoid repeated brand extraction. Public hosting requires the approved audience and publish manifest, followed by URL/access/link verification.
For comparisons, trends or rates, use the analytics contract. Only requested persistence loads workspace mutations; report changes as applied only after scoped readback.