Author Byline
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Display clear author bylines.
Create or customize OpenSpec workflow schemas in this repository using openspec schema init and openspec schema fork.
MITAuto-check passed
Install Openspec Schema Authoring
$ npx skills add intent-driven-dev/openspec-schemas --skill openspec-schema-authoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install intent-driven-dev/openspec-schemas openspec-schema-authoring --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/intent-driven-dev/openspec-schemas.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/openspec-schema-authoring .claude/skills/openspec-schema-authoring && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "openspec-schema-authoring" agent skill from https://github.com/intent-driven-dev/openspec-schemas/tree/main/.opencode/skills/openspec-schema-authoring into .claude/skills/openspec-schema-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openspec-schema-authoring", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/intent-driven-dev/openspec-schemas/tree/main/.opencode/skills/openspec-schema-authoringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add intent-driven-dev/openspec-schemas --skill openspec-schema-authoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install intent-driven-dev/openspec-schemas openspec-schema-authoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/openspec-schemas.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opencode/skills/openspec-schema-authoring .agents/skills/openspec-schema-authoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openspec-schema-authoring" agent skill from https://github.com/intent-driven-dev/openspec-schemas/tree/main/.opencode/skills/openspec-schema-authoring into .agents/skills/openspec-schema-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openspec-schema-authoring", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add intent-driven-dev/openspec-schemas --skill openspec-schema-authoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install intent-driven-dev/openspec-schemas openspec-schema-authoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/openspec-schemas.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opencode/skills/openspec-schema-authoring .cursor/skills/openspec-schema-authoring && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "openspec-schema-authoring" agent skill from https://github.com/intent-driven-dev/openspec-schemas/tree/main/.opencode/skills/openspec-schema-authoring into .cursor/skills/openspec-schema-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openspec-schema-authoring", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/intent-driven-dev/openspec-schemas.git --path .opencode/skills/openspec-schema-authoring--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add intent-driven-dev/openspec-schemas --skill openspec-schema-authoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install intent-driven-dev/openspec-schemas openspec-schema-authoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/openspec-schemas.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opencode/skills/openspec-schema-authoring .gemini/skills/openspec-schema-authoring && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "openspec-schema-authoring" agent skill from https://github.com/intent-driven-dev/openspec-schemas/tree/main/.opencode/skills/openspec-schema-authoring into .gemini/skills/openspec-schema-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openspec-schema-authoring", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install intent-driven-dev/openspec-schemas openspec-schema-authoringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add intent-driven-dev/openspec-schemas --skill openspec-schema-authoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/intent-driven-dev/openspec-schemas.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opencode/skills/openspec-schema-authoring .github/skills/openspec-schema-authoring && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "openspec-schema-authoring" agent skill from https://github.com/intent-driven-dev/openspec-schemas/tree/main/.opencode/skills/openspec-schema-authoring into .github/skills/openspec-schema-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openspec-schema-authoring", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add intent-driven-dev/openspec-schemas --skill openspec-schema-authoring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install intent-driven-dev/openspec-schemas openspec-schema-authoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/openspec-schemas.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opencode/skills/openspec-schema-authoring .opencode/skills/openspec-schema-authoring && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "openspec-schema-authoring" agent skill from https://github.com/intent-driven-dev/openspec-schemas/tree/main/.opencode/skills/openspec-schema-authoring into .opencode/skills/openspec-schema-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openspec-schema-authoring", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
openspec-schema-authoring- GitHub stars
- 105
- Token cost
- ~757 tokens
- SKILL.md length
- 294 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create or customize OpenSpec workflow schemas in this repository using openspec schema init and openspec schema fork.
- Works in 7 steps: Choose whether you're starting fresh or… → Discover available schema sources → Option A: Create a new schema from… → …
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Openspec Schema Authoring is an agent skill from intent-driven-dev/openspec-schemas. Create or customize OpenSpec workflow schemas in this repository using openspec schema init and openspec schema fork.
Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires openspec CLI.
The repository describes itself as: Collection of OpenSpec Custom Schema for Workflows other than standard spec-driven schema that is included in OpenSpec. The licence is MIT.
Example prompts
- “/openspec-schema-authoring”
Requirements
- Compatibility (from SKILL.md): Requires openspec CLI.
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Choose whether you're starting fresh or forking
- Discover available schema sources
- Option A: Create a new schema from scratch (init)
- Option B: Customize an existing workflow (fork)
- Edit schema internals (minimal expectations)
- Validate the schema locally (required quality gate)
- Debug schema resolution (if validation or behavior is surprising)
What it can do on your machine
Read from SKILL.md and the folder at commit 4bb6de2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires openspec CLI.
From compatibility in the SKILL.md frontmatter.
Context cost
Openspec Schema Authoring loads about 757 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 294 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from intent-driven-dev/openspec-schemas at commit 4bb6de2, republished under its MIT licence (© intent-driven-dev). 294 words, ~757 tokens.
Download SKILL.mdSave it as
.claude/skills/openspec-schema-authoring/SKILL.md (or your agent's skills folder).- name
- openspec-schema-authoring
- description
- Create or customize OpenSpec workflow schemas in this repository using `openspec schema init` and `openspec schema fork`.
- compatibility
- Requires openspec CLI.
- license
- MIT
- metadata.author
- openspec-schemas
- metadata.version
- 1.0
Use this skill when you want to add or customize an OpenSpec workflow schema in this repository.
Goal: produce a copyable schema folder under openspec/schemas/<schema-name>/ containing schema.yaml and templates/.
Steps
Choose whether you're starting fresh or forking
If you want a brand-new workflow schema, use
init. If you want to customize an existing workflow (recommended), usefork.Discover available schema sources
List schemas available to fork (both this repo and upstream packages):
bash openspec schemas --jsonOption A: Create a new schema from scratch (init)
Create a new project-local schema folder:
bash openspec schema init <schema-name>Common flags:
--description "..."to describe the workflow--artifacts "proposal,specs,design,tasks"to set the artifact IDs (comma-separated)--defaultto set the schema as the project default--no-defaultto skip the interactive prompt to set as default
Result (expected):
openspec/schemas/<schema-name>/schema.yamlandopenspec/schemas/<schema-name>/templates/.Option B: Customize an existing workflow (fork)
Copy an existing schema into this repo so you can edit it:
bash openspec schema fork <source> [new-schema-name]Sources can be:
- A schema already in this repo (e.g.,
minimalist,event-driven) - A built-in upstream schema provided by the CLI (e.g.,
spec-driven,tdd)
Result (expected): a new folder under
openspec/schemas/<new-schema-name>/containingschema.yaml+templates/.- A schema already in this repo (e.g.,
Edit schema internals (minimal expectations)
When updating
openspec/schemas/<schema-name>/schema.yamland templates, ensure:artifacts[].idmatches the intended workflow sequenceartifacts[].requiresmatches dependenciesartifacts[].generatesmatches output paths that templates will create- Template files exist under
openspec/schemas/<schema-name>/templates/for each artifact
Validate the schema locally (required quality gate)
Run validation for every schema you changed:
bash openspec schema validate <schema-name>Note: some CLI versions mention
openspec schema review, but this repo's workflow standardizes onopenspec schema validate.Debug schema resolution (if validation or behavior is surprising)
Confirm which schema folder the CLI is using:
bash openspec schema which <schema-name>
Guardrails
- Prefer
openspec schema forkover manual copying. - Keep schemas as copyable, repository-local folders under
openspec/schemas/. - Always run
openspec schema validatebefore opening a PR.
© intent-driven-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .opencode/skills/openspec-schema-authoring of intent-driven-dev/openspec-schemas.
Open the folder on GitHubat commit 4bb6de2
Compare with similar skills
Openspec Schema Authoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Openspec Schema Authoring this skillintent-driven-dev/openspec-schemas | 105 | — | ~757 | Automated safety check: Pass | MIT | |
| Author Bylinethedaviddias/Front-End-Checklist | 74k | — | ~409 | Automated safety check: Pass | MIT | |
| Author Expertisethedaviddias/Front-End-Checklist | 74k | — | ~438 | Automated safety check: Pass | MIT | |
| Author Infothedaviddias/Front-End-Checklist | 74k | — | ~422 | Automated safety check: Pass | MIT | |
| Hermes Agent Skill AuthoringNousResearch/hermes-agent | 252k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Configuring Oauth2 Authorization Flowmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Author Expertise
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Highlight author credentials and expertise.
Author Info
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Implement comprehensive author markup.
Hermes Agent Skill Authoring
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
Configuring Oauth2 Authorization Flow
mukul975/Anthropic-Cybersecurity-Skills
Configures secure OAuth 2.0 authorization flows, including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token…
Customer Support Agent
mastra-ai/mastra
Authoring playbook for building agents that triage and reply to customer messages — support tickets, email inquiries, chat questions, refund requests, or product issues.
More from intent-driven-dev/openspec-schemas
Openspec Linearized
intent-driven-dev/openspec-schemas
A skill your agent uses whenever Codex operates on an OpenSpec change lifecycle or artifact, including propose/new change, apply/implement tasks, archive/finalize, sync specs, continue/update…
Openspec Schema Authoring
intent-driven-dev/openspec-schemas
Create or customize OpenSpec workflow schemas in this repository using openspec schema init and openspec schema fork.
Questions about Openspec Schema Authoring
What does Openspec Schema Authoring do?
Create or customize OpenSpec workflow schemas in this repository using openspec schema init and openspec schema fork. Openspec Schema Authoring is an agent skill from intent-driven-dev/openspec-schemas. Create or customize OpenSpec workflow schemas in this repository using openspec schema init and openspec schema fork.
How do I install Openspec Schema Authoring in Claude Code?
Run `npx skills add intent-driven-dev/openspec-schemas --skill openspec-schema-authoring -a claude-code`. Or copy the skill folder (.opencode/skills/openspec-schema-authoring in intent-driven-dev/openspec-schemas) into .claude/skills/openspec-schema-authoring in your project. Claude Code loads it when a task matches its description.
How do I install Openspec Schema Authoring in Codex?
Run `npx skills add intent-driven-dev/openspec-schemas --skill openspec-schema-authoring -a codex`. Or copy the skill folder (.opencode/skills/openspec-schema-authoring in intent-driven-dev/openspec-schemas) into .agents/skills/openspec-schema-authoring in your project. Codex loads it when a task matches its description.
Can I use Openspec Schema Authoring in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add intent-driven-dev/openspec-schemas --skill openspec-schema-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openspec-schema-authoring, .gemini/skills/openspec-schema-authoring, .github/skills/openspec-schema-authoring and .opencode/skills/openspec-schema-authoring in your project.
What does Openspec Schema Authoring need to run?
SKILL.md names no scripts, command-line tools or credentials: Openspec Schema Authoring is instructions for the agent only. Compatibility (from SKILL.md): Requires openspec CLI..
Does Openspec Schema Authoring access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Openspec Schema Authoring safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Openspec Schema Authoring use?
Openspec Schema Authoring is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Openspec Schema Authoring use?
About 757 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Openspec Schema Authoring?
Skills that share tags, products or a category with Openspec Schema Authoring: Author Byline (thedaviddias/Front-End-Checklist, 74k stars), Author Expertise (thedaviddias/Front-End-Checklist, 74k stars), Author Info (thedaviddias/Front-End-Checklist, 74k stars) and Hermes Agent Skill Authoring (NousResearch/hermes-agent, 252k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Openspec Schema Authoring?
intent-driven-dev (a GitHub organization) maintains it in intent-driven-dev/openspec-schemas, which has 105 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on August 16, 2026.
Source: intent-driven-dev/openspec-schemas on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.