Skip to content
Back to skills

Managed Content

ASecurity

Usar cuando se regeneran secciones auto-generadas en documentos con marcadores de seguridad.

  • 50 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
ai-agentsgo

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 28, 2026

npx -y skills add gonzalezpazmonica/savia --skill managed-content --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Managed Content?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Managed Content
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gonzalezpazmonica-managed-content/badge)](https://www.skillsdirectory.com/skills/gonzalezpazmonica-managed-content)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
layer: peripheral
name: managed-content
description: Usar cuando se regeneran secciones auto-generadas en documentos con marcadores de seguridad.
metadata:
  # --- metadata.savia.* (SE-333) ---
  savia.category: governance
  savia.maturity: beta
  savia.priority: medium
  savia.summary: "Gestiona secciones auto-generadas con marcadores safe-regeneration. Permite actualizar contenido automatico sin tocar contenido manual. Comandos: /managed-sync, /managed-scan."
  savia.tags: "managed-content, markers, auto-generated, sync"
---

# 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

```markdown
<!-- 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

Files in this skill

  • DOMAIN.md738 B
  • SKILL.md2.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…