Agent Skills: synthesis-writer
Use when `evidence-review` has completed extraction and needs a bounded narrative synthesis.
ID: willoscar/research-units-pipeline-skills/synthesis-writer
51039
Install this agent skill to your local
Skill Files
The files that make up synthesis-writer.
Loading file tree…
More agent skills
- baoyu-post-to-weiboPosts content to Weibo (微博). Supports regular posts with text, images, and videos, and headline articles (头条文章) with Markdown input via Chrome CDP. Use when user asks to "post to Weibo", "发微博", "发布微博", "publish to Weibo", "share on Weibo", "写微博", or "微博头条文章".
- data-client-endpoint-setupSet up @data-client/endpoint for custom async operations. Wraps existing async functions with Endpoint for use with Data Client hooks. Use after data-client-setup detects non-REST/GraphQL async patterns.
- node-inspect-debuggerDebug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.
- customizing-statuslineCreates, edits, and migrates Letta Code statusline mods. Use when handling the /statusline command or continuing work started by /statusline.
- figma-generate-libraryBuild or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. This skill teaches WHAT to build and in WHAT ORDER — it complements the `figma-use` skill which teaches HOW to call the Plugin API. Both skills should be loaded together.
- working-with-legacy-codeSafely change and test untested codebases using Feathers'' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.