Agent skill

write

Write blog posts from session insights with multi-perspective analysis.

View SKILL.md on GitHub Repository
Stars 87
Forks 8

Install this agent skill to your Project

npx add-skill https://github.com/jongwony/epistemic-protocols/tree/main/write/skills/write

SKILL.md

Write Skill

Transform session insights and conceptual explorations into structured, publishable content through multi-perspective analysis and iterative refinement.

When to Use

Invoke this skill when:

  • Converting framework development or analytical sessions into blog posts
  • Writing about conceptual topics requiring multi-perspective review
  • Structured iterative refinement anticipated

Skip when:

  • Technical tutorials with code (standard writing)
  • Documentation updates (direct Edit)
  • Single-pass content without review need

Workflow Overview

PROTHESIS(Context→Perspective→Inquiry→Synthesis) → FORMAT → DRAFT → REFINE → VALIDATE → FINALIZE
Phase Tool Decision Point
Prothesis /frame protocol Context-derived perspectives, parallel inquiry
Format AskUserQuestion Output type, language
Draft Write —
Refine Edit (loop) User feedback
Validate /gap Gap detection
Finalize Edit —

Phase Execution

1-3. Prothesis Protocol (Multi-Perspective Analysis)

Apply the Prothesis protocol (/frame) for epistemic analysis:

Phase 0: G(U) → C              -- Context acquisition from session/topic
Phase 1: C → {P₁...Pₙ}(C) → Pₛ -- Perspectives derived FROM context (not predefined)
Phase 2: Pₛ → ∥I(Pₛ) → R       -- Parallel inquiry with Horizon Limits
Phase 3: R → Syn(R) → L        -- Synthesis: convergence, divergence, assessment

Key differences from standalone /frame:

  • Continues automatically to Format phase after Synthesis
  • Lens L becomes input for content generation

Reference: prothesis/skills/frame/SKILL.md

4. Format Decision

Present output options:

  • Blog Post (Korean/English)
  • Essay
  • Newsletter
  • Thread

5. Draft Generation

Write initial draft to ~/.claude/.write/ directory:

  • Filename: YYYY-MM-DD-{topic-slug}.md
  • Structure: Hook → Context → Framework → Application → Implications

6. Iterative Refinement

Loop on user feedback:

  • Incremental changes → Edit directly
  • Structural changes → Generate option versions (A, B, C)

Exit conditions:

  • User approval
  • Explicit "finalize" command

7. Gap Detection

Invoke /gap for final validation:

  • Procedural gaps
  • Consideration gaps
  • Duplicate content

8. Finalization

Apply final edits. Optionally clean intermediate versions.

Quality Criteria

Metric Limit
Concepts per section ≤3
Framework components ≤5
Abstraction layers ≤2

Content Transformation

What Becomes Content

Session Element Blog Element
Problem context Opening hook
Multi-perspective analysis Framework structure
Convergence points Core thesis
Divergence points Discussion sections
Resolution approach Actionable methodology

What Gets Filtered

  • Tool invocations, command outputs
  • Trial-and-error debugging steps
  • Redundant restatements
  • Context-specific details (paths, configs)

Integration

This skill integrates with:

  • /frame — Multi-perspective analysis (Phases 1-3)
  • /gap — Gap detection (Phase 7)

Additional Resources

For detailed workflow steps and content transformation rules:

  • references/workflow.md — Complete phase descriptions

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

jongwony/epistemic-protocols

contextualize

Detect application-context mismatch after execution. Verifies applicability when correct output may not fit the actual context, producing contextualized execution. Type: (ApplicationDecontextualized, AI, CONTEXTUALIZE, Result) → ContextualizedExecution. Alias: Epharmoge(ἐφαρμογή).

87 8
Explore
jongwony/epistemic-protocols

reflexion

Cross-session learning through guided dialogue. Extracts session insights and integrates into persistent memory when session knowledge should be preserved. Alias: Reflexion.

87 8
Explore
jongwony/epistemic-protocols

gap

Gap surfacing before decisions. Raises procedural, consideration, assumption, and alternative gaps as questions when gaps go unnoticed, producing an audited decision. Type: (GapUnnoticed, AI, SURFACE, Decision) → AuditedDecision. Alias: Syneidesis(συνείδησις).

87 8
Explore
jongwony/epistemic-protocols

bound

Define epistemic boundaries per decision. Produces BoundaryMap classifying domains as user-supplies, AI-proposes, or AI-autonomous when boundary ownership is undefined. Type: (BoundaryUndefined, AI, DEFINE, TaskScope) → DefinedBoundary. Alias: Horismos(ὁρισμός).

87 8
Explore
jongwony/epistemic-protocols

verify

This skill should be used when the user asks to "verify protocols", "check consistency before commit", "validate definitions", "run pre-commit checks", "verify soundness", or wants to ensure epistemic protocol quality. Invoke explicitly with /verify for pre-commit validation.

87 8
Explore
jongwony/epistemic-protocols

clarify

Clarify intent-expression gaps. Extracts clarified intent when what you mean differs from what you said. Type: (IntentMisarticulated, Hybrid, EXTRACT, Expression) → ClarifiedIntent. Alias: Hermeneia(ἑρμηνεία).

87 8
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results