菜单
Post-processing skill that audits a generated presentation for NDA and sensitive material, then rewrites flagged content with appropriate public-facing language. Called automatically by /presentation when audience is community — the only public audience. Never invoked for internal, investor, or client presentations.
Generates a combined community-facing presentation that aggregates all internal weekly updates into a single master document. Run once per week after individual updates have been committed. Reads all presentations from the target week in aukilabs/presentations, synthesises them by project, applies NDA redaction, and commits a community-update page to community/week-{NN}.html. Always community audience — this is the outward-facing digest.
Sub-skill called by /presentation and /presentation-external (the router skills). Auto-populates presentation context from a contributor's work in the current ISO week — reads CHANGELOG entries, merged PRs, closed issues, and skill diffs since the most recent past Friday. Returns a structured digest that the router passes down to /slides or /page. Reduces user-prompting burden by pre-filling "what shipped, what's in progress, what's next".
Generates an Auki Labs weekly update as a styled scrollable HTML document (single page, print-friendly). Use when someone wants to create a weekly update, work update, team update, one-pager, or progress report in document form (vs. a slide deck). Routes through audience selection and gathers content via probing questions before generating the file. Calls /harvest to pre-fill context from Git when available.
Starting point for creating an internal Auki Labs presentation. Use when any team member wants to create a weekly update, work summary, or team presentation. Always internal audience — no audience question asked. Offers two formats: slides (reveal.js deck) or one-pager (scrollable HTML document). Employees always start here for internal work; use /presentation-external for investor, client, or community-facing output.
Generates a self-contained reveal.js HTML slide deck. Handles two modes — weekly update (default) and product deck. Weekly update mode gathers work via /harvest and tells the story of a contributor's week. Product deck mode gathers product/company information and produces a standalone pitch or product presentation. Both modes share the same slide types, design system, and themes.
Use when creating a cross-repo quest. Everything lives in a single GitHub Project created from the Auki Kanban Template ([REDACTED - link to your organization's Kanban template]). The project README holds the demo definition, demo script, constraints, tests, and repos overview. Questions and Tasks are cards on the Kanban board. No git mirror, no Notion, no separate changelog/relay files. Minimal token footprint.
| name | nda-redact |
| description | Post-processing skill that audits a generated presentation for NDA and sensitive material, then rewrites flagged content with appropriate public-facing language. Called automatically by /presentation when audience is community — the only public audience. Never invoked for internal, investor, or client presentations. |
Audits a generated roundup or slide deck for sensitive content and rewrites flagged passages before the file is committed. Never removes sections entirely — always replaces with appropriate language that preserves the narrative while removing the sensitive detail.
Called by /presentation after generation is complete, before the file is written to disk. Only runs for community audience — the only public one. investor and client presentations go to the private repo and are shared directly by the company, so they do not need NDA redaction (though their tone and content emphasis still differ from internal).
Receives:
communityWrite replacements that:
Bad replacement: "We made progress on some internal initiatives." Good replacement: "We completed a significant infrastructure improvement that reduces a key latency metric by more than 50%."
Return the full HTML with replacements applied inline. Flag each change with an HTML comment so the author can review:
<!-- NDA-REDACTED: "Acme Corp pilot" → "a major retail pilot" -->
After processing, summarise what was changed for the author:
The author wrote this. They know what's sensitive. If anything is borderline, surface it rather than silently removing it. The goal is an output the author is confident sharing, not one they discover has been over-sanitised.