Run any Skill in Manus with one click

sigma-present

Stars3

Forks1

UpdatedJune 17, 2026 at 13:28

Export sigma markdown artifacts (research.md, spec.md, plans, verify results, kanban board.md) as a polished, single self-contained HTML file — either an interactive reveal.js slide DECK or a long-scroll animated REPORT page, with an optional kanban snapshot. Use when the user wants to share, present, email, or hand off a sigma artifact as a standalone .html (or print it to PDF) rather than as raw markdown. Triggers: "turn this spec into slides", "export research as a report", "make a deck from the board", "share these verify results".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

navidgh66

navidgh66/sigma

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Web DevelopersComputer and Mathematical Occupations·SOC 15-1254

File Explorer

6 files

SKILL.md

readonly

name	sigma-present
description	Export sigma markdown artifacts (research.md, spec.md, plans, verify results, kanban board.md) as a polished, single self-contained HTML file — either an interactive reveal.js slide DECK or a long-scroll animated REPORT page, with an optional kanban snapshot. Use when the user wants to share, present, email, or hand off a sigma artifact as a standalone .html (or print it to PDF) rather than as raw markdown. Triggers: "turn this spec into slides", "export research as a report", "make a deck from the board", "share these verify results".
origin	sigma

sigma-present

Transform a sigma artifact into a single portable .html that opens anywhere, prints to PDF, and looks intentional — not a generic template.

This skill is an artifact transform, not a freeform deck designer. (For building a presentation from scratch / from a topic, use frontend-slides.) Here the input is always an existing sigma markdown artifact and the output is a deterministic, citation-aware deck or report.

When to use

The user has a sigma artifact (research.md, proposals.md, architecture.md, spec.md, tasks.md, a plan, verify output, or board.md) and wants to share / present / email / archive it as HTML or PDF.
They say "slides", "deck", "present", "report", "export", "share", "hand off".

Mode decision (pick one)

Trigger	Mode	Template
"slides", "deck", "present", "pitch", "talk"	DECK (reveal.js)	`templates/deck.reveal.html`
"report", "page", "write-up", long narrative (research/spec/verify)	REPORT (scroll)	`templates/report.scroll.html`
`board.md`, "kanban", "board snapshot", "status"	KANBAN	`templates/kanban.board.html`

Default: a narrative artifact (research/spec/plan/verify) → REPORT unless the user says slides/deck/present. board.md → KANBAN. A pitch/talk → DECK.

Workflow

Locate the artifact. Read from sigma/specs/{date}-{slug}/. Validate it exists; if not, say so and stop (fail fast, clear message). Identify the stage it came from for the provenance footer.
Pick the mode per the table above.
Ingest & section-map — see INGEST.md. Map markdown headings → slides or scroll sections; pull out citations; flag fact vs inference.
Pick a theme from THEMES.md. Default light/editorial; dark only if asked. Wire the palette into both CSS variables and any Chart.js colors. Hold the line on design quality: one direction, scale-contrast hierarchy, intentional spacing — never a uniform card grid or stock gradient hero.
Emit the file from the matching template, filling its placeholders.
- Default: CDN <link>/<script> (small, emailable).
- --inline / "offline": inline the dist CSS/JS and base64 images so the file needs no network.
Motion + a11y pass (mandatory).
- Animate only compositor-friendly props (transform, opacity, clip-path).
- Every emitted file includes a prefers-reduced-motion: reduce block.
- Reports include the IntersectionObserver fallback for engines without animation-timeline: view() (e.g. Firefox).
Provenance footer + citations. Render "Generated by sigma · {stage} · {date} · source: {slug}" and a Sources section/end-slide from the artifact's citations.
Deliver. Write export.html (or export.deck.html / export.report.html) next to the artifact. Tell the user the path and how to get a PDF:
- DECK: open with ?print-pdf appended, then browser Print.
- REPORT/KANBAN: browser Print (a @media print block disables motion).

Output rules

Single file whenever possible. CDN by default; fully inlined on request.
Charts via Chart.js (CDN, or inlined for offline). Treat charts as part of the theme — pass the CSS-variable palette into chart colors.
No template look. See the web design-quality bar: hierarchy via scale, intentional rhythm, real type pairing, designed hover/focus states.

Files in this skill

templates/deck.reveal.html — reveal.js single-file deck boilerplate.
templates/report.scroll.html — framework-free long-scroll report.
templates/kanban.board.html — column/card board snapshot.
THEMES.md — named CSS-variable palettes + font pairings.
INGEST.md — artifact → section mapping rules.

Common mistakes

Forcing a long report into slides (or vice versa) — pick the mode by content.
Dropping citations — sigma artifacts are cited; the export must keep them.
Animating layout props or omitting the reduced-motion guard.
Shipping a multi-file build — keep it one portable .html.

More from this repository

same repository

sigma-claude-md

navidgh66/sigma

Check or scaffold CLAUDE.md / CLAUDE.local.md against best-practice research (official Anthropic guidance + community consensus + real-world examples). Use when running /claude-md-check or /claude-md-create, when a human asks to "check", "audit", "improve", or "review" a CLAUDE.md file, or when scaffolding a new one and native /init would produce unbounded, undisciplined output. Carries the length/structure/specificity rubric both commands share.

2026-07-103

sigma-cost

navidgh66/sigma

Estimate, measure, and optimize token cost for sigma's heavy operations (review's three axes, the profile walk, loop cycles, multi-model research). Use before running a heavy op to size it and pick model tiers, and after to record actual spend and report trends. Triggers: "how expensive", "estimate cost", "which model should this axis use", "what's burning tokens", "sigma cost", or before any multi-axis review / loop / deep research run.

2026-07-043

sigma-docs

navidgh66/sigma

Generate EXTERNAL-facing project documentation from the codebase itself — README, API/reference docs (from code signatures + docstrings), CHANGELOG / release notes (from git log), and an "about this project" presentation. Grounds in ARCHITECTURE.md when present; delegates HTML/theming for presentations to sigma-present. Use when the user wants docs for an AUDIENCE (users, contributors, release readers) — not internal onboarding. Triggers: "write a README", "generate API docs", "draft release notes", "make a project overview deck", "document this for users".

2026-07-043

code-simplifier

navidgh66/sigma

Use when refining already-verified code to fight AI slop — over-abstraction, dead code, duplication, needless cleverness — while preserving behaviour exactly. Powers `sigma loop --simplify`. The simplifier is a DISTINCT agent from the implementer; cleanup is re-verified, never a gate.

2026-06-293

sigma-prune

navidgh66/sigma

Find loaded-but-unused MCP servers and plugins that bloat every Claude context, and reversibly disable the dead weight to save tokens + cost. Use when the context feels heavy, tool lists are huge, or you want to trim what's loaded. Triggers: "too many tools", "context is bloated", "what MCP/plugins am I not using", "save context", "prune unused", "sigma prune", or a periodic context-hygiene pass.

2026-06-253

sigma-scout

navidgh66/sigma

Discover skills relevant to sigma's domains on skillsmp.com and keep the bundle fresh, without ever auto-installing. Use to find trending or new community skills for classic-ml / deep-learning / nlp / rl / data / agents / mlops / llm work, vet them, and pull the keepers in. Triggers: "find new skills", "what skills should sigma add", "scout skillsmp", "keep the bundle current", "any trending skills for <domain>", or a periodic bundle refresh.

2026-06-253

name	sigma-present
description	Export sigma markdown artifacts (research.md, spec.md, plans, verify results, kanban board.md) as a polished, single self-contained HTML file — either an interactive reveal.js slide DECK or a long-scroll animated REPORT page, with an optional kanban snapshot. Use when the user wants to share, present, email, or hand off a sigma artifact as a standalone .html (or print it to PDF) rather than as raw markdown. Triggers: "turn this spec into slides", "export research as a report", "make a deck from the board", "share these verify results".
origin	sigma

sigma-present

Transform a sigma artifact into a single portable .html that opens anywhere, prints to PDF, and looks intentional — not a generic template.

When to use

The user has a sigma artifact (research.md, proposals.md, architecture.md, spec.md, tasks.md, a plan, verify output, or board.md) and wants to share / present / email / archive it as HTML or PDF.
They say "slides", "deck", "present", "report", "export", "share", "hand off".

Mode decision (pick one)

Trigger	Mode	Template
"slides", "deck", "present", "pitch", "talk"	DECK (reveal.js)	`templates/deck.reveal.html`
"report", "page", "write-up", long narrative (research/spec/verify)	REPORT (scroll)	`templates/report.scroll.html`
`board.md`, "kanban", "board snapshot", "status"	KANBAN	`templates/kanban.board.html`

Default: a narrative artifact (research/spec/plan/verify) → REPORT unless the user says slides/deck/present. board.md → KANBAN. A pitch/talk → DECK.

Workflow

Locate the artifact. Read from sigma/specs/{date}-{slug}/. Validate it exists; if not, say so and stop (fail fast, clear message). Identify the stage it came from for the provenance footer.
Pick the mode per the table above.
Ingest & section-map — see INGEST.md. Map markdown headings → slides or scroll sections; pull out citations; flag fact vs inference.
Pick a theme from THEMES.md. Default light/editorial; dark only if asked. Wire the palette into both CSS variables and any Chart.js colors. Hold the line on design quality: one direction, scale-contrast hierarchy, intentional spacing — never a uniform card grid or stock gradient hero.
Emit the file from the matching template, filling its placeholders.
- Default: CDN <link>/<script> (small, emailable).
- --inline / "offline": inline the dist CSS/JS and base64 images so the file needs no network.
Motion + a11y pass (mandatory).
- Animate only compositor-friendly props (transform, opacity, clip-path).
- Every emitted file includes a prefers-reduced-motion: reduce block.
- Reports include the IntersectionObserver fallback for engines without animation-timeline: view() (e.g. Firefox).
Provenance footer + citations. Render "Generated by sigma · {stage} · {date} · source: {slug}" and a Sources section/end-slide from the artifact's citations.
Deliver. Write export.html (or export.deck.html / export.report.html) next to the artifact. Tell the user the path and how to get a PDF:
- DECK: open with ?print-pdf appended, then browser Print.
- REPORT/KANBAN: browser Print (a @media print block disables motion).

Output rules

Single file whenever possible. CDN by default; fully inlined on request.
Charts via Chart.js (CDN, or inlined for offline). Treat charts as part of the theme — pass the CSS-variable palette into chart colors.
No template look. See the web design-quality bar: hierarchy via scale, intentional rhythm, real type pairing, designed hover/focus states.

Files in this skill

templates/deck.reveal.html — reveal.js single-file deck boilerplate.
templates/report.scroll.html — framework-free long-scroll report.
templates/kanban.board.html — column/card board snapshot.
THEMES.md — named CSS-variable palettes + font pairings.
INGEST.md — artifact → section mapping rules.

Common mistakes

Forcing a long report into slides (or vice versa) — pick the mode by content.
Dropping citations — sigma artifacts are cited; the export must keep them.
Animating layout props or omitting the reduced-motion guard.
Shipping a multi-file build — keep it one portable .html.