| Build per-subsection writing briefs (NO PROSE) so later drafting is driven by evidence and checkable comparison axes (not outline placeholders).
npx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill subsection-briefs
outline/subsection_briefs.refined.ok freezes reviewed briefs only while the marker is newer than the briefs, declared inputs, domain packs, and generator. Stale markers are removed before backed-up regeneration.
Build deterministic H3 brief cards from outline + mapping + paper notes.
Compatibility mode is active: this skill keeps the current outline/subsection_briefs.jsonl field contract and paragraph-plan shape while moving phrase/domain logic into references/ and assets/.
scripts/run.py as the deterministic materializer.transition-weaver, writer-context-pack, and subsection-writer.Always read:
references/overview.mdRead by task:
thesis feels repetitive or copyable, read references/thesis_patterns.md.tension_statement is too generic, read references/tension_patterns.md.references/axis_catalog_generic.md and references/axis_catalog_llm_agents.md.references/bridge_terms.md.references/examples_good.md.Machine-readable assets:
assets/phrase_packs/thesis_patterns.jsonassets/phrase_packs/bridge_contrast.jsonassets/domain_packs/generic.jsonassets/domain_packs/llm_agents.jsonassets/domain_packs/embodied_ai.jsonassets/domain_packs/rag_evaluation.jsonassets/domain_packs/text_to_image.jsonThe script loads these packs first; patch them before changing Python when the issue is phrasing, domain routing, axis inventory, cluster purity, or lexical bridge coverage.
outline/outline.ymloutline/mapping.tsvpapers/paper_notes.jsonlGOAL.mdoutline/claim_evidence_matrix.mdoutline/subsection_briefs.jsonlRequired record shape remains compatibility-preserving:
sub_id, title, section_id, section_titlerq, thesis, scope_rule, axes, bridge_terms, contrast_hook, tension_statementevaluation_anchor_minimal, required_evidence_fields, clustersparagraph_plan, evidence_level_summary, generated_atrun.py Should Doassets/.run.py Should Not Dothesis/tension_statement conservative and let downstream evidence skills strengthen the subsection.bridge_terms to surface concrete lexical handles that later evidence/ranking stages can still match (OOD, sim-to-real, world model, failure detector, specific benchmark families), not only generic axis names.cluster_rules over ad-hoc bootstrap overlaps when the mapped set is already large enough to support disjoint clusters.When running in compatibility mode, scripts/run.py currently reads:
outline/outline.yml for section/subsection structureoutline/mapping.tsv for paper-to-subsection coveragepapers/paper_notes.jsonl for structured evidenceGOAL.md for topic/domain cuesoutline/claim_evidence_matrix.md as optional supporting context when presentuv run python .codex/skills/subsection-briefs/scripts/run.py --workspace <workspace>--workspace <dir>--unit-id <id>--inputs <a;b;...>--outputs <a;b;...>--checkpoint <C*>uv run python .codex/skills/subsection-briefs/scripts/run.py --workspace <workspace>GOAL.md and the asset packs before changing the script.papers/paper_notes.jsonl is thin, reroute to note extraction rather than inventing axes.Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take willoscar/subsection-briefs from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.