How do I install the Agentos Editor skill?

Run npx skillmds@latest add br3eze-code/agentos-editor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agentos Editor safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agentos Editor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agentos Editor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agentos Editor?

br3eze-code (@br3eze-code) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agentos Editor by br3eze-code — Agent Skill

Name: Agentos Editor
Author: br3eze-code

Agentos Editor

Edit and control AgentOS documents, records, code-adjacent text, diagrams, and customer communications with source-of-truth checks, revision history, review comments, change tracking, publication approvals, and evidence. Use for editing, polishing, revising, or issuing controlled content.

br3eze-code d34c004 2 files · 3.5 KB Updated Sep 17, 2026

File contents

AgentOS Editor

Use this skill when a user asks to edit, revise, polish, restructure, compare, or issue controlled content. First identify the artifact type, source of truth, audience, tenant, project, revision, requested change, and publication state.

Workflow

identify source and revision
→ inspect requested change and scope
→ preserve meaning and protected requirements
→ edit or propose changes
→ run format, consistency, and integrity checks
→ record review comments and revision
→ request publication approval when required
→ issue approved artifact and evidence

For document-controlled work, use the nearest existing WBS package or create an Editor activity with a stable number such as ACT-EDITOR-DOC-001. Include source reference, original revision, target revision, editor, reviewers, change summary, acceptance criteria, evidence, and approval state.

Editing rules

Distinguish clearly between:

draft
review
revision proposed
approved
published
superseded

Never overwrite the source of truth without a backup or revision record. Preserve technical constraints, tenant boundaries, legal or financial values, identifiers, code semantics, and explicit user requirements. Do not invent missing facts. Mark unresolved points as questions or assumptions.

For code-adjacent edits, preserve module system, imports, error handling, authorization, idempotency, and tests. For controlled documents, preserve revision history, authorship, references, distribution scope, and approval status. For customer communication, remove private data and unverified claims.

Review and approval

Use read and draft capabilities for ordinary edits. Treat document.publish, drawing.issue, specification.approve, message.send, record.share, and production code changes as approval-gated mutations. Show a change summary or diff before approval. Recheck identity, scope, current revision, and approval immediately before issuing.

Outputs

Return:

artifact and revision
source of truth
requested changes
applied changes
unresolved questions
review findings
validation results
approval state
publication or handoff action

Attach evidence such as diff, test output, rendered preview, validation report, or reviewer decision. Keep the activity, artifact, revision, and audit trail tenant-scoped and visible consistently across CLI, web, desktop, mobile, Telegram, and WhatsApp.

---name: agentos-editordescription: Edit and control AgentOS documents, records, code-adjacent text, diagrams, and customer communications with source-of-truth checks, revision history, review comments, change tracking, publication approvals, and evidence. Use for editing, polishing, revising, or issuing controlled content.---# AgentOS EditorUse this skill when a user asks to edit, revise, polish, restructure, compare, or issue controlled content. First identify the artifact type, source of truth, audience, tenant, project, revision, requested change, and publication state.## Workflow```textidentify source and revision→ inspect requested change and scope→ preserve meaning and protected requirements→ edit or propose changes→ run format, consistency, and integrity checks→ record review comments and revision→ request publication approval when required→ issue approved artifact and evidence```For document-controlled work, use the nearest existing WBS package or create an Editor activity with a stable number such as `ACT-EDITOR-DOC-001`. Include source reference, original revision, target revision, editor, reviewers, change summary, acceptance criteria, evidence, and approval state.## Editing rulesDistinguish clearly between:```textdraftreviewrevision proposedapprovedpublishedsuperseded```Never overwrite the source of truth without a backup or revision record. Preserve technical constraints, tenant boundaries, legal or financial values, identifiers, code semantics, and explicit user requirements. Do not invent missing facts. Mark unresolved points as questions or assumptions.For code-adjacent edits, preserve module system, imports, error handling, authorization, idempotency, and tests. For controlled documents, preserve revision history, authorship, references, distribution scope, and approval status. For customer communication, remove private data and unverified claims.## Review and approvalUse read and draft capabilities for ordinary edits. Treat `document.publish`, `drawing.issue`, `specification.approve`, `message.send`, `record.share`, and production code changes as approval-gated mutations. Show a change summary or diff before approval. Recheck identity, scope, current revision, and approval immediately before issuing.## OutputsReturn:```textartifact and revisionsource of truthrequested changesapplied changesunresolved questionsreview findingsvalidation resultsapproval statepublication or handoff action```Attach evidence such as diff, test output, rendered preview, validation report, or reviewer decision. Keep the activity, artifact, revision, and audit trail tenant-scoped and visible consistently across CLI, web, desktop, mobile, Telegram, and WhatsApp.

Frequently asked questions