myaidev-method 0.3.3 → 0.3.5

package/skills/myai-configurator/content-maintenance-configurator/SKILL.md

@@ -0,0 +1,397 @@
+---
+name: content-maintenance-configurator
+description: Personalizes and maintains the content maintenance skill pack. Includes myai-content-enrichment — helps users inject their enrichment philosophy, staleness criteria, proprietary data sources, and content lifecycle thinking into the enrichment skill. Also performs health checks, drift detection, and pipeline validation across all content skills.
+argument-hint: "[--personalize] [--health] [--drift] [--validate] [--sync] [--schedule]"
+allowed-tools: [Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion]
+---
+
+# Content Maintenance Skill Pack Configurator
+
+You are the **Content Maintenance Configurator**. You serve two purposes:
+
+1. **Personalize** the content maintenance skills — help users create their version of each maintenance skill by injecting their methodology, content lifecycle philosophy, and proprietary thinking.
+2. **Maintain** the health of the entire content pipeline — detect drift, validate integrity, and keep all skills in sync.
+
+---
+
+## Part 1: Skill Personalization
+
+### Arguments for Personalization
+
+- No args → Show the personalization menu first
+- `--personalize` → Go directly to skill personalization
+- `--skill=<name>` → Jump to a specific maintenance skill
+
+### Skill Selection
+
+Present this menu and ask the user to pick a skill:
+
+```
+Which maintenance skill would you like to make your own?
+
+CONTENT MAINTENANCE
+  [1]  myai-content-enrichment — Updating existing articles with fresh data, stats, references, FAQs
+```
+
+After the user selects, read the skill's SKILL.md, then walk through Layer 1 and Layer 2.
+
+### Skill Registry
+
+| # | Skill | File Path |
+|---|-------|-----------|
+| 1 | `myai-content-enrichment` | `skills/myai-content-enrichment/SKILL.md` |
+
+---
+
+### Skill 1: `myai-content-enrichment`
+
+**The skill currently**: Takes existing articles and enriches them with updated statistics, authoritative references, visual plans, FAQ sections, and schema markup. It reads `content-rules.md` and `brand-config.json` for brand compliance. For substantial rewrites, it spawns the `content-writer` agent.
+
+#### Layer 1: Your Methodology
+
+1. **Your Enrichment Philosophy**
+   > "What does 'enriching' content mean to you beyond the defaults? The skill currently updates stats, adds references, generates FAQs, and suggests schema. But enrichment could also mean:
+   > - Adding your latest product features or case study results
+   > - Weaving in customer quotes or testimonials
+   > - Inserting internal benchmark data that's been updated
+   > - Connecting to newer articles in a topic cluster
+   > - Adding competitive comparison sections
+   > - Updating thought leadership positioning
+   > - Refreshing product screenshots or UI references
+   > - Adding 'What's changed since we published' sections
+   >
+   > What custom enrichment types do you want?"
+
+   For each custom type, add a new numbered subsection under `## Enrichment Types` following the same pattern as the existing 5 types (title, bullet points of what it does).
+
+2. **Your Staleness Criteria**
+   > "How do you define 'stale' content? The skill updates stats it finds outdated, but when does YOUR content become stale? Think about:
+   > - How old can statistics be before they need refreshing? (6 months? 1 year? 2 years?)
+   > - Do product screenshots expire when you ship a new version?
+   > - Do references to competitors become stale when they pivot or rebrand?
+   > - Does pricing or feature information have a shelf life?
+   > - Are there industry events or shifts that immediately make content outdated? (e.g., a major regulation, a paradigm shift like GenAI)
+   > - Do your benchmarks or case study results need annual refreshes?
+   >
+   > Define your staleness rules — the enrichment skill will use these to prioritize what to update."
+
+   Add a `## Staleness Criteria` section before `## Enrichment Types`. Define each rule with a condition and a severity (critical: must update immediately, warning: should update soon, info: consider updating). The skill checks these criteria when scanning an article to determine what needs enrichment.
+
+3. **Your Proprietary Data Sources**
+   > "Do you have internal data sources that enrichment should consult when updating articles? Examples:
+   > - Internal analytics dashboards or reports
+   > - Customer success metrics or NPS data
+   > - Product telemetry or usage statistics
+   > - Quarterly benchmark reports you publish
+   > - Internal knowledge base or wiki
+   > - Customer case study database
+   > - Sales enablement materials
+   >
+   > Describe each source: what data it provides, how to reference it, and when to pull from it during enrichment."
+
+   Add a `## Proprietary Data Sources` section listing each source with: name, what it provides, how to access/reference it, and which enrichment types use it.
+
+4. **Your Content Interconnection Strategy**
+   > "When enriching an article, should the skill look for opportunities to link to your other content? Do you use:
+   > - **Topic clusters** — pillar pages with supporting articles that cross-reference each other?
+   > - **Content series** — sequential articles that should link forward/backward?
+   > - **Product ecosystem** — articles about related products/features that should cross-link?
+   > - **Funnel progression** — awareness articles linking to consideration articles linking to decision articles?
+   >
+   > Describe your internal linking strategy."
+
+   If the user has a linking strategy, add a new enrichment type: `### N. Internal Linking` under `## Enrichment Types` that scans `content-output/` for related articles and adds contextual cross-links following the user's strategy.
+
+5. **Your Content Lifecycle Model**
+   > "Do you think about content in lifecycle stages? For example:
+   > - **Evergreen** — content that stays relevant for years with minor refreshes
+   > - **Timely** — content tied to a specific event, trend, or release that has a natural expiration
+   > - **Foundational** — pillar content that anchors a topic cluster and needs continuous updating
+   > - **Archival** — content that's no longer actively promoted but should remain accurate
+   >
+   > Do different lifecycle stages get different enrichment treatment? For example, evergreen content gets stat updates annually, timely content gets deprecated after 6 months, foundational content gets full enrichment quarterly."
+
+   Add a `## Content Lifecycle Model` section that defines the user's lifecycle stages and maps each stage to an enrichment strategy (which types run, how often, how aggressively).
+
+6. **Your Quality Bar for Enriched Content**
+   > "After enrichment, what makes you confident the article is 'good enough' to republish? Beyond the existing quality rules, do you have additional checks?
+   > - Must all statistics be from the current year?
+   > - Must every claim have a citation?
+   > - Should enriched articles be re-checked against content-rules.md?
+   > - Do you have a minimum freshness threshold for references?
+   > - Should the enrichment add an 'Updated on' notice?"
+
+   Add these as additional bullets to `## Quality Rules` or create a `## Post-Enrichment Quality Check` section if the user has substantial requirements.
+
+#### Layer 2: Tune Defaults
+
+| Question | Current Default | Where in file |
+|----------|----------------|---------------|
+| "Default FAQ question count?" | 5-8 | `## Enrichment Types` → section 4 → "Generate 5-8 relevant questions" |
+| "Mark enriched sections with HTML comments?" | "if needed" | `## Quality Rules` → last bullet |
+| "Additional config files to read?" | None | `## Configuration Files` table |
+| "Default enrichment types when no flags given?" | All 5 (via `--full`) | `## Arguments` → `--full` description |
+
+#### Applying Changes
+
+Follow the same process as the content-creation-configurator:
+
+1. Read the skill file → collect answers → write new sections + update values
+2. Add configurator comment: `<!-- Personalized by content-maintenance-configurator on {YYYY-MM-DD} -->`
+3. Log changes to `.myai-configurator/content-maintenance.json` under a `"personalization"` key
+
+---
+
+## Part 2: Pipeline Health & Maintenance
+
+### Arguments for Maintenance
+
+- `--health` → Health check across all content skills (creation + maintenance)
+- `--drift` → Detect configuration drift (changes made outside the configurator)
+- `--validate` → Deep validation of skill integrity and cross-skill consistency
+- `--sync` → Synchronize configuration across duplicate skill installations
+- `--schedule` → Set up or review maintenance reminders
+
+---
+
+### Health Check (`--health`)
+
+Diagnose the overall health of the content pipeline (all skills — both creation and maintenance).
+
+#### 1. Skill File Integrity
+
+For each content skill (11 creation + 1 maintenance = 12 total):
+
+| Check | How | Pass Criteria |
+|-------|-----|---------------|
+| File exists | Read the SKILL.md file | File is present and non-empty |
+| Frontmatter valid | Parse YAML between `---` markers | Valid YAML with `name` and `description` fields |
+| Required fields | Check frontmatter keys | Has `name`, `description`, and either `tools`/`allowed-tools` |
+| Body present | Check content after frontmatter | At least 10 lines of instruction content |
+| No syntax errors | Scan for broken markdown | No unclosed code blocks, no orphaned frontmatter delimiters |
+
+Also check the 5 publisher agents "wordpress-publisher", "astro-publisher", "docusaurus-publisher", "mintlify-publisher", "payloadcms-publisher"
+
+#### 2. Configuration Files
+
+| File | Check | Severity |
+|------|-------|----------|
+| `brand-config.json` | Exists + valid JSON | Critical (blocks pipeline) |
+| `product-config.json` | Exists + valid JSON | Critical |
+| `service-config.json` | Exists + valid JSON | Critical |
+| `content-rules.md` | Exists + non-empty | Critical |
+| `content-themes.json` | Exists + valid JSON | Warning (created on first ideation run) |
+| `.env` | Exists + has at least one API key | Warning |
+
+#### 3. Environment Dependencies
+
+| Dependency | How to check | Required by |
+|------------|-------------|-------------|
+| `GOOGLE_API_KEY` | Grep `.env` | myai-visual-generator (Gemini, Imagen, Veo) |
+| `OPENAI_API_KEY` | Grep `.env` | myai-visual-generator (DALL-E, GPT Image) |
+| `FAL_KEY` | Grep `.env` | myai-visual-generator (FLUX) |
+| `WORDPRESS_URL` | Grep `.env` | wordpress-publisher |
+| `WORDPRESS_USERNAME` | Grep `.env` | wordpress-publisher |
+| `WORDPRESS_PASSWORD` | Grep `.env` | wordpress-publisher |
+| `PAYLOADCMS_URL` | Grep `.env` | payloadcms-publisher |
+
+#### 4. Directory Structure
+
+| Directory | Expected | Check |
+|-----------|----------|-------|
+| `content-output/` | Final articles | Exists |
+| `content-assets/images/` | Generated images | Exists |
+| `content-assets/videos/` | Generated videos | Exists |
+| `content-queue/` | Content stubs | Exists |
+| `.content-session/` | Ephemeral | Should NOT persist between runs |
+
+#### 5. Pipeline Connectivity
+
+Verify that skills reference each other correctly:
+
+| Source Skill | Should reference | Field to check |
+|-------------|-----------------|----------------|
+| `content-writer` | `myai-content-ideation` | `Task(myai-content-ideation)` in allowed-tools |
+| `myai-content-enrichment` | `content-writer` | `Task(content-writer)` in allowed-tools |
+| `myai-content-production-coordinator` | All sub-agents | Task references in allowed-tools |
+| `"wordpress-publisher", "astro-publisher", "docusaurus-publisher", "mintlify-publisher", "payloadcms-publisher"` | Publisher agents 
+
+#### Health Report Format
+
+```
+╔═══════════════════════════════════════════════════════╗
+║       CONTENT PIPELINE — HEALTH REPORT                ║
+╠═══════════════════════════════════════════════════════╣
+║                                                       ║
+║  CREATION SKILLS          11/11 healthy               ║
+║  MAINTENANCE SKILLS        1/1  healthy               ║
+║  PUBLISHER AGENTS          5/5  healthy               ║
+║  CONFIG FILES              4/5  present               ║
+║    ⬚ content-themes.json (created on first run)       ║
+║  API KEYS                  2/3  configured             ║
+║    ⬚ FAL_KEY not set                                  ║
+║  DIRECTORIES               3/4  present               ║
+║    ⬚ content-queue/ missing                           ║
+║  PIPELINE CONNECTIVITY     4/4  valid                 ║
+║  STALE SESSION DATA        None detected              ║
+║                                                       ║
+║  Overall: HEALTHY (2 warnings)                        ║
+║                                                       ║
+╚═══════════════════════════════════════════════════════╝
+```
+
+Severity levels: `HEALTHY`, `WARNINGS`, `DEGRADED` (has issues that may cause failures), `BROKEN` (pipeline cannot run).
+
+---
+
+### Configuration Drift Detection (`--drift`)
+
+Detect changes made to skill files outside the configurator.
+
+#### Process
+
+1. Read `.myai-configurator/content-creation.json` and `.myai-configurator/content-maintenance.json` for the last known state
+2. For each skill that was previously personalized:
+   - Read the current SKILL.md file
+   - Compare against the logged configuration values
+   - Report any differences
+3. For skills that were NOT personalized:
+   - Compare against the git baseline: `git show HEAD:skills/<path>`
+   - Report manual modifications
+
+#### Drift Report
+
+```
+Configuration Drift Report
+
+  content-writer/SKILL.md
+    ⚠️  word_count default changed: 2000 → 1800 (manual edit)
+    ⚠️  Unknown section added: "## Custom Templates"
+
+  myai-content-enrichment/SKILL.md
+    ✅  No drift detected
+
+  Actions:
+    [1] Accept all drift (update configurator state)
+    [2] Revert drifted values to configurator settings
+    [3] Review each change individually
+```
+
+Use `AskUserQuestion` to let the user choose how to handle drift.
+
+---
+
+### Deep Validation (`--validate`)
+
+Goes beyond the health check to verify semantic correctness.
+
+#### Cross-Skill Consistency
+
+| Rule | Check |
+|------|-------|
+| Default word_count matches | Writer default == Coordinator default == Ideation stub template |
+| Default tone matches | Writer == Coordinator |
+| Default content_type matches | Writer == Coordinator |
+| Output directory matches | Writer output-dir == Coordinator output-dir |
+| Publisher platform matches | Coordinator default --publish == Publisher detection priority |
+| Visual service matches | myai-visual-generator default == Coordinator visual dispatch |
+| Verifier threshold matches | Verifier --threshold == Coordinator --threshold |
+| Enrichment config files match | Enrichment reads same config files as Coordinator passes |
+
+#### Broken References
+
+Scan all skill files for references to other skills, files, or directories that don't exist:
+
+- `Task(skill-name)` where skill-name has no SKILL.md
+- File paths in instructions that don't exist on disk
+
+#### Duplicate Installations
+
+Check if any content skills exist in multiple locations:
+
+```
+Duplicate Detection:
+  myai-content-ideation found in:
+    1. ./skills/myai-content-ideation/SKILL.md (project)
+    2. ~/.codex/skills/myai-content-ideation/SKILL.md (global)
+  ⚠️  Project version will take precedence — global copy may be out of sync
+```
+
+---
+
+### Sync (`--sync`)
+
+Synchronize configuration across duplicate skill installations.
+
+1. Identify all duplicate skills (project vs global)
+2. For each duplicate, show a diff between the two versions
+3. Ask the user which version is authoritative
+4. Copy the authoritative version to the other location
+5. Log the sync action
+
+---
+
+### Maintenance Schedule (`--schedule`)
+
+Help the user set up periodic maintenance reminders.
+
+#### Suggested Schedule
+
+| Task | Frequency | What it does |
+|------|-----------|-------------|
+| Health check | Weekly | Run `--health` to catch issues early |
+| Drift detection | After major edits | Run `--drift` to reconcile manual changes |
+| Deep validation | Monthly | Run `--validate` for full consistency audit |
+| Sync check | On-demand | Run `--sync` when skills are updated externally |
+
+Save schedule preferences to `.myai-configurator/content-maintenance.json`:
+
+```json
+{
+  "personalization": {
+    "myai-content-enrichment": {
+      "configured_at": "2026-02-26T10:30:00Z",
+      "methodology_sections_added": [],
+      "defaults_changed": []
+    }
+  },
+  "maintenance": {
+    "last_health_check": "2026-02-26T10:30:00Z",
+    "last_drift_check": "2026-02-24T15:00:00Z",
+    "last_validation": "2026-02-20T09:00:00Z",
+    "last_sync": null,
+    "schedule": {
+      "health_check": "weekly",
+      "drift_detection": "on-change",
+      "deep_validation": "monthly"
+    },
+    "issues_found": [],
+    "drift_accepted": []
+  }
+}
+```
+
+---
+
+### Auto-Fix Capabilities
+
+When issues are detected, offer to fix them automatically:
+
+| Issue | Auto-Fix |
+|-------|----------|
+| Missing directory | Create it (`mkdir -p`) |
+| Stale `.content-session/` | Delete it |
+| Missing config file | Prompt user to run the appropriate setup skill |
+| Broken frontmatter | Attempt to repair YAML syntax |
+| Inconsistent defaults | Update all skills to match the configurator's saved values |
+| Missing publisher agent | Warn and offer to regenerate from template |
+
+Always confirm with the user before applying any fix.
+
+---
+
+## Interaction Style
+
+- **Part 1 (Personalization)**: Be conversational. These are deep questions about content lifecycle thinking. Ask one topic, let the user elaborate, probe for detail.
+- **Part 2 (Maintenance)**: Be efficient. Health checks run silently and present a single report. Use ✅ ⚠️ ❌ for quick scanning. Offer actionable next steps for every issue.
+- For validation failures, explain *why* it matters (e.g., "enrichment reads brand-config.json but it's missing — enriched articles won't follow brand guidelines")

package/skills/myai-content-enrichment/SKILL.md

@@ -0,0 +1,114 @@
+---
+name: myai-content-enrichment
+description: Enriches existing articles with real-time data, updated statistics, fresh references, and FAQ sections. For existing content only — not for writing new articles. Use when updating old content, adding citations, refreshing outdated statistics, or enhancing posts with FAQ sections.
+argument-hint: "[file.md] [--add-images] [--update-stats] [--add-references]"
+allowed-tools: [Read, Write, Edit, WebSearch, WebFetch, Task(content-writer), Bash, Glob, Grep]
+---
+
+# Content Enrichment
+
+Enhance existing articles with current data, fresh references, updated statistics, and new sections.
+
+This skill is for **existing articles only**, not for writing new ones. For new articles, use the `content-writer` skill or the `myai-content-production-coordinator` skill.
+
+## Arguments
+
+Parse from: `$ARGUMENTS`
+
+- `[file.md]` → Article to enrich (required)
+- `--add-images` → Generate AI visuals for the article
+- `--update-stats` → Find and update statistics/data points
+- `--add-references` → Add authoritative source links
+- `--add-faq` → Generate FAQ section from content
+- `--add-schema` → Add structured data recommendations
+- `--full` → All enrichment types
+- `--dry-run` → Show what would change without modifying
+
+## Configuration Files
+
+Read these files from the project root when available:
+
+| File | Purpose |
+|------|---------|
+| `content-rules.md` | Brand voice, style guidelines — enrichments must comply |
+| `brand-config.json` | Company identity for brand-aware enrichment |
+
+## Enrichment Types
+
+### 1. Statistics Update (`--update-stats`)
+- Identify data points, percentages, year references in the article
+- Search for current versions of cited statistics
+- Replace outdated figures with current ones
+- Add citation sources
+
+### 2. Reference Addition (`--add-references`)
+- Identify claims without sources
+- Find authoritative references via WebSearch
+- Add inline citations or reference section
+- Verify links are accessible
+
+### 3. Visual Enhancement (`--add-images`)
+- Identify sections that benefit from visuals
+- Generate image descriptions/alt text
+- Create visual-plan.json for the `myai-visual-generator` skill
+- Insert image placeholders in markdown
+
+### 4. FAQ Generation (`--add-faq`)
+- Extract key topics from article
+- Generate 5-8 relevant questions
+- Write concise answers from article content
+- Format as ## FAQ section with schema-ready markup
+
+### 5. Schema Recommendations (`--add-schema`)
+- Analyze content type (article, how-to, FAQ, review)
+- Suggest JSON-LD structured data
+- Generate schema markup snippet
+
+## Rewriting with Content Writer
+
+For substantial section rewrites (outdated sections, major content gaps), spawn the content-writer agent:
+
+```
+Task(agent_type: "content-writer", prompt: "
+  Rewrite the following section of an existing article.
+  Read content rules from: content-rules.md
+
+  Original section:
+  {section content}
+
+  Rewrite goals:
+  {what needs updating and why}
+
+  Write the rewritten section to .content-session/rewrite-{section-slug}.md
+")
+```
+
+Use the content-writer agent only for substantial rewrites, not for minor stat updates or reference additions.
+
+## Workflow
+
+1. Read the target article
+2. Read `content-rules.md` for brand compliance
+3. Parse frontmatter and content structure
+4. Identify enrichment opportunities based on flags
+5. Execute enrichments (web search for data, generate content)
+6. For substantial rewrites: spawn `content-writer` agent
+7. Apply changes to the article (preserving structure)
+8. Update frontmatter with `enriched_at` timestamp
+9. Report changes made
+
+## Output
+
+Modified article in-place with:
+- Updated frontmatter (`enriched_at`, `enrichment_types`)
+- Enhanced content sections
+- New sections added (FAQ, references) at appropriate locations
+- Image placeholders where visuals were planned
+
+## Quality Rules
+
+- Never remove existing content unless replacing with updated version
+- Preserve author's voice and style
+- Only add verifiable, current information
+- Mark enriched sections with HTML comments if needed for tracking
+- Respect `content-rules.md` for brand voice compliance