maintaining-documentation
v0.2.0Keep a project's docs true to the code and useful to their readers, without rewriting historical records.
By Prime Radiant, Inc.License: MIT9 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Codex, Claude Code, and Agent Plugins
- Parsed components
- 2 skill or MCP entries
- Source updated
- Oct 12, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install maintaining-documentation for Codex and Claude Code
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add maintaining-documentation@agent-plugin-marketplacePaste and run these commands in a terminal with Codex. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/prime-radiant-inc/maintaining-documentationClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json├── plugin.json├── skills/copyediting-docs/SKILL.md└── skills/maintaining-documentation/SKILL.md
Included Skills2
Use when copyediting or tightening the prose of documentation (README, guide, tutorial, troubleshooting, reference, architecture doc) whose content is already settled, or when a doc reads as wordy, passive, or vague.
Use when documentation needs writing, checking, or maintaining — writing a README, tutorial, how-to, troubleshooting guide, reference, architecture doc, or onboarding doc; docs that read like a code tour; docs that may have drifted from code; pre-release doc verification; updating docs after finishing code work; adding or enforcing project terminology; deciding where a new doc should live; or a routine re-audit of previously verified docs.
Plugin manifests3
{
"name": "maintaining-documentation",
"version": "0.2.0",
"description": "Keep a project's docs true to the code and useful to their readers, without rewriting historical records.",
"author": {
"name": "Prime Radiant, Inc."
},
"repository": "https://github.com/prime-radiant-inc/maintaining-documentation",
"license": "MIT",
"skills": "./skills/",
"hooks": {}
}{
"name": "maintaining-documentation",
"version": "0.2.0",
"description": "Keep a project's docs true to the code and useful to their readers, without rewriting historical records.",
"author": {
"name": "Prime Radiant, Inc."
},
"license": "MIT",
"repository": "https://github.com/prime-radiant-inc/maintaining-documentation"
}{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "maintaining-documentation",
"version": "0.2.0",
"description": "Keep a project's docs true to the code and useful to their readers, without rewriting historical records.",
"author": {
"name": "Prime Radiant, Inc."
},
"repository": "https://github.com/prime-radiant-inc/maintaining-documentation",
"license": "MIT"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[maintaining-documentation on Agent Plugins Marketplace](https://pluginsmp.com/plugins/maintaining-documentation)