Humanizer
Azure-Samples/interview-coach-agent-framework
Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.
Switches into OpenSpec docs-writing mode; loads the house style guide and drafts or revises pages in its voice (action-first, no preamble, scannable).
Install Write Openspec Docs
$ npx skills add goern/forgejo-mcp --skill write-openspec-docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install goern/forgejo-mcp write-openspec-docs --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/goern/forgejo-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-openspec-docs .claude/skills/write-openspec-docs && 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 "write-openspec-docs" agent skill from https://github.com/goern/forgejo-mcp/tree/main/.agents/skills/write-openspec-docs into .claude/skills/write-openspec-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-openspec-docs", 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/goern/forgejo-mcp/tree/main/.agents/skills/write-openspec-docsType 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 goern/forgejo-mcp --skill write-openspec-docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install goern/forgejo-mcp write-openspec-docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/goern/forgejo-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/write-openspec-docs .agents/skills/write-openspec-docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-openspec-docs" agent skill from https://github.com/goern/forgejo-mcp/tree/main/.agents/skills/write-openspec-docs into .agents/skills/write-openspec-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-openspec-docs", 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 goern/forgejo-mcp --skill write-openspec-docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install goern/forgejo-mcp write-openspec-docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/goern/forgejo-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/write-openspec-docs .cursor/skills/write-openspec-docs && 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 "write-openspec-docs" agent skill from https://github.com/goern/forgejo-mcp/tree/main/.agents/skills/write-openspec-docs into .cursor/skills/write-openspec-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-openspec-docs", 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/goern/forgejo-mcp.git --path .agents/skills/write-openspec-docs--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 goern/forgejo-mcp --skill write-openspec-docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install goern/forgejo-mcp write-openspec-docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/goern/forgejo-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/write-openspec-docs .gemini/skills/write-openspec-docs && 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 "write-openspec-docs" agent skill from https://github.com/goern/forgejo-mcp/tree/main/.agents/skills/write-openspec-docs into .gemini/skills/write-openspec-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-openspec-docs", 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 goern/forgejo-mcp write-openspec-docsInstalls 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 goern/forgejo-mcp --skill write-openspec-docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/goern/forgejo-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/write-openspec-docs .github/skills/write-openspec-docs && 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 "write-openspec-docs" agent skill from https://github.com/goern/forgejo-mcp/tree/main/.agents/skills/write-openspec-docs into .github/skills/write-openspec-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-openspec-docs", 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 goern/forgejo-mcp --skill write-openspec-docs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install goern/forgejo-mcp write-openspec-docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/goern/forgejo-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/write-openspec-docs .opencode/skills/write-openspec-docs && 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 "write-openspec-docs" agent skill from https://github.com/goern/forgejo-mcp/tree/main/.agents/skills/write-openspec-docs into .opencode/skills/write-openspec-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-openspec-docs", 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
write-openspec-docs- GitHub stars
- 140
- Used in
- 1 other repo
- Token cost
- ~954 tokens
- SKILL.md length
- 541 words
- Files
- 3
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Switches into OpenSpec docs-writing mode; loads the house style guide and drafts or revises pages in its voice (action-first, no preamble, scannable).
- Editing pages in the OpenSpec docs tree
- SKILL.md covers Ground rules and When done
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Write Openspec Docs is an agent skill from goern/forgejo-mcp. Switches into OpenSpec docs-writing mode; loads the house style guide and drafts or revises pages in its voice (action-first, no preamble, scannable). Use when writing or editing pages in the OpenSpec docs tree.
Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `full-process.md` and `writing.md`).
It sits in Writing & Content. The repository describes itself as: MIRROR ONLY!! This Model Context Protocol (MCP) server provides tools and resources for interacting with the Forgejo (specifically Codeberg.org) REST API. The licence is GPL-3.0.
When your agent uses it
- Editing pages in the OpenSpec docs tree
Example prompts
- “Use the write-openspec-docs skill to switch into OpenSpec docs-writing mode; loads the house style guide and drafts or revises pages in its voice…”
- “/write-openspec-docs”
What it can do on your machine
Read from SKILL.md and the folder at commit 64a14bc. 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.
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.
Context cost
Write Openspec Docs loads about 954 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 541 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 goern/forgejo-mcp at commit 64a14bc, republished under its GPL-3.0 licence (© goern). 541 words, ~954 tokens.
Download SKILL.mdSave it as
.claude/skills/write-openspec-docs/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- write-openspec-docs
- description
- Switches into OpenSpec docs-writing mode; loads the house style guide and drafts or revises pages in its voice (action-first, no preamble, scannable). Use when writing or editing pages in the OpenSpec docs tree.
- argument-hint
- page or section
Write OpenSpec docs
You are now writing OpenSpec's user docs. Read writing.md; it is the style authority for everything drafted here. The short version, in effect immediately:
- A page is a retrieval surface, not an essay. Structure decides whether the reader finds the answer; prose only decides how it reads. Open every section with the answer, never a running story.
- Choose the page type before the outline. Guides follow the reader's task; reference mirrors the product's structure and uses exact field, command, and file names as scan anchors. Reference needs complete coverage without compressing several facts into one sentence, cell, or paragraph.
- Draft the shortest version that answers; expanding a spare page is cheap, cutting a bloated one is a rewrite. Plain words, the fewest of them: an idea that fits in one line takes one line. Depth most readers skip goes behind a link, and the payload (commands, real output, failures and fixes) stays whole.
- Dumb sentences, smart structure. Write the obvious sentence (actor, verb, object, stating the literal event); never compress extra facts in or take an angle. No hype adjectives, no preamble, no em dashes.
- One job per slot: one fact per sentence, list intros only announce the list, one reader question or lookup target per section. A related fact gets its own slot, never a ride in someone else's.
- Ground items in what the reader can verify: path or folder first, concept as the gloss, real output shown honestly.
- No house template. Inventories open with a list naming every item, then expand each in its own unit after the list, never inline. Sequences take numbered steps (numbers mean order; inventories take bullets). Single ideas and reasoning stay in short prose.
- Every load-bearing fact sits on a scan anchor: code fence, numbered bold lead-in,
**Term**: factbullet, table, file tree. Never only mid-paragraph. - Before finishing, run two backstop tests. Retrievability: can each question or exact product name be found by scanning alone? The glance: inspect the rendered page as shapes; does it look finishable, or like work? Check table-heavy changes at desktop and narrow widths. A failure means a slot got written without being earned; fix it now, don't leave it for review.
Show full SKILL.md (175 more words)Show less
Ground rules
- Load the
no-ai-slopskill before drafting; it owns the generic slop patterns, while writing.md owns what OpenSpec's docs specifically look and sound like. - Read the target page in full before editing it.
- Real facts only: flags, paths, and output as they exist in source. If a claim can't be checked cheaply, still write it, but name it as unchecked when you show the work; never bridge a gap with a plausible-sounding sentence.
- A fact lives on one page; everywhere else links to it. The docs tree's README owns the page map and structural invariants; check it before restructuring or adding pages.
- For reference pages, inventory the contract from source before drafting prose. Follow the reference process in writing.md.
- When unsure how something should scan or sound, match the exemplars:
docs-lab/start/setup.mdfor section shape and inventories,docs-lab/start/installation.md(Uninstalling) for multi-step tasks.
When done
Show the user what changed and name any unchecked claims.
If the user asks for the deep, evidence-first drafting session (run every command, one section per sitting, formal checkpoints), follow full-process.md.
© goern, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files in .agents/skills/write-openspec-docs of goern/forgejo-mcp.
- SKILL.md
- full-process.md
- writing.md
Open the folder on GitHubat commit 64a14bc
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in goern/forgejo-mcp, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Write Openspec Docs 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 |
|---|---|---|---|---|---|---|
| Write Openspec Docs this skillgoern/forgejo-mcp | 140 | 1 repos | ~954 | Automated safety check: Pass | GPL-3.0 | |
| HumanizerAzure-Samples/interview-coach-agent-framework | 172 | 37 repos | ~5.8k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| JavaScript Concept Fact Checkerleonardomso/33-js-concepts | 67k | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| User-Facing Text Cleanupguillaumemeyer/watermarks-remover | 23k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Install Anti Sloptrycompai/crm | 11k | 1 repos | ~881 | Automated safety check: Pass | MIT |
Similar skills
- Official
Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
JavaScript Concept Fact Checker
leonardomso/33-js-concepts
Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.
User-Facing Text Cleanup
guillaumemeyer/watermarks-remover
Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.
Install Anti Slop
trycompai/crm
Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.
Social Content
freekmurze/dotfiles
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms.
More from goern/forgejo-mcp
All 15 skills in this repoRelease Openspec
goern/forgejo-mcp
A skill your agent uses when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut…
Unified Notifications
goern/forgejo-mcp
Fetch and display notifications from both GitHub and Codeberg in a unified markdown view with clickable links.
Caveman Compress
goern/forgejo-mcp
Compress a memory file such as CLAUDE.md or a todo list into caveman format to save input tokens, keeping a readable backup.
Draft Openspec Docs
goern/forgejo-mcp
Collaborative page-drafting mode for the OpenSpec docs. An agent skill from goern/forgejo-mcp.
Verify Openspec Docs
goern/forgejo-mcp
Fact-checks OpenSpec user documentation with a fresh-context subagent that re-runs commands and checks claims against source.
Wt Switch Create
goern/forgejo-mcp
Create a new worktrunk worktree (optionally in another repo) and switch this session's working directory into it.
Related
Categories
Questions about Write Openspec Docs
What does Write Openspec Docs do?
Switches into OpenSpec docs-writing mode; loads the house style guide and drafts or revises pages in its voice (action-first, no preamble, scannable). Write Openspec Docs is an agent skill from goern/forgejo-mcp. Switches into OpenSpec docs-writing mode; loads the house style guide and drafts or revises pages in its voice (action-first, no preamble, scannable).
When should I use Write Openspec Docs?
Write Openspec Docs fits situations like: editing pages in the OpenSpec docs tree.
How do I install Write Openspec Docs in Claude Code?
Run `npx skills add goern/forgejo-mcp --skill write-openspec-docs -a claude-code`. Or copy the skill folder (.agents/skills/write-openspec-docs in goern/forgejo-mcp) into .claude/skills/write-openspec-docs in your project. Claude Code loads it when a task matches its description.
How do I install Write Openspec Docs in Codex?
Run `npx skills add goern/forgejo-mcp --skill write-openspec-docs -a codex`. Or copy the skill folder (.agents/skills/write-openspec-docs in goern/forgejo-mcp) into .agents/skills/write-openspec-docs in your project. Codex loads it when a task matches its description.
Can I use Write Openspec Docs 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 goern/forgejo-mcp --skill write-openspec-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-openspec-docs, .gemini/skills/write-openspec-docs, .github/skills/write-openspec-docs and .opencode/skills/write-openspec-docs in your project.
What does Write Openspec Docs need to run?
SKILL.md names no scripts, command-line tools or credentials: Write Openspec Docs is instructions for the agent only.
Does Write Openspec Docs 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 Write Openspec Docs 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 Write Openspec Docs use?
Write Openspec Docs is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Write Openspec Docs use?
About 954 tokens (SKILL.md is roughly 3.8k 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 Write Openspec Docs?
Skills that share tags, products or a category with Write Openspec Docs: Humanizer (Azure-Samples/interview-coach-agent-framework, 172 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars) and User-Facing Text Cleanup (guillaumemeyer/watermarks-remover, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write Openspec Docs?
goern (a GitHub user) maintains it in goern/forgejo-mcp, which has 140 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 6, 2026.
Source: goern/forgejo-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.