writing-kit-assembler
Looplia writer skill for assembling final writing kits. Combines content analysis and ideas into structured output with suggested outlines. Creates comprehensive WritingKit JSON with all components.
What this skill does
# Writing Kit Assembler Skill
Assemble comprehensive writing kits from analysis and ideas.
## Purpose
Combine outputs from earlier workflow steps into a final, actionable writing kit:
- Content summary and metadata
- Generated ideas (hooks, angles, questions)
- Suggested outline with sections
- Supporting quotes and references
## Process
### Step 1: Read Analysis
Read content analysis JSON (first input):
- contentId
- source metadata
- summary (headline, tldr, bullets)
- keyThemes
- importantQuotes
- coreIdeas
### Step 2: Read Ideas
Read idea synthesis JSON (second input):
- hooks
- angles
- questions
- personalization context
### Step 3: Create Suggested Outline
Design a structured outline:
```
Introduction
├── Hook (from ideas)
├── Context/Background
└── Thesis/Main Point
Body Sections (3-5)
├── Section 1: {Theme from analysis}
│ ├── Key point
│ ├── Supporting quote
│ └── Transition
├── Section 2: {Theme from analysis}
│ └── ...
└── Section N: {Theme from analysis}
Conclusion
├── Summary of key points
├── Call to action (from angles)
└── Closing thought
```
### Step 4: Map Content to Sections
For each body section:
1. Choose a key theme from analysis
2. Identify supporting quotes
3. Connect to relevant ideas/angles
4. Write section summary
### Step 5: Assemble WritingKit
Combine all components into final structure.
### Step 6: Write Output
Output complete WritingKit JSON.
## Input
Two input files:
1. Analysis JSON from media-reviewer
2. Ideas JSON from idea-synthesis
## Output Schema
```json
{
"contentId": "string",
"source": {
"type": "video|audio|article|transcript",
"title": "Original content title",
"url": "Source URL if available",
"creator": "Author/creator name"
},
"summary": {
"headline": "One compelling sentence",
"tldr": "3-5 sentence summary",
"bullets": ["Key point 1", "Key point 2", "Key point 3"],
"keyThemes": ["theme1", "theme2"],
"importantQuotes": [
{
"text": "Exact quote from source",
"timestamp": "12:34",
"context": "What was being discussed"
}
]
},
"ideas": {
"hooks": [
{ "text": "Hook text", "type": "question" }
],
"angles": [
{ "perspective": "...", "approach": "..." }
],
"questions": [
{ "text": "...", "depth": "medium" }
]
},
"suggestedOutline": {
"title": "Suggested article title",
"sections": [
{
"heading": "Introduction",
"type": "intro",
"points": ["Hook with question", "Establish context", "Preview main argument"],
"suggestedHook": "What if...?"
},
{
"heading": "Section title based on theme",
"type": "body",
"points": ["Main point", "Evidence/quote", "Analysis"],
"supportingQuote": {
"text": "Quote from source",
"timestamp": "5:23"
},
"theme": "Related theme from analysis"
},
{
"heading": "Conclusion",
"type": "conclusion",
"points": ["Summarize key insights", "Call to action", "Final thought"],
"suggestedAngle": "Skeptic's view"
}
]
},
"meta": {
"generatedAt": "2025-01-15T10:30:00Z",
"workflowVersion": "2.0.0",
"stepsCompleted": ["analyze-content", "generate-ideas", "build-writing-kit"]
}
}
```
## Outline Design Guidelines
### Introduction Section
- Start with a hook from ideas
- Establish why this matters
- Preview the structure
### Body Sections (3-5)
- One theme per section
- Include supporting quote when available
- Build logical progression
- Connect to angles where relevant
### Conclusion Section
- Summarize (don't repeat)
- Include call to action
- End with memorable thought
## Section Mapping
| Analysis Component | Outline Usage |
|--------------------|---------------|
| keyThemes | Body section headings |
| importantQuotes | Section supporting quotes |
| coreIdeas | Section key points |
| hooks | Introduction opener |
| angles | Body perspectives, conclusion CTA |
| questions | Section discussion points |
## Quality Checklist
Before outputting:
- [ ] All required fields present
- [ ] contentId matches across inputs
- [ ] At least 3 body sections
- [ ] Each body section has heading and points
- [ ] Quotes are properly attributed
- [ ] Meta includes timestamp
- [ ] JSON is valid
## Important Rules
1. **Include all components** - Don't omit summary, ideas, or outline
2. **Preserve quotes exactly** - Never paraphrase
3. **Keep timestamps** - If input has them, output has them
4. **Match contentId** - Same ID across all components
5. **Design actionable outlines** - Writer should be able to start immediately
6. **Use sonnet model** - This requires synthesis and organization
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.