القائمة
Use when summarizing an article, paper, transcript, or doc - with verbatim quotes for the most important claims
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the meta-builder routes to kind=discipline. Generates a discipline spell with the rule, excuses table, warning signs, and hard gates.
Use when the user wants to capture a repeatable task as a reusable spell, or asks "how do I build a workflow / skill / framework for X"
Use when the meta-builder routes to kind=subagent. Generates a spell that dispatches one or more subagents to do work in parallel or in isolation.
Use when the meta-builder routes to kind=workflow. Generates a workflow spell with explicit stages, checkpoints, and loop-back conditions.
Use when composing multiple spells into a chain that runs end-to-end (e.g. brainstorm -> plan -> execute -> verify).
Use when browsing what spells are available - bundled seeds, your personal library, or both. Filter by kind, audience, or update status.
| name | summarizing-a-document |
| description | Use when summarizing an article, paper, transcript, or doc - with verbatim quotes for the most important claims |
| kind | content |
| audience | anyone |
| ai-tools | any |
| complexity | simple |
| time | 5-10 min |
| version | 1.0.0 |
| source | bundled |
Produces a short, scannable summary of a longer source. The summary's central claims are each backed by a verbatim quote so the reader can verify quickly.
A markdown summary with: a one-sentence takeaway at the top, then 3-5 bullets, each pairing a claim (in your words) with a verbatim quote from the source.
Input: A 2,000-word article on remote work productivity for an engineering manager.
Output:
Takeaway: Async-first teams should default to written status updates over meetings; the data shows 25% productivity gains but only when managers also reduce 1:1 cadence.
- Async beats sync for individual contributor productivity — "Engineers in async-first teams shipped 25% more features per sprint than peers in sync-first teams." (para 4)
- The gain disappears if managers don't also adjust — "Managers who maintained weekly 1:1s erased the async productivity gain." (para 7)
- ...
