systems-paper-writing

Comprehensive guide for writing systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides paragraph-level structural blueprints, writing patterns, venue-specific checklists, reviewer guidelines, LaTeX templates, and conference deadlines. Use this skill for all systems conference paper writing.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable systems-paper blueprint with clear workflows and checklists, undermined only by some philosophical padding and broken LaTeX-template references. The core progressive disclosure is sound but the missing templates/ directories are a real navigation defect.

Suggestions

Either create the referenced templates/osdi2026/, nsdi2027/, asplos2027/, and sosp2026/ directories or remove the "LaTeX Templates" section and the "LaTeX templates" claim from the description to avoid dead links.

Trim the "Writing Philosophy" section (e.g. the OS-process-state metaphor) and consolidate the per-section "Source:" attribution lines to reduce token overhead.

Move the long page-allocation and conference-difference tables into a reference file if they grow, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly dense, actionable structural guidance (page budgets, sentence counts, checklists), but the "Writing Philosophy" aphorisms and repeated "Source:" attribution lines pad the body and could be tightened without losing value.	2 / 3
Actionability	Provides concrete, copy-ready instruction: 5-sentence abstract template, the "X is better for Y in Z" thesis formula, numbered contribution lists, G1–Gn gap mapping, and the "state every conclusion three times" rule — actionable without needing code.	3 / 3
Workflow Clarity	A clear 6-step "Workflow: Structuring a New Systems Paper" sequence is paired with an explicit validation checkpoint (Step 5 runs the pre-submission checklist), matching the clear-sequence-with-checklist anchor.	3 / 3
Progressive Disclosure	The five references/.md links are real, well-signaled, and one level deep, but all four templates/ paths (osdi2026/, nsdi2027/, asplos2027/, sosp2026/) referenced in the body do not exist, breaking navigation for a promised deliverable.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with an explicit Use-when trigger, natural venue keywords, and a clearly bounded niche. It uses third-person voice and names concrete deliverables rather than vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "paragraph-level structural blueprints, writing patterns, venue-specific checklists, reviewer guidelines, LaTeX templates, and conference deadlines" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly answers what ("Provides ... blueprints, writing patterns ...") and when with an explicit trigger ("Use this skill for all systems conference paper writing"), satisfying both halves.	3 / 3
Trigger Term Quality	Natural venue keywords users would say ("systems papers", "OSDI, SOSP, ASPLOS, NSDI, and EuroSys", "conference paper writing") are well covered rather than generic jargon.	3 / 3
Distinctiveness Conflict Risk	Narrow niche of systems-conference paper writing with named venues and an explicit "Use this skill for all systems conference paper writing" trigger makes it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: Orchestra-Research/AI-Research-SKILLs
Path: 20-ml-paper-writing/systems-paper-writing/SKILL.md
Commit: 773a529

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.