القائمة
Structures a presentation narrative — the story arc, a slide-by-slide outline, and speaker notes — from results or receipts. Use to shape a talk or deck, or /present. Not for prose reports (report) or rendering visuals (asset).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Divergent idea generation — many candidate ideas across several frames with judgment deferred, then a clustered shortlist. Use to open a solution space wide, or /brainstorm. Not for developing one idea (ideate) or picking one (propose).
Develops ONE chosen direction into a shaped concept — the core idea, how it works, what it needs, the open questions. Use to deepen a single idea, or /ideate. Not for generating many (brainstorm) or deciding among them (propose).
Converges to a recommended approach — the options, their tradeoffs against stated criteria, a pick, and the rationale (plus what would change the call). Use to decide among approaches, or /propose. Not for generating options (brainstorm) or deep-diving one (ideate).
Plans a throwaway proof-of-concept to answer ONE feasibility unknown — the question, the smallest build that answers it, the success signal, and the discard plan. Use to de-risk before committing, or /prototype. Not for the real build (executor) or deciding (propose).
Produces a REDTEAM-FINDINGS.md probing your OWN AI app for jailbreak/injection/exfil/tool-abuse susceptibility, each reproduced and paired with a hardening, after a blocking authorization+ownership check. Use to red-team an owned AI system defensively.
Produces a PENTEST-PLAN.md then PENTEST-FINDINGS.md for your OWN app's attack surface (each finding reproduced, non-destructive, with remediation) after a blocking authorization+ownership check. Use to test an owned app's attack surface defensively.
| name | present |
| description | Structures a presentation narrative — the story arc, a slide-by-slide outline, and speaker notes — from results or receipts. Use to shape a talk or deck, or /present. Not for prose reports (report) or rendering visuals (asset). |
The narrative-structuring skill for reporting. Given results (receipts, a report, findings), it builds the
story of a presentation: the arc (setup → tension → resolution → ask), a slide-by-slide outline with one
message per slide, and speaker notes. It shapes the telling; it does not write the prose report (that is
report) or render the visuals (that is asset, which turns a slide spec into pixels on the DESIGN tokens).
It is read-only and advisory: it writes a PRESENTATION.md (the outline + notes), never product code or
rendered slides. The output is judged by Review — is there one clear message per slide, does the arc land
the ask, and is it grounded in the real results rather than spin?
Does: identify the audience + the single takeaway + the ask; shape the story arc; outline slides with one
message each (title + the point + what visual/data it needs); write speaker notes; ground every claim in a
receipt/result; write PRESENTATION.md + a receipt. Does not: write the prose stakeholder report (that is
report), render or design the actual slides/graphics (that is asset), or invent results not in the
evidence.
report (multi-tier stakeholder prose).asset (token-driven visual production) on this
outline.archive first; a presentation with no evidence is
spin.propose (recommendation + tradeoffs).state/receipts/*, a report output, findings, or stated outcomes.asset/dataviz to render — not rendered here).PRESENTATION.md — audience/takeaway/ask + arc + slide outline (message + needed visual) +
speaker notes.presentations/PRESENTATION.md if that dir exists) —
persistence: Ephemeral. Audience + takeaway + ask · story arc · slide-by-slide outline (one message +
the visual it needs) · speaker notes · evidence trace.<workspace>/receipts/present-receipt-<ts>.json): base schema + audience, takeaway,
ask, slide_count, arc, presentation_path. persistence: Ephemeral.Done when: PRESENTATION.md fixes the audience/takeaway/ask, shapes a story arc, outlines slides with
one grounded message each (naming the visual each needs), and includes speaker notes; a receipt records the
takeaway + slide count.
Not done if: slides carry multiple messages (a list, not a narrative); a claim is not grounded in the
results (spin); or it rendered/designed the actual slides instead of outlining them (that is asset).
Next step: asset renders the slides/graphics from this outline on the DESIGN tokens; report covers a
written prose version for those not in the room.
present structures the spoken/deck narrative;
report writes the document.present produces the outline + one
visual-need per slide; asset makes them.