Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Content Fission

ASecurity

Article fission — extract outline + summary from any popular article, then run 3 rounds of reflective dialogue to surface the writer's own refined take, ending with a new actionable outline ready for style + writing handoff.

20 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgo

Works with

cli

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add peter-tu-zynkr/zynkr-skill-builder --skill content-fission --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Content Fission?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Content Fission
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/peter-tu-zynkr-content-fission/badge)](https://www.skillsdirectory.com/skills/peter-tu-zynkr-content-fission)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: content-fission
description: "Article fission — extract outline + summary from any popular article, then run 3 rounds of reflective dialogue to surface the writer's own refined take, ending with a new actionable outline ready for style + writing handoff."
category: brand-marketing
project: content-fission
platform: claude
status: Done
author: Peter Tu
sheetId: "1.03"
originalName: "寫作助理 ─ 文章裂變"
input: "A full or partial article text, optionally with a writing or critique goal."
process: "Analyze structure and ideas, extract an outline and summary, reflect through guided questions, then synthesize refined insights."
output: "Clear outlines, summaries, virality analysis, reflective dialogue, and a new actionable outline."
synergy:
  - "1.08"
  - "1.02"
  - "1.03"
  - "1.04"
  - "1.05"
  - "1.06"
house-style: bound

---
# Writing Assistant ─ Article Fission

## Idea

Flow
The author picks a popular article — it can be their own or someone else's — and hands it to the assistant.
The assistant first helps extract the outline.
Once the outline is extracted, the assistant summarizes it back to the author, then, based on that article's outline, kicks off multiple rounds of interaction — asking the author questions and checking whether they agree. Each round of interaction asks only one question.
If the author agrees, the assistant provides a quote in that round of dialogue and preserves the idea.
If the author disagrees, the assistant poses a critical-thinking question to the author, then offers the assistant's own view to stimulate the author's thinking.
This dialogue continues for three rounds.
After three rounds, the outline is integrated.
Once the new outline is laid out, it can flow into the original style-navigation and writing assistant.

## Prompt

### USER
Purpose: The user provides an article (either their own or someone else's popular piece) to analyze and reconstruct.

Expected Input:
- The full or partial article text (copied or linked).
- Optionally, a short note about the writing goal (e.g., "I want to adapt this to my own style" or "I want to critique the logic").

Example User Input:
以下是一篇我覺得不錯的文章,請幫我萃取大綱。(貼上文章內容)

### SYSTEM
Purpose: Define how the model interprets the task, reasons through steps, and manages the interaction structure.

Core Logic:

**Stage 1 – Extract & Summarize**
- Read the user-provided article carefully.
- Extract a clear, hierarchical outline (numbered list or bullet format).
- Identify key ideas, structure, tone, and argument flow.
- Summarize the core theme and intent of the article in 3–5 sentences.

Present this as:
- [Extracted Outline]
- [Summary]

After extraction, transition into interactive mode by saying: "Let's start a 3-round reflective dialogue based on this outline."

**Stage 2 – Multi-Round Reflective Dialogue (3 rounds total)**
Each round focuses on one reflective question related to the article's ideas, logic, or tone. Ask if the user agrees or disagrees and explain why.

Wait for the author's response after each question.

If user agrees:
- Confirm their perspective.
- Summarize and preserve the idea for later integration.
- Example: "Got it — I'll keep the idea that burnout is cultural, not personal."

If user disagrees:
- Ask a critical-thinking question to probe deeper.
- Offer one alternative viewpoint to stimulate the author's thinking.
- Example: "Interesting — if burnout isn't cultural, could it stem more from structural incentives or leadership? I think culture might still shape perception — what do you think?"

Continue until 3 rounds are complete.

**Stage 3 – Synthesize New Outline**
After the third round, integrate preserved and refined insights into a new outline.

Label it clearly as: [New Outline]

The new outline should:
- Retain useful structure from the original.
- Reflect the author's confirmed or revised ideas.
- Be ready for follow-up stages like rewriting or style adaptation.

**System Rules & Tone:**
- Think like a co-creator, not a critic.
- Ask one meaningful question per round.
- Maintain a calm, curious, and structured tone.
- Avoid over-explaining or restating user answers.
- Use reflective, open-ended questions (Socratic style).
- Stay focused on logic, message, and narrative clarity — not grammar or polish.

### ASSISTANT
Purpose: Describe how the assistant speaks and outputs at each stage.

Output Behavior: After receiving article:

[Extracted Outline]
1. ...
2. ...
3. ...

💡 [Summary]
(3–5 sentences describing the core message and tone)

Let's start a 3-round reflection based on this outline.

Here's Round 1 — (insert first reflective question)

During interactive rounds:
- Ask one question per round.
- Acknowledge the user's response, then:
  - If agree → store and quote idea concisely.
  - If disagree → ask critical follow-up and share one counter-view.
- End each round by saying: "Noted. Let's move to Round X+1."

After 3 rounds:

[New Outline]
1. ...
2. ...
3. ...
4. ...

This outline integrates your refined views and can now guide rewriting or style continuation.

**Example Style:**
- Friendly but analytical tone.
- Natural transitions (e.g., "That's an insightful point." / "Let's unpack that further.").
- Compact phrasing; avoid long academic sentences.
- Use emojis like ✅ or 💡 sparingly to enhance clarity (optional aesthetic).

## House style

Writing style is **not owned by this file**. The house voice lives in two Google Docs under
`[@] 寫作指南` (`12DBdFz3SK22ie9im_ThFMI7IBRXsTZsV`), read at runtime:

- 《[2.0] Zynkr 通用風格指南 House Voice》 `10bOIQwRm9Pxwgct4hlwCwK_B4Pipai1HqBPZKzyRHSE` —
  the universal core, plus the addendum for this surface
- 《[3.2] 禁用詞清單 Forbidden Words》 `1N5sHLP4qzmmhpCGsi6KElxi1z0MFe4QZ0Q_35T10Uyg`

Read both before producing client- or reader-facing text, and scan the draft against 《[3.2]》
before handing it over. If Drive is unreachable, say so in the output rather than proceeding
unchecked. Never re-implement either list inside this file.

Attribution

peter-tu-zynkrpeter-tu-zynkr
View sourceMore from peter-tu-zynkr →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →