specification-writing

specification-writing is a skill for Claude Code from raja21068/AutoResearch. It costs 49 tokens per session (1,941 once invoked), scanned A, a copy of specification-writing, MIT.

A workflow for writing a complete patent specification from patent claims and an invention disclosure. A patent specification is the detailed description that explains and supports what the claims seek to protect.

In plain words
What is it for?
Use it to draft a patent description in a selected jurisdiction and language, using existing claims, invention details, prior-art findings, and figures.
Why use it?
It helps organize the technical description around the claims and relevant prior art. This reduces the chance that the description and claims do not support each other.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Codex.

Good fit Use it to draft a patent description in a selected jurisdiction and language, using existing claims, invention details, prior-art findings, and figures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/raja21068/autoresearch/specification-writing
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add raja21068/AutoResearch --skill specification-writing
Clone the repo
git clone --depth 1 https://github.com/raja21068/AutoResearch

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for specification-writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/raja21068/autoresearch/specification-writing/github.svg)](https://agentmods.dev/skills/raja21068/autoresearch/specification-writing)
Your own site
<a href="https://agentmods.dev/skills/raja21068/autoresearch/specification-writing"><img src="https://agentmods.dev/badge/skills/raja21068/autoresearch/specification-writing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for specification-writing

Your own site · 80×15
<a href="https://agentmods.dev/skills/raja21068/autoresearch/specification-writing"><img src="https://agentmods.dev/badge/skills/raja21068/autoresearch/specification-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,941 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01941
Opus 5 $0.00024 $0.00971
Sonnet 5 $0.00010 $0.00388
Haiku 4.5 $0.00005 $0.00194

Measured 8d ago against content hash 2285d0e41be8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

specification-writing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

91% identical to specification-writing — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/aris/skills-codex/specification-writing/SKILL.md · 212 lines

How it starts

The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Specification Writing: Section-by-Section Patent Description

Write the patent specification based on: $ARGUMENTS

Adapted from /paper-write for patent specifications. The specification supports the claims -- it is not a paper.

Constants

  • REVIEWER_MODEL = gpt-5.4 — External reviewer for specification quality
  • JURISDICTION = "auto" — Inherit from pipeline or detect from args; CN, US, EP, ALL
  • OUTPUT_FORMAT = "markdown" — Markdown drafts; converted to filing format by /jurisdiction-format
  • OUTPUT_DIR = "patent/" — Base output directory
  • LANGUAGE = "auto" — Auto from jurisdiction: CN->Chinese, US/EP->English

Inputs

  1. patent/CLAIMS.md — the drafted claims (primary source)
  2. patent/INVENTION_DISCLOSURE.md — invention decomposition
  3. patent/PRIOR_ART_REPORT.md — for background section
  4. User-provided figures (if any)

Shared References

Load ../shared-references/patent-writing-principles.md for specification writing rules, language guidelines, and reference numeral conventions. Load ../shared-references/patent-format-cn.md or patent-format-us.md or patent-format-ep.md based on jurisdiction.

Workflow

Step 1: Initialize Specification Structure

Create the output directory and section files:

patent/specification/
├── title.md
├── technical_field.md
├── background.md
├── summary.md
├── drawings_description.md
├── detailed_description.md
└── abstract.md

Step 2: Write Title (发明名称)

  • Must match the broadest claim scope
  • No trademarks, no "improved" or "new" or "novel"
  • CN format: "一种[领域]的[技术主题]" or "[领域]的[技术主题]装置"
  • US/EP format: "[Technical topic] for [purpose]" or "[Technical topic] and method thereof"
  • Keep concise (CN: typically under 25 characters; US: under 500 characters)

Step 3: Write Technical Field (技术领域)

1-2 paragraphs identifying the technical domain:

  • "The present invention relates to [broad field], and more particularly to [specific area]."
  • CN: "本发明涉及[技术领域],具体涉及[具体领域]。"

Read the full file on GitHub · 212 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 212 lines · 49 tokens per session scan A 2285d0e41be8

Subscribe to this mod's changes

specification-writing is a skill published in the GitHub repository raja21068/AutoResearch (2 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 1,941 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to specification-writing, differing in 10 lines, and is treated as a copy.

Related

Other skills, from other repositories

literature-review-agent

Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). Execute the literature search strategy from outline.json — discover candidate papers via web search, verify them through Semantic Scholar (Levenshtein > 70 fuzzy title match, temporal cutoff, dedup by paperId), cross-corroborate against Crossref + OpenAlex to…

Ar9av/PaperOrchestra · 149 tokens

content-refinement-agent

Step 5 of the PaperOrchestra pipeline (arXiv:2604.05018). Iteratively refine drafts/paper.tex by simulating peer review and applying targeted revisions, with strict accept/revert halt rules, deterministic 0-100 decision bands (Accept/Minor/Major/Reject) that drive a target-met early stop, and a Devil's Advocate…

Ar9av/PaperOrchestra · 145 tokens

agent-research-aggregator

Pre-pipeline aggregator that scans AI agent cache directories (.claude, .cursor, .antigravity, .openclaw) or any user-specified directory for experimentation logs, extracts insights and numeric results, and formats them as PaperOrchestra-ready inputs (idea.md + experimentallog.md). TRIGGER when the user says…

Ar9av/PaperOrchestra · 177 tokens

paper-orchestra

Orchestrate the full PaperOrchestra (Song et al., 2026, arXiv:2604.05018) five-agent pipeline to turn unstructured research materials (idea, experimental log, LaTeX template, conference guidelines, optional figures) into a submission-ready LaTeX manuscript and compiled PDF. TRIGGER when the user asks to "write a paper…

Ar9av/PaperOrchestra · 143 tokens

section-writing-agent

Step 4 of the PaperOrchestra pipeline (arXiv:2604.05018). ONE single multimodal LLM call that drafts the remaining paper sections (Abstract, Methodology, Experiments, Conclusion), extracts numeric values from experimentallog.md into LaTeX booktabs tables, splices the generated figures from Step 2, and merges…

Ar9av/PaperOrchestra · 125 tokens

outline-agent

Step 1 of the PaperOrchestra pipeline (arXiv:2604.05018). Convert (idea.md, experimentallog.md, template.tex, conferenceguidelines.md) into a strict JSON outline containing a plotting plan, literature search plan (Intro + Related Work), and section-level writing plan with citation hints. TRIGGER when the orchestrator…

Ar9av/PaperOrchestra · 99 tokens