Using Agent Skills
addyosmani/agent-skills
Meta-skill for choosing which workflow skill fits the task at hand, plus always-on habits: surface assumptions, stop on confusion, push back, keep it simple and stay in scope.
A skill your agent uses when creating or updating Doc View repository documentation, AGENTS.md, AI workflow guidance, OpenSpec configuration, or repo-local Codex skills.
Install Doc View Docs Maintenance
$ npx skills add liuzhihang/doc-view --skill doc-view-docs-maintenance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install liuzhihang/doc-view doc-view-docs-maintenance --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/liuzhihang/doc-view.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/doc-view-docs-maintenance .claude/skills/doc-view-docs-maintenance && 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 "doc-view-docs-maintenance" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-docs-maintenance into .claude/skills/doc-view-docs-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-docs-maintenance", 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/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-docs-maintenanceType 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 liuzhihang/doc-view --skill doc-view-docs-maintenance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install liuzhihang/doc-view doc-view-docs-maintenance --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/liuzhihang/doc-view.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/doc-view-docs-maintenance .agents/skills/doc-view-docs-maintenance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "doc-view-docs-maintenance" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-docs-maintenance into .agents/skills/doc-view-docs-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-docs-maintenance", 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 liuzhihang/doc-view --skill doc-view-docs-maintenance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install liuzhihang/doc-view doc-view-docs-maintenance --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/liuzhihang/doc-view.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/doc-view-docs-maintenance .cursor/skills/doc-view-docs-maintenance && 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 "doc-view-docs-maintenance" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-docs-maintenance into .cursor/skills/doc-view-docs-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-docs-maintenance", 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/liuzhihang/doc-view.git --path .codex/skills/doc-view-docs-maintenance--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 liuzhihang/doc-view --skill doc-view-docs-maintenance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install liuzhihang/doc-view doc-view-docs-maintenance --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/liuzhihang/doc-view.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/doc-view-docs-maintenance .gemini/skills/doc-view-docs-maintenance && 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 "doc-view-docs-maintenance" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-docs-maintenance into .gemini/skills/doc-view-docs-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-docs-maintenance", 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 liuzhihang/doc-view doc-view-docs-maintenanceInstalls 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 liuzhihang/doc-view --skill doc-view-docs-maintenance -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/liuzhihang/doc-view.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/doc-view-docs-maintenance .github/skills/doc-view-docs-maintenance && 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 "doc-view-docs-maintenance" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-docs-maintenance into .github/skills/doc-view-docs-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-docs-maintenance", 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 liuzhihang/doc-view --skill doc-view-docs-maintenance -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install liuzhihang/doc-view doc-view-docs-maintenance --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/liuzhihang/doc-view.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/doc-view-docs-maintenance .opencode/skills/doc-view-docs-maintenance && 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 "doc-view-docs-maintenance" agent skill from https://github.com/liuzhihang/doc-view/tree/master/.codex/skills/doc-view-docs-maintenance into .opencode/skills/doc-view-docs-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-view-docs-maintenance", 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
doc-view-docs-maintenance- GitHub stars
- 207
- Token cost
- ~456 tokens
- SKILL.md length
- 210 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when creating or updating Doc View repository documentation, AGENTS.md, AI workflow guidance, OpenSpec configuration, or repo-local Codex skills.
- Works in 6 steps: Confirm whether the change is mechanical… → Keep AGENTS.md as the concise entry… → Keep facts in their authoritative… → …
- Updating Doc View repository documentation
- SKILL.md covers Read First, Steps and Guardrails
- Calls git
What it does
Doc View Docs Maintenance is an agent skill from liuzhihang/doc-view. Use when creating or updating Doc View repository documentation, AGENTS.md, AI workflow guidance, OpenSpec configuration, or repo-local Codex skills.
Its SKILL.md is about 460 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 Agent instruction files. The repository describes itself as: IDEA 插件 Doc View 的仓库地址. The licence is MIT.
When your agent uses it
- Updating Doc View repository documentation
- AI workflow guidance
- OpenSpec configuration
- Repo-local Codex skills
Example prompts
- “/doc-view-docs-maintenance”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Confirm whether the change is mechanical documentation-only or describes a runtime/workflow behavior change.
- Keep AGENTS.md as the concise entry point; put detail in architecture, contract, performance, compatibility, AI workflow, roadmap, or…
- Keep facts in their authoritative source: versions/build facts in Gradle/plugin files, architecture in source plus architecture.md…
- Keep repo-local skills workflow-oriented and link canonical docs instead of copying project facts or full OpenSpec artifacts.
- Update indexes and inbound links when a canonical doc or skill moves.
- Verify OpenSpec status when applicable, file/link existence, stale workflow terms, secrets, git diff --check, and diff scope.
What it can do on your machine
Read from SKILL.md and the folder at commit 00f1f94. 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:
git
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
Doc View Docs Maintenance loads about 456 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 210 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 liuzhihang/doc-view at commit 00f1f94, republished under its MIT licence (© liuzhihang). 210 words, ~456 tokens.
Download SKILL.mdSave it as
.claude/skills/doc-view-docs-maintenance/SKILL.md (or your agent's skills folder).- name
- doc-view-docs-maintenance
- description
- Use when creating or updating Doc View repository documentation, AGENTS.md, AI workflow guidance, OpenSpec configuration, or repo-local Codex skills.
Doc View Docs Maintenance
Use this skill for repository guidance and AI workflow changes.
Read First
AGENTS.mddocs/ai-workflow.md- The target canonical doc and its inbound links
docs/release-checklist.mdwhen verification or release guidance changes- Active OpenSpec context when the documentation describes behavior, architecture, compatibility, or workflow requirements
Steps
- Confirm whether the change is mechanical documentation-only or describes a runtime/workflow behavior change.
- Keep
AGENTS.mdas the concise entry point; put detail in architecture, contract, performance, compatibility, AI workflow, roadmap, or release docs. - Keep facts in their authoritative source: versions/build facts in Gradle/plugin files, architecture in source plus
architecture.md, normative requirements in OpenSpec specs. - Keep repo-local skills workflow-oriented and link canonical docs instead of copying project facts or full OpenSpec artifacts.
- Update indexes and inbound links when a canonical doc or skill moves.
- Verify OpenSpec status when applicable, file/link existence, stale workflow terms, secrets,
git diff --check, and diff scope.
Guardrails
- Do not modify Java, Gradle,
plugin.xml, runtime resources, templates, icons, forms, or message bundles in documentation-only work. - Do not maintain
docs/contracts/**as a second normative spec system. - Do not claim runtime tests passed when only documentation checks ran.
- Keep examples free of credentials and private project code.
- Keep task checkboxes aligned with actual implementation and verification.
© liuzhihang, 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 .codex/skills/doc-view-docs-maintenance of liuzhihang/doc-view.
Open the folder on GitHubat commit 00f1f94
Compare with similar skills
Doc View Docs Maintenance 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 |
|---|---|---|---|---|---|---|
| Doc View Docs Maintenance this skillliuzhihang/doc-view | 207 | — | ~456 | Automated safety check: Pass | MIT | |
| Using Agent Skillsaddyosmani/agent-skills | 103k | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Claude ReflectBayramAnnakov/claude-reflect | 1.7k | 2 repos | ~627 | Automated safety check: Pass | MIT | |
| Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills | 21k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Writing For Agentsbestofjs/bestofjs | 3.1k | 18 repos | ~2.7k | Automated safety check: Pass | MIT | |
| Task Observerrebelytics/one-skill-to-rule-them-all | 3.2k | 1 repos | ~12k | Automated safety check: Pass | CC-BY-4.0 |
Similar skills
Claude Reflect
BayramAnnakov/claude-reflect
Self-learning system that captures corrections during sessions and reminds users to run /reflect to update CLAUDE.md.
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.
Writing For Agents
bestofjs/bestofjs
Writing documents for agents. An agent skill from bestofjs/bestofjs.
Task Observer
rebelytics/one-skill-to-rule-them-all
Monitors task execution for skill improvement opportunities.
- Official
SkillOpt Sleep Cycle
microsoft/SkillOpt
Runs an on-demand or nightly sleep cycle that reviews past Claude Code sessions and proposes validated updates to CLAUDE.md and skills.
More from liuzhihang/doc-view
Doc View Contract Design
liuzhihang/doc-view
A skill your agent uses when defining or reviewing Doc View behavior contracts before changing PSI parsing, DTOs, Markdown output, uploads, exports, settings, UI-visible behavior, or IntelliJ…
Doc View Java Maintenance
liuzhihang/doc-view
A skill your agent uses when implementing or reviewing Java-only Doc View production changes, especially PSI parsing, services, DTOs, UI, integrations, settings, export, or IntelliJ Platform behavior.
Doc View Release Readiness
liuzhihang/doc-view
A skill your agent uses when preparing, checking, or reviewing a Doc View plugin release, including changelog, version, plugin verification, manual IDE validation, Marketplace preparation, and…
Related
Categories
Questions about Doc View Docs Maintenance
What does Doc View Docs Maintenance do?
A skill your agent uses when creating or updating Doc View repository documentation, AGENTS.md, AI workflow guidance, OpenSpec configuration, or repo-local Codex skills. Doc View Docs Maintenance is an agent skill from liuzhihang/doc-view.md, AI workflow guidance, OpenSpec configuration, or repo-local Codex skills.
When should I use Doc View Docs Maintenance?
Doc View Docs Maintenance fits situations like: updating Doc View repository documentation; AI workflow guidance; openSpec configuration; repo-local Codex skills.
How do I install Doc View Docs Maintenance in Claude Code?
Run `npx skills add liuzhihang/doc-view --skill doc-view-docs-maintenance -a claude-code`. Or copy the skill folder (.codex/skills/doc-view-docs-maintenance in liuzhihang/doc-view) into .claude/skills/doc-view-docs-maintenance in your project. Claude Code loads it when a task matches its description.
How do I install Doc View Docs Maintenance in Codex?
Run `npx skills add liuzhihang/doc-view --skill doc-view-docs-maintenance -a codex`. Or copy the skill folder (.codex/skills/doc-view-docs-maintenance in liuzhihang/doc-view) into .agents/skills/doc-view-docs-maintenance in your project. Codex loads it when a task matches its description.
Can I use Doc View Docs Maintenance 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 liuzhihang/doc-view --skill doc-view-docs-maintenance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doc-view-docs-maintenance, .gemini/skills/doc-view-docs-maintenance, .github/skills/doc-view-docs-maintenance and .opencode/skills/doc-view-docs-maintenance in your project.
What does Doc View Docs Maintenance need to run?
Going by SKILL.md and its folder, Doc View Docs Maintenance needs the command-line tools its instructions call (git).
Does Doc View Docs Maintenance 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 Doc View Docs Maintenance 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 Doc View Docs Maintenance use?
Doc View Docs Maintenance 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 Doc View Docs Maintenance use?
About 456 tokens (SKILL.md is roughly 1.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 Doc View Docs Maintenance?
Skills that share tags, products or a category with Doc View Docs Maintenance: Using Agent Skills (addyosmani/agent-skills, 103k stars), Claude Reflect (BayramAnnakov/claude-reflect, 1.7k stars), Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars) and Writing For Agents (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Doc View Docs Maintenance?
liuzhihang (a GitHub user) maintains it in liuzhihang/doc-view, which has 207 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 16, 2026.
Source: liuzhihang/doc-view on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.