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/org-auki
SkillsMP has collected 16 skills from aukilabs/org-auki. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 16
- GitHub stars
- 0
- GitHub forks
- 0
Skills in this repository
Showing 16 of 16 collected skills.
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…
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.…
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…
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…
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…
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,…
Takes an uploaded file (PDF, HTML, markdown, or plain text) and re-renders it as a polished, self-contained HTML document using the Auki design system (colours + token set). Use when someone wants a polished, self-contained branded document.
Use when designing or reviewing a piece of content for memetic fitness — tweets, blog posts, talks, product copy, any artifact meant to spread. Scores the meme across four dimensions (Observability, Fidelity, Self-normalization, Incentive).
Use when the user asks for tasks, a weekly plan, or "what should I work on." Combines user.md, user_role.md, goals.md, and every linked project's sprint.md into a role-filtered task list written to tasks.md.
Use when writing an investor update. Structures the update around a shareable Hook & Ask (the part most investors will actually read) followed by mission/momentum, traction, strategy validation, and team — optimized for the retell test.
Use when evaluating a UI design change — individually or collaboratively. Scores the delta across four dimensions (Logic, Intuition, Ergonomic, Aesthetic) so you can reason about whether the change is actually an improvement and whether it optimizes for what…
Use when writing persuasive content (sales pitches, blog posts, speeches, marketing copy) or structuring an argument. Applies the NASA method (Need → Acceptance → Solution → Acceptance) to make sure context is loaded into the listener's attention before the…
Use when creating a new Auki project exocortex. Produces the standard file structure (README, vision, AGENTS, CONTRIBUTING, roadmap, glossary, CHANGELOG, parking_lot, src/ with readme and sprint) and adds the project to the canonical list in…
Use when syncing or aggregating changelog decisions from sub-repos up to a quest's main changelog. Use this on a cron schedule to ensure no human-written sub-repo decisions are missed in the quest's aggregated view.
Use when crafting a narrative, launch story, product announcement, talk opening, or pitch. Structures communication as Why → How → What so the audience buys into the purpose before evaluating the product.