zero-yx/static_flow / skills/article-summary-architect
article-summary-architect
VerifiedCreate high-quality bilingual `detailed_summary` for StaticFlow articles. Focus on evidence, reader value, and clear structure while leaving room for flexible writing style and reasoning.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.3 KB |
| agents/openai.yaml | config | 340 B |
| references/quality-checklist.md | markdown | 1.4 KB |
| references/summary-templates.md | markdown | 1.5 KB |
| references/type-taxonomy.md | markdown | 1.3 KB |
references/summary-templates.md
View on GitHub# Summary Patterns (Reference, Not Templates)
Use this file as a pattern library. Copying a fixed structure is not required.
## 1) Minimal thinking path
Before drafting, answer:
1. What is the core problem?
2. What is the strongest conclusion?
3. What evidence/path makes it trustworthy?
4. What caveats or boundaries should readers know?
## 2) Practical writing patterns
### Pattern A: Technical deep dive
- Opening: what this article explains.
- Core mechanism: key data/control flow or design choices.
- Trade-offs: performance, complexity, maintainability.
- Actionable takeaways: when to use/avoid.
### Pattern B: Incident or debugging postmortem
- Symptom and impact.
- Root cause and triggering conditions.
- Fix and why it works.
- Regression guard and lessons learned.
### Pattern C: Comparison article
- Compared options and scope.
- Key dimensions and differences.
- Decision guidance by scenario.
### Pattern D: Non-technical essay/learning note
- Central question or viewpoint.
- Main reasoning thread.
- Practical implications for readers.
## 3) Styling guidance
- Prefer concise sections + bullets for scanability.
- Keep headings natural and reader-facing.
- Keep structure flexible: section count and bullet count should match article complexity.
- Avoid empty phrases and generic praise.
## 4) Bilingual guidance
- `zh` and `en` should carry equivalent meaning.
- Natural wording can differ; key points should not diverge.
- If one language needs slight restructuring for readability, keep factual alignment intact.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |