Agent skill

Public Docs Release

A skill your agent uses for WorldForge README, docs, changelog, generated provider docs, MkDocs navigation, version/release metadata, public positioning, and release or publish readiness checks.

MITAuto-check passedDevelopment

Install Public Docs Release

skills CLI

$ npx skills add AbdelStark/worldforge --skill public-docs-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install AbdelStark/worldforge public-docs-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/AbdelStark/worldforge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/public-docs-release .claude/skills/public-docs-release && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "public-docs-release" agent skill from https://github.com/AbdelStark/worldforge/tree/main/.codex/skills/public-docs-release into .claude/skills/public-docs-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "public-docs-release", 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

$skill-installer install https://github.com/AbdelStark/worldforge/tree/main/.codex/skills/public-docs-release

Type 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.

skills CLI

$ npx skills add AbdelStark/worldforge --skill public-docs-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install AbdelStark/worldforge public-docs-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AbdelStark/worldforge.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/public-docs-release .agents/skills/public-docs-release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "public-docs-release" agent skill from https://github.com/AbdelStark/worldforge/tree/main/.codex/skills/public-docs-release into .agents/skills/public-docs-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "public-docs-release", 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.

skills CLI

$ npx skills add AbdelStark/worldforge --skill public-docs-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install AbdelStark/worldforge public-docs-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AbdelStark/worldforge.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/public-docs-release .cursor/skills/public-docs-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "public-docs-release" agent skill from https://github.com/AbdelStark/worldforge/tree/main/.codex/skills/public-docs-release into .cursor/skills/public-docs-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "public-docs-release", 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

$ gemini skills install https://github.com/AbdelStark/worldforge.git --path .codex/skills/public-docs-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add AbdelStark/worldforge --skill public-docs-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install AbdelStark/worldforge public-docs-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AbdelStark/worldforge.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/public-docs-release .gemini/skills/public-docs-release && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "public-docs-release" agent skill from https://github.com/AbdelStark/worldforge/tree/main/.codex/skills/public-docs-release into .gemini/skills/public-docs-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "public-docs-release", 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.

GitHub CLI

$ gh skill install AbdelStark/worldforge public-docs-release

Installs 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).

skills CLI

$ npx skills add AbdelStark/worldforge --skill public-docs-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/AbdelStark/worldforge.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/public-docs-release .github/skills/public-docs-release && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "public-docs-release" agent skill from https://github.com/AbdelStark/worldforge/tree/main/.codex/skills/public-docs-release into .github/skills/public-docs-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "public-docs-release", 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.

skills CLI

$ npx skills add AbdelStark/worldforge --skill public-docs-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install AbdelStark/worldforge public-docs-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AbdelStark/worldforge.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/public-docs-release .opencode/skills/public-docs-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "public-docs-release" agent skill from https://github.com/AbdelStark/worldforge/tree/main/.codex/skills/public-docs-release into .opencode/skills/public-docs-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "public-docs-release", 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: public-docs-release
GitHub stars: 108
Token cost: ~679 tokens
SKILL.md length: 262 words
Files: 2
Skills in repo: 7
Repo updated: Sep 19, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses for WorldForge README, docs, changelog, generated provider docs, MkDocs navigation, version/release metadata, public positioning, and release or publish readiness checks.

Works in 3 steps: Command to run. → Expected success signal. → First triage step when it fails.
WorldForge README
SKILL.md covers Voice, Synchronization Rules, Generated Docs and Operational Docs Standard, plus 2 more sections
Calls uv

What it does

Public Docs Release is an agent skill from AbdelStark/worldforge. Use for WorldForge README, docs, changelog, generated provider docs, MkDocs navigation, version/release metadata, public positioning, and release or publish readiness checks. Keeps public surfaces synchronized without hype or generated-doc drift.

Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Changelog and release notes and Technical documentation. The repository describes itself as: Harness framework to build world model based workflows for physical AI systems. The licence is MIT.

When your agent uses it

WorldForge README
Generated provider docs
MkDocs navigation
Version/release metadata

Example prompts

“/public-docs-release”

Requirements

Python 3

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Command to run.
Expected success signal.
First triage step when it fails.

What it can do on your machine

Read from SKILL.md and the folder at commit 30b65da. 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
Shell commands in SKILL.md call:
- uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
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

Public Docs Release loads about 679 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 262 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~67
When it runs · the whole SKILL.md, loaded when a task matches: ~679

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 AbdelStark/worldforge at commit 30b65da, republished under its MIT licence (© AbdelStark). 262 words, ~679 tokens.

Download SKILL.mdSave it as .claude/skills/public-docs-release/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: public-docs-release
description: Use for WorldForge README, docs, changelog, generated provider docs, MkDocs navigation, version/release metadata, public positioning, and release or publish readiness checks. Keeps public surfaces synchronized without hype or generated-doc drift.

Public Docs And Release

Voice

Serious, precise, maintainer-style.
No hype, no tool branding, no inflated physical-fidelity claims.
Use "integration layer" for the project frame. Treat "typed" and "local JSON" as supporting details, not the headline.
README stays concise; route operational depth to docs/src/playbooks.md.
Public docs should help a maintainer reproduce evidence. Avoid narrative process notes and personal collaboration context.

Synchronization Rules

Change	Usually update
Provider capability/env var	provider docs, generated catalog, README table, `.env.example`, changelog, AGENTS/CLAUDE if agent-relevant
CLI command/help	README, `docs/src/cli.md`, `docs/src/examples.md`, help snapshots
Public Python API/error behavior	`docs/src/api/python.md`, changelog, tests, AGENTS/CLAUDE if contract-relevant
Runtime/smoke workflow	README, playbooks, operations, provider page, support docs
Docs page add/remove	`mkdocs.yml` and `docs/src/SUMMARY.md`
Release/version	`pyproject.toml`, `uv.lock`, README/version text, `CITATION.cff`, changelog, docs

Generated Docs

Do not hand-edit provider catalog blocks. Change provider profile/catalog metadata, then run:

bash

uv run python scripts/generate_provider_docs.py
uv run python scripts/generate_provider_docs.py --check

Operational Docs Standard

Every new runtime, provider, persistence, benchmark, or release workflow should include:

Command to run.
Expected success signal.
First triage step when it fails.

Definition Of Done

Source docs, generated docs, README tables, changelog, and navigation are synchronized for the changed public behavior.
Generated provider catalog blocks were regenerated from metadata instead of hand-edited.
Commands in docs are still executable or explicitly marked host-owned/credentialed/illustrative.
mkdocs build --strict and the relevant docs drift checks pass, or any skipped gate has a concrete blocker.

Sharp Edges

Symptom	Cause	Fix
MkDocs strict warning	Bad link/nav/SUMMARY drift	Fix source page and sync nav/SUMMARY
Provider table changes disappear	Edited generated block by hand	Change catalog/profile metadata and regenerate
CLI snapshot fails after copy edit	Help text changed	Update `tests/test_cli_help_snapshots.py` intentionally

Files

SKILL.md and 1 other file in .codex/skills/public-docs-release of AbdelStark/worldforge.

SKILL.md
agents/openai.yaml

Open the folder on GitHubat commit 30b65da

Compare with similar skills

Public Docs Release 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.

Public Docs Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Public Docs Release this skillAbdelStark/worldforge	108	—	~679	Automated safety check: Pass	MIT	19 days ago
Simple Englishmoeru-ai/airi	50k	2 repos	~4.6k	Automated safety check: Pass	MIT	today
Ccb GitHubSeemSeam/claude_codex_bridge	3.6k	—	~4.9k	Automated safety check: Pass	Custom licence	yesterday
Golang Documentationunxed/f4	241	3 repos	~3.5k	Automated safety check: Pass	MIT	today
Simple Englishropensci/ckanr	104	3 repos	~2k	Automated safety check: Pass	MIT	16 days ago
Opik Documentation Patternscomet-ml/opik	22k	—	~1.3k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
50k GitHub starsUsed in 2 repos~4.6k tokens
DevelopmentAuto-check passed
Ccb GitHub
SeemSeam/claude_codex_bridge
Maintain this CCB project's GitHub-facing release and npm publication surface.
3.6k GitHub stars~4.9k tokensUpdated yesterday
DevelopmentAuto-check passed
Golang Documentation
unxed/f4
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt.
241 GitHub starsUsed in 3 repos~3.5k tokens
DevelopmentAuto-check passed
Simple English
ropensci/ckanr
Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before…
104 GitHub starsUsed in 3 repos~2k tokens
DevelopmentAuto-check passed
Opik Documentation Patterns
comet-ml/opik
Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.
22k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
Release
jrswab/axe
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
895 GitHub stars~1.4k tokensUpdated 3 days ago
DevelopmentAuto-check passed

More from AbdelStark/worldforge

Testing Validation
AbdelStark/worldforge
A skill your agent uses when selecting, running, or fixing WorldForge validation: pytest, coverage, ruff, generated provider docs, MkDocs strict build, package contract, CI failures, and release…
108 GitHub stars~871 tokensUpdated 19 days ago
Auto-check passed
Evaluation Benchmarking
AbdelStark/worldforge
A skill your agent uses for WorldForge evaluation suites, benchmark harness changes, benchmark input fixtures, budget gates, report rendering, metrics semantics, and any claims based on benchmark or…
108 GitHub stars~732 tokensUpdated 19 days ago
Auto-check passed
Optional Runtime Smokes
AbdelStark/worldforge
A skill your agent uses for LeWorldModel, GR00T, LeRobot, PushT robotics showcase, real-checkpoint smoke scripts, checkpoint building, and host-owned optional runtime dependencies.
108 GitHub stars~855 tokensUpdated 19 days ago
Auto-check passed
Persistence State
AbdelStark/worldforge
A skill your agent uses for WorldForge local state: run workspaces and artifacts under .worldforge/ (run manifests, evidence bundles, retention/prune), the WorldForge(statedir=...) directory, and…
108 GitHub stars~921 tokensUpdated 19 days ago
Auto-check passed
Provider Adapter Development
AbdelStark/worldforge
A skill your agent uses for WorldForge provider work: adding adapters, changing capability declarations, promoting scaffolds, debugging provider failures, updating provider catalog docs, or touching…
108 GitHub stars~990 tokensUpdated 19 days ago
Auto-check: notes
Tui Development
AbdelStark/worldforge
A skill your agent uses for the robotics showcase Textual UI: report panes, launch helpers, screenshots, visual tests, and changes under src/worldforge/harness/tui.py or robotics view/rendering…
108 GitHub stars~792 tokensUpdated 19 days ago
Auto-check passed

Questions about Public Docs Release

What does Public Docs Release do?

A skill your agent uses for WorldForge README, docs, changelog, generated provider docs, MkDocs navigation, version/release metadata, public positioning, and release or publish readiness checks. Public Docs Release is an agent skill from AbdelStark/worldforge. Use for WorldForge README, docs, changelog, generated provider docs, MkDocs navigation, version/release metadata, public positioning, and release or publish readiness checks.

When should I use Public Docs Release?

Public Docs Release fits situations like: worldForge README; generated provider docs; mkDocs navigation; version/release metadata.

How do I install Public Docs Release in Claude Code?

Run `npx skills add AbdelStark/worldforge --skill public-docs-release -a claude-code`. Or copy the skill folder (.codex/skills/public-docs-release in AbdelStark/worldforge) into .claude/skills/public-docs-release in your project. Claude Code loads it when a task matches its description.

How do I install Public Docs Release in Codex?

Run `npx skills add AbdelStark/worldforge --skill public-docs-release -a codex`. Or copy the skill folder (.codex/skills/public-docs-release in AbdelStark/worldforge) into .agents/skills/public-docs-release in your project. Codex loads it when a task matches its description.

Can I use Public Docs Release 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 AbdelStark/worldforge --skill public-docs-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/public-docs-release, .gemini/skills/public-docs-release, .github/skills/public-docs-release and .opencode/skills/public-docs-release in your project.

What does Public Docs Release need to run?

Going by SKILL.md and its folder, Public Docs Release needs the command-line tools its instructions call (uv). Our summary lists: Python 3.

Does Public Docs Release access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Public Docs Release 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 Public Docs Release use?

Public Docs Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Public Docs Release use?

About 679 tokens (SKILL.md is roughly 2.7k 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 Public Docs Release?

Skills that share tags, products or a category with Public Docs Release: Simple English (moeru-ai/airi, 50k stars), Ccb GitHub (SeemSeam/claude_codex_bridge, 3.6k stars), Golang Documentation (unxed/f4, 241 stars) and Simple English (ropensci/ckanr, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Public Docs Release?

AbdelStark (a GitHub user) maintains it in AbdelStark/worldforge, which has 108 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 19, 2026.

Source: AbdelStark/worldforge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Public Docs Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Public Docs And Release

Voice

Synchronization Rules

Generated Docs

Operational Docs Standard

Definition Of Done

Sharp Edges

Files

Compare with similar skills

Similar skills

More from AbdelStark/worldforge

Related

Questions about Public Docs Release