article-summary-architect

Draft the summary by first extracting the article's core problem, conclusion, and evidence, then write aligned zh and en versions with concise sections and bullets. Keep meaning equivalent across languages while allowing natural wording differences.

Provide the article content and ask for a detailed_summary rewrite. The skill outputs frontmatter-ready YAML with detailed_summary.zh and detailed_summary.en fields, structured with an opening sentence plus scannable sections and bullets.

A good summary states the problem, core mechanism or argument, actionable takeaway, and any caveats, all grounded in the article text. It avoids generic filler, fabricated metrics, and rigid schema labels that distract readers.

Yes, it adapts structure and tone to the article domain, including essays and learning notes. It avoids forcing technical framing onto non-technical content and selects emphasis based on the article's dominant intent.

Divergence happens when each language is written independently without checking key points against the source. The quality checklist requires major points to appear in both zh and en with consistent tone and specificity before finalizing.

Rewrite when the summary is generic enough to fit unrelated articles, contains claims not grounded in the source text, shows major zh/en divergence, or has a flat structure that readers cannot scan effectively.