File contents Managed Content Markers
Safe regeneration pattern for auto-generated content in pm-workspace. Managed markers protect manual content while allowing automatic updates to generated sections.
Marker Format
<!-- managed-by: pm-workspace | section: {name} | updated: {ISO-date} -->
... auto-generated content ...
<!-- end-managed: {name} -->
Each managed section includes:
managed-by : Tool/system responsible for regeneration
section : Named identifier for the content block
updated : ISO 8601 timestamp of last regeneration
Three-Phase Workflow
Phase 1: Scan
Find all files with managed markers in the workspace. List:
File path
Section name
Last updated timestamp
Freshness status (e.g., "stale" if > 7 days old)
Phase 2: Regenerate
Re-generate content between markers while:
Preserving everything outside managed sections
Updating timestamp to current date
Validating marker integrity
Phase 3: Validate
Verify no content outside markers was modified. Abort if:
Markers are malformed
Content outside markers changed unexpectedly
Use Cases
File
Section
Purpose
CLAUDE.md
skills-catalog
Auto-generated list of all skills
CLAUDE.md
commands-summary
Count of commands by category
CLAUDE.md
agents-registry
Registry of all agents
pm-workflow.md
command-counts
Category counts with trends
plugin.json
capabilities
Computed capability counts
README.md
feature-list
Feature matrix auto-generated
Safety Guarantees
Content outside markers is NEVER modified
Markers include timestamp for tracking freshness
Regeneration is preview-first; requires --apply flag to persist
Failed validation prevents write operations
Integration Points
managed-sync: Regenerate all marked sections
managed-scan: Audit all markers and freshness
managed-content rule: Enforcement for new auto-generated content
1 --- 2 name: managed-content 3 description: Managed Content Markers 4 --- 5 6 # Managed Content Markers 7 8 Safe regeneration pattern for auto-generated content in pm-workspace. Managed markers protect manual content while allowing automatic updates to generated sections. 9 10 ## Marker Format 11 12 ```markdown 13 <!-- managed-by: pm-workspace | section: {name} | updated: {ISO-date} --> 14 ... auto-generated content ... 15 <!-- end-managed: {name} --> 16 ``` 17 18 Each managed section includes: 19 - **managed-by**: Tool/system responsible for regeneration 20 - **section**: Named identifier for the content block 21 - **updated**: ISO 8601 timestamp of last regeneration 22 23 ## Three-Phase Workflow 24 25 ### Phase 1: Scan 26 Find all files with managed markers in the workspace. List: 27 - File path 28 - Section name 29 - Last updated timestamp 30 - Freshness status (e.g., "stale" if > 7 days old) 31 32 ### Phase 2: Regenerate 33 Re-generate content between markers while: 34 - Preserving everything outside managed sections 35 - Updating timestamp to current date 36 - Validating marker integrity 37 38 ### Phase 3: Validate 39 Verify no content outside markers was modified. Abort if: 40 - Markers are malformed 41 - Content outside markers changed unexpectedly 42 43 ## Use Cases 44 45 | File | Section | Purpose | 46 |------|---------|---------| 47 | CLAUDE.md | skills-catalog | Auto-generated list of all skills | 48 | CLAUDE.md | commands-summary | Count of commands by category | 49 | CLAUDE.md | agents-registry | Registry of all agents | 50 | pm-workflow.md | command-counts | Category counts with trends | 51 | plugin.json | capabilities | Computed capability counts | 52 | README.md | feature-list | Feature matrix auto-generated | 53 54 ## Safety Guarantees 55 56 - Content outside markers is **NEVER** modified 57 - Markers include timestamp for tracking freshness 58 - Regeneration is preview-first; requires `--apply` flag to persist 59 - Failed validation prevents write operations 60 61 ## Integration Points 62 63 - `managed-sync`: Regenerate all marked sections 64 - `managed-scan`: Audit all markers and freshness 65 - `managed-content` rule: Enforcement for new auto-generated content
gonzalezpazmonica/pm-workspace commit ae4645449d
Frequently asked questions How do I install the Managed Content skill? Run npx get-skill add gonzalezpazmonica/managed-content 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.
What does the Managed Content skill do? Managed Content Markers It is listed under Coding & Dev Tools on SkillMD.
Is Managed Content safe to use? This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
Which AI agents work with Managed Content? 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 Managed Content free to use? Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
Who published Managed Content? gonzalezpazmonica (@gonzalezpazmonica) published this skill. Their other Agent Skills are listed on their SkillMD profile.