Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
Update LunCoSim's canonical documentation and agent guidance when behavior, ownership, APIs, scenes, tutorials, validation rules, or workflows change.
Install Update Documents
$ npx skills add LunCoSim/lunco-sim --skill update-documents -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LunCoSim/lunco-sim update-documents --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/LunCoSim/lunco-sim.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/update-documents .claude/skills/update-documents && 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 "update-documents" agent skill from https://github.com/LunCoSim/lunco-sim/tree/main/skills/update-documents into .claude/skills/update-documents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-documents", 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/LunCoSim/lunco-sim/tree/main/skills/update-documentsType 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 LunCoSim/lunco-sim --skill update-documents -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LunCoSim/lunco-sim update-documents --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LunCoSim/lunco-sim.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/update-documents .agents/skills/update-documents && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "update-documents" agent skill from https://github.com/LunCoSim/lunco-sim/tree/main/skills/update-documents into .agents/skills/update-documents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-documents", 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 LunCoSim/lunco-sim --skill update-documents -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LunCoSim/lunco-sim update-documents --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LunCoSim/lunco-sim.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/update-documents .cursor/skills/update-documents && 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 "update-documents" agent skill from https://github.com/LunCoSim/lunco-sim/tree/main/skills/update-documents into .cursor/skills/update-documents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-documents", 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/LunCoSim/lunco-sim.git --path skills/update-documents--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 LunCoSim/lunco-sim --skill update-documents -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LunCoSim/lunco-sim update-documents --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LunCoSim/lunco-sim.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/update-documents .gemini/skills/update-documents && 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 "update-documents" agent skill from https://github.com/LunCoSim/lunco-sim/tree/main/skills/update-documents into .gemini/skills/update-documents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-documents", 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 LunCoSim/lunco-sim update-documentsInstalls 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 LunCoSim/lunco-sim --skill update-documents -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LunCoSim/lunco-sim.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/update-documents .github/skills/update-documents && 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 "update-documents" agent skill from https://github.com/LunCoSim/lunco-sim/tree/main/skills/update-documents into .github/skills/update-documents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-documents", 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 LunCoSim/lunco-sim --skill update-documents -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LunCoSim/lunco-sim update-documents --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LunCoSim/lunco-sim.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/update-documents .opencode/skills/update-documents && 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 "update-documents" agent skill from https://github.com/LunCoSim/lunco-sim/tree/main/skills/update-documents into .opencode/skills/update-documents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-documents", 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
update-documents- GitHub stars
- 105
- Token cost
- ~1.2k tokens
- SKILL.md length
- 587 words
- Files
- 1
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Update LunCoSim's canonical documentation and agent guidance when behavior, ownership, APIs, scenes, tutorials, validation rules, or workflows change.
- Works in 5 steps: identify the owner and read the relevant… → choose among the valid options and state… → make the smallest authoritative edit,… → …
- Asked to update docs
- SKILL.md covers Find the one canonical home, Decide what kind of edit is…, Write a useful skill and Verify the document change
- Calls rg and git
What it does
Update Documents is an agent skill from LunCoSim/lunco-sim. Update LunCoSim's canonical documentation and agent guidance when behavior, ownership, APIs, scenes, tutorials, validation rules, or workflows change. USE THIS SKILL when asked to update docs, AGENTS.md, a README, an architecture page, a skill, a tutorial authoring guide, or references after a code or asset change; when a document is stale; or when the user asks where a rule or option should be explained. For the agent mid-code: docs/architecture, docs/README.md, skills/README.md, AGENTS.md…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Technical documentation and Agent instruction files. The repository describes itself as: Collaborative Multiphysics Cosimulator For Space Missions 🌎🚀🌚. The licence is Apache-2.0.
When your agent uses it
- Asked to update docs
- An architecture page
- A tutorial authoring guide
- References after a code
Example prompts
- “/update-documents”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- identify the owner and read the relevant architecture/source files;
- choose among the valid options and state the reason;
- make the smallest authoritative edit, updating callers and docs together;
- verify with the project command that proves the behavior, not only parsing;
- report exact paths, results, limits, and any blocker.
What it can do on your machine
Read from SKILL.md and the folder at commit d1c6f00. 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:
rggit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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
Update Documents loads about 1.2k tokens when it runs. Until then it costs about 148 tokens; SKILL.md has 587 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 LunCoSim/lunco-sim at commit d1c6f00, republished under its Apache-2.0 licence (© LunCoSim). 587 words, ~1,217 tokens.
Download SKILL.mdSave it as
.claude/skills/update-documents/SKILL.md (or your agent's skills folder).- name
- update-documents
- description
- Update LunCoSim's canonical documentation and agent guidance when behavior, ownership, APIs, scenes, tutorials, validation rules, or workflows change. USE THIS SKILL when asked to update docs, AGENTS.md, a README, an architecture page, a skill, a tutorial authoring guide, or references after a code or asset change; when a document is stale; or when the user asks where a rule or option should be explained. For the agent mid-code: docs/architecture, docs/README.md, skills/README.md, AGENTS.md, assets/tutorials/README.md, or a request to keep docs and callers synchronized.
Update canonical LunCoSim documents
Use this skill for documentation changes that must remain aligned with the implemented owner. A document is a maintained interface: it must say what is true now, where the source of truth lives, and how to verify it.
Find the one canonical home
Read the owning source before editing prose. Then choose the narrowest home:
| Question | Canonical home |
|---|---|
| How the architecture works and why | docs/architecture/ |
| Which crate owns a responsibility | docs/crates-index.md |
| How to run an application | docs/apps/<app>/ and docs/apps/README.md |
| How to author tutorials or assets | assets/tutorials/README.md or an applicable skills/*/SKILL.md |
| How an agent should perform a task | skills/<name>/SKILL.md and skills/README.md |
| Repository-wide operating contract | AGENTS.md |
| A feature's required behavior | the relevant specs/<nnn>-*/spec.md |
Prefer updating an existing page over adding a second explanation. Add a new architecture page only when the topic has no owner; add a skill only when the task is a repeatable agent workflow rather than design rationale. Link between homes instead of copying long sections.
Decide what kind of edit is needed
- Correction: replace the stale claim everywhere it is public. Remove the retired contract, aliases, fallback instructions, and examples in the same change.
- New behavior: document the owner, consumer, lifecycle, and acceptance evidence. Update the affected skill and index when an agent must learn a new workflow.
- New option: explain the decision boundary, the exact authored fields or commands, and when each option is appropriate. State what must not be mixed.
- Removal: remove navigation, references, examples, and obsolete skill instructions; do not preserve a second “legacy” procedure unless the runtime still supports it as a deliberate contract.
For USD, distinguish authored-layer facts from composed runtime behavior. For an authored lesson, document its catalog entry, Rhai source, optional scene asset, lifecycle owner, and whether the scene uses a fixed-light world, an explicit ephemeris, an existing world, or no scene asset. Do not make Rust or a script own a scene fact that USD already authors.
Show full SKILL.md (266 more words)Show less
Write a useful skill
Use imperative instructions and keep SKILL.md under 500 lines. Its frontmatter
description is the trigger, so include user-facing phrases and mid-code signals
there. The body should be a runbook:
- identify the owner and read the relevant architecture/source files;
- choose among the valid options and state the reason;
- make the smallest authoritative edit, updating callers and docs together;
- verify with the project command that proves the behavior, not only parsing;
- report exact paths, results, limits, and any blocker.
Put detailed, conditional material in one-level references/ files only when the
body would otherwise become unwieldy. Do not create auxiliary README,
installation, changelog, or quick-reference files inside a skill.
When creating a new skill in this repository, create its directory under
skills/, give it a lowercase hyphenated name, add it to skills/README.md,
and add it to the relevant docs/README.md skill table if that table lists the
category. Generate agents/openai.yaml with the skill-creator helper when the
repository skill is intended for UI discovery.
Verify the document change
Search for stale names and duplicate contracts:
rg -n "old_name|old command|retired field" AGENTS.md docs skills assets
git diff --checkFor code or authored assets, run the owning focused test and the production
scene/API gate. Use $LUNCOSIM_BIN --validate for USD/Rhai preflight,
but do not call it runtime proof. For tutorial behavior, use an authored Rhai
observer under assets/scenarios/tests/ and run the production scene-test
binary; keep Rust tests generic to seams that Rhai cannot observe.
Before handoff, review the complete diff for stale links, duplicated explanations, unmarked design-vs-built claims, and instructions that preserve an obsolete fallback. Say explicitly when a full runtime or packaged verification was not run.
© LunCoSim, Apache-2.0. 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 skills/update-documents of LunCoSim/lunco-sim.
Open the folder on GitHubat commit d1c6f00
Compare with similar skills
Update Documents 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 |
|---|---|---|---|---|---|---|
| Update Documents this skillLunCoSim/lunco-sim | 105 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills | 21k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Dsh Web Documentationzhu1090093659/dsh-web | 8.5k | — | ~479 | Automated safety check: Pass | Apache-2.0 | |
| Newprojectscunning1975/MixtapeTools | 470 | 1 repos | ~850 | Automated safety check: Pass | None | |
| Sync Public DocsCaldis/react-zmage | 946 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Review DocsKaggle/kaggle-environments | 454 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Dsh Web Documentation
zhu1090093659/dsh-web
A skill your agent uses when adding or editing dsh-web README files, docs, AGENTS.md instructions, user-facing configuration text, or bilingual documentation pairs.
Newproject
scunning1975/MixtapeTools
Scaffold a new research project with standard directory structure, CLAUDE.md template, and documented README.
Sync Public Docs
Caldis/react-zmage
A skill your agent uses when modifying public API in packages/core (types/global.ts, types/default.ts, index.ts, or package.json exports field), adding/renaming/removing props, changing default…
Review Docs
Kaggle/kaggle-environments
Audit a game environment's README.md and AGENTS.md against its engine implementation.
Documentation
samchon/typia
Defines README, website-guide, and agent-instruction structure, audience, prose formatting, and voice for typia.
More from LunCoSim/lunco-sim
All 38 skills in this repoNightly Changelog
LunCoSim/lunco-sim
Generate concise LunCoSim nightly GitHub release notes with platform downloads, installation guidance, an AI-agent mission prompt, and a changelog link.
Interactive Component Authoring
LunCoSim/lunco-sim
Build or repair a reusable scene component through a live LunCoSim Editor session.
Assembly Quality
LunCoSim/lunco-sim
Build or review a componentized LunCoSim USD assembly with a realistic, dimensionally checkable presentation.
Author Rhai Tests
LunCoSim/lunco-sim
Author and review LunCoSim behavioral, asset-backed, component, mission, visual, and requirements-verification tests.
Author Rhai Tool
LunCoSim/lunco-sim
Create, extend, register, or debug a reusable LunCoSim Rhai tool library for live USD authoring, component linting, inspection, or test support.
Author Tutorial
LunCoSim/lunco-sim
Author an interactive tutorial, guided lesson, onboarding flow, coach-mark tour, or objectives checklist in LunCoSim.
Related
Categories
Questions about Update Documents
What does Update Documents do?
Update LunCoSim's canonical documentation and agent guidance when behavior, ownership, APIs, scenes, tutorials, validation rules, or workflows change. Update Documents is an agent skill from LunCoSim/lunco-sim. Update LunCoSim's canonical documentation and agent guidance when behavior, ownership, APIs, scenes, tutorials, validation rules, or workflows change.
When should I use Update Documents?
Update Documents fits situations like: asked to update docs; an architecture page; A tutorial authoring guide; references after a code.
How do I install Update Documents in Claude Code?
Run `npx skills add LunCoSim/lunco-sim --skill update-documents -a claude-code`. Or copy the skill folder (skills/update-documents in LunCoSim/lunco-sim) into .claude/skills/update-documents in your project. Claude Code loads it when a task matches its description.
How do I install Update Documents in Codex?
Run `npx skills add LunCoSim/lunco-sim --skill update-documents -a codex`. Or copy the skill folder (skills/update-documents in LunCoSim/lunco-sim) into .agents/skills/update-documents in your project. Codex loads it when a task matches its description.
Can I use Update Documents 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 LunCoSim/lunco-sim --skill update-documents -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-documents, .gemini/skills/update-documents, .github/skills/update-documents and .opencode/skills/update-documents in your project.
What does Update Documents need to run?
Going by SKILL.md and its folder, Update Documents needs the command-line tools its instructions call (rg and git).
Does Update Documents access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Update Documents 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 Update Documents use?
Update Documents is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Update Documents use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Update Documents?
Skills that share tags, products or a category with Update Documents: Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), Dsh Web Documentation (zhu1090093659/dsh-web, 8.5k stars), Newproject (scunning1975/MixtapeTools, 470 stars) and Sync Public Docs (Caldis/react-zmage, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Update Documents?
LunCoSim (a GitHub organization) maintains it in LunCoSim/lunco-sim, which has 105 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 7, 2026.
Source: LunCoSim/lunco-sim on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.