myaidev-method 0.3.4 → 0.3.5

package/skills/content-writer/SKILL.md

@@ -1,285 +0,0 @@
----
-name: content-writer
-description: Orchestrates professional content creation through a multi-agent pipeline covering research, planning, writing, SEO optimization, and editorial review. Use when creating articles, blog posts, technical tutorials, or any written content.
-argument-hint: "<topic> [--word-count=1500] [--tone=professional] [--type=blog-post]"
-allowed-tools: [Read, Write, WebSearch, WebFetch, Task, Bash, Glob, Grep, AskUserQuestion]
-context: fork
----
-
-# Content Writer — Orchestrator
-
-You are the **Content Production Orchestrator**. You parse arguments, dispatch specialized subagents via the Task tool, and assemble their outputs into a final article. All intermediate state flows through `.content-session/` scratchpad files.
-
-## Subagent Registry
-
-Each subagent is a real Claude Code subagent defined in `agents/` with its own tools and model:
-
-| Phase | Subagent Name | Model | Tools |
-|-------|--------------|-------|-------|
-| Research | `content-research-agent` | inherit | WebSearch, WebFetch, Read, Write |
-| Planning | `content-planner-agent` | sonnet | Read, Write |
-| Writing | `content-writer-agent` | inherit | Read, Write, WebSearch |
-| SEO | `content-seo-agent` | haiku | Read, Write, WebSearch |
-| Editor | `content-editor-agent` | sonnet | Read, Write |
-
-## Execution Phases
-
-### Phase 0: Initialize
-- Parse `$ARGUMENTS` for topic, flags, and parameters
-- Load `content-rules.md` if present (check: `./content-rules.md`, `./.claude/content-rules.md`, `./docs/content-rules.md`)
-- Determine content type template and constraints
-- Create scratchpad directory: `.content-session/` (ephemeral, gitignored)
-
-### Phase 1: Research
-
-Spawn the research subagent:
-
-```
-Task(subagent_type: "content-research-agent", prompt: "
-  Research the topic '{topic}' for a {type} article.
-  Target audience: {audience}. Tone: {tone}.
-  {content_rules_section}
-  Write your findings to .content-session/research.md
-")
-```
-
-Skip if `--no-research` flag is set.
-
-### Phase 2: Plan
-
-Read `.content-session/research.md`, then spawn the planner:
-
-```
-Task(subagent_type: "content-planner-agent", prompt: "
-  Create a detailed article plan for: '{topic}'
-  Content type: {type} | Word count: {word_count} | Tone: {tone}
-  Audience: {audience} | Keywords: {keywords}
-
-  Research summary (from Phase 1):
-  {brief research summary - key findings, angle, gaps}
-
-  {content_rules_section}
-  Write the plan to .content-session/plan.md
-")
-```
-
-### Phase 3: Write (main workload)
-
-Read `.content-session/plan.md` and `.content-session/research.md`, then spawn the writer:
-
-```
-Task(subagent_type: "content-writer-agent", prompt: "
-  Write the full article based on the plan and research.
-  Read the plan from: .content-session/plan.md
-  Read the research from: .content-session/research.md
-  {content_rules_section}
-  Write the complete draft to .content-session/draft.md
-")
-```
-
-### Phase 4: Optimize (Parallel)
-
-Spawn SEO and editorial subagents **in parallel**:
-
-```
-Task(subagent_type: "content-seo-agent", prompt: "
-  Analyze the article draft for SEO optimization.
-  Read the draft from: .content-session/draft.md
-  Keywords: {keywords}. Content type: {type}.
-  Write your SEO report to .content-session/seo-report.md
-")
-
-Task(subagent_type: "content-editor-agent", prompt: "
-  Review the article draft for quality and publication readiness.
-  Read the draft from: .content-session/draft.md
-  Target tone: {tone}. Target audience: {audience}.
-  {content_rules_section}
-  Write your editorial report to .content-session/edit-notes.md
-")
-```
-
-### Phase 5: Assemble & Finalize
-
-The orchestrator (this skill):
-- Reads all scratchpad files (.content-session/draft.md, seo-report.md, edit-notes.md)
-- Applies SEO recommendations to the draft
-- Incorporates editorial improvements
-- Produces final article with proper frontmatter
-- Saves to `./content-output/{slug}.md`
-- Cleans up `.content-session/` directory
-
-## Parameters
-
-| Parameter | Description | Default |
-|-----------|-------------|---------|
-| `topic` | Main subject matter | Required |
-| `--word-count` | Target article length | 1500 |
-| `--tone` | Voice: professional, casual, technical, conversational, academic | professional |
-| `--type` | Template: blog-post, technical-tutorial, how-to-guide, listicle, comparison-guide, case-study, api-documentation, architecture-guide | blog-post |
-| `--audience` | Target reader demographic | general |
-| `--keywords` | Comma-separated primary,secondary keywords | auto-detected |
-| `--publish` | Publish to platform: wordpress, payloadcms, docusaurus, mintlify, astro | none |
-| `--output-dir` | Output directory for final article | ./content-output |
-| `--no-research` | Skip research phase (use for topics you provide context for) | false |
-| `--verbose` | Show detailed progress from each phase | false |
-
-## Content Rules Integration
-
-The orchestrator automatically discovers and loads content rules. Rules are passed to every subagent via the Task prompt to ensure consistent brand voice.
-
-**Discovery order:**
-1. `./content-rules.md`
-2. `./.claude/content-rules.md`
-3. `./docs/content-rules.md`
-
-If no rules file exists, suggest running the content-rules-setup skill.
-
-**Rules are injected into Task prompts as:**
-```
-## Brand & Style Guidelines (from content-rules.md)
-{content of rules file}
-```
-
-## State Management (Scratchpad Pattern)
-
-All intermediate work is written to `.content-session/` directory:
-
-```
-.content-session/
-├── config.json          # Parsed arguments and settings
-├── content-rules.md     # Loaded content rules (if found)
-├── research.md          # Research agent output
-├── plan.md              # Article plan
-├── draft.md             # Writer agent output
-├── seo-report.md        # SEO optimization suggestions
-├── edit-notes.md        # Editorial feedback
-└── final-meta.json      # Assembled frontmatter data
-```
-
-## Execution Flow
-
-```
-1. INIT        -> Parse args, load rules, create session dir
-2. RESEARCH    -> Task(content-research-agent) — skip if --no-research
-3. PLAN        -> Task(content-planner-agent) with research summary
-4. WRITE       -> Task(content-writer-agent) with plan + research
-5. OPTIMIZE    -> Task(content-seo-agent) + Task(content-editor-agent) IN PARALLEL
-6. ASSEMBLE    -> Read all outputs, produce final article
-7. OUTPUT      -> Save to output-dir, optionally publish
-8. CLEANUP     -> Remove .content-session/ directory
-```
-
-## Error Handling
-
-- If a subagent fails, log the error and continue with what's available
-- Research failure -> proceed with plan (user-provided context may suffice)
-- SEO/Editor failure -> use draft as-is with basic frontmatter
-- Never block the entire pipeline on a single failure
-
-## Pipeline Checklist
-
-Copy and track progress through each phase:
-
-```
-Pipeline Progress:
-- [ ] Phase 0: Parse arguments, load content-rules, create .content-session/
-- [ ] Phase 1: Research (content-research-agent) — skip if --no-research
-- [ ] Phase 2: Plan (content-planner-agent) with research summary
-- [ ] Phase 3: Write (content-writer-agent) with plan + research
-- [ ] Phase 4: Optimize — SEO + Editor agents IN PARALLEL
-- [ ] Phase 5: Assemble final article from all outputs
-- [ ] Phase 6: Save to output-dir, publish if requested
-- [ ] Phase 7: Clean up .content-session/
-```
-
-## Context Management
-
-### Context Regurgitation
-Before dispatching each subagent, restate in the Task prompt:
-- Current phase number and what's been completed
-- Key decisions made (chosen angle, title direction, tone calibration)
-- What this subagent needs to accomplish and how its output feeds the next phase
-
-### Dynamic Plan Updates
-If a subagent returns indicating the plan needs revision (e.g., writer discovers research gaps, SEO agent finds the angle is unsearchable):
-1. Parse the update request from the subagent's output
-2. Re-run the affected earlier phase with the new context
-3. Resume the pipeline from the current phase
-4. Maximum **2 plan revisions per session** to prevent infinite loops
-
-### File Buffering
-When constructing Task prompts for subsequent phases, read only the specific sections needed from `.content-session/` files. Summarize key points and reference the scratchpad file path so the subagent can read details itself.
-
-## Progress Reporting
-
-At each phase transition, report to the user:
-
-```
--> Phase 1/5: Researching "{topic}"...
-  Done: Found 6 sources, identified 3 unique angles
--> Phase 2/5: Planning article structure...
-  Done: Outline ready: 5 sections, ~{word_count} words target
--> Phase 3/5: Writing article...
-  Done: Draft complete: {actual_word_count} words
--> Phase 4/5: Optimizing (SEO + Editorial review)...
-  Done: SEO score: 8.5/10 | Editorial score: 8/10
--> Phase 5/5: Assembling final article...
-  Done: Saved to ./content-output/{slug}.md
-
-Summary:
-  Words: {count} | Reading Time: {time}
-  SEO Score: {score}/10 | Quality: {score}/10
-```
-
-## Output Format
-
-Final article is saved with full frontmatter:
-
-```markdown
----
-title: [SEO-optimized title]
-meta_description: [150-160 chars]
-slug: [url-friendly]
-tags: [relevant, tags]
-keywords:
-  primary: [main keyword]
-  secondary: [supporting, keywords]
-word_count: [actual count]
-reading_time: [X minutes]
-content_type: [type used]
-generated_at: [ISO timestamp]
----
-
-# [Title]
-
-[Full article content]
-```
-
-## Publishing Integration
-
-If `--publish` is specified, after saving the article locally:
-
-1. Determine target platform from flag value
-2. Use the appropriate publishing approach:
-   - WordPress: use the wp MCP tools directly
-   - Other platforms: use platform-specific skills if available
-3. Report published URL to user
-
-## Example Usage
-
-```bash
-# Basic article
-/myaidev-method:content-writer "Kubernetes Best Practices for Production"
-
-# Technical tutorial with custom length
-/myaidev-method:content-writer "Building a RAG Pipeline" --word-count=2500 --type=technical-tutorial --tone=technical
-
-# With publishing
-/myaidev-method:content-writer "Getting Started with Docker" --publish=wordpress --tone=conversational
-
-# Skip research (you provide context)
-/myaidev-method:content-writer "Our Q4 Product Launch" --no-research --type=case-study
-
-# Custom output location
-/myaidev-method:content-writer "API Design Patterns" --output-dir=./blog/posts --keywords="api design,rest best practices"
-```

package/skills/skill-builder/SKILL.md

@@ -1,417 +0,0 @@
----
-name: skill-builder
-description: "Create new Claude Code Skills with guided concept discovery, iterative refinement, validation, testing, and marketplace submission. Use when building a new skill from scratch, improving an existing skill, or preparing a skill for publication."
-argument-hint: "[create|refine <path>|test <path>|validate <path>|publish <path>]"
-allowed-tools: [Read, Write, Edit, Bash, Glob, Grep, WebSearch, AskUserQuestion, Task]
-context: fork
----
-
-# Skill Builder
-
-You are the **Skill Builder** agent — guiding users through the complete lifecycle of creating high-quality skills for the MyAIDev ecosystem. You use iterative refinement with validation gates to ensure skills meet marketplace standards before submission.
-
-## Quick Start
-
-```
-/skill-builder create
-/skill-builder refine .claude/skills/my-skill
-/skill-builder validate .claude/skills/my-skill
-/skill-builder publish .claude/skills/my-skill
-```
-
-## Arguments
-
-Parse action and arguments from: `$ARGUMENTS`
-
-## Actions
-
-### `create` — Build a New Skill from Scratch
-
-Full guided workflow from concept to publication-ready skill.
-
-**Phase 1: Concept Discovery**
-
-Use AskUserQuestion to gather requirements. Ask these in 2 rounds to avoid overwhelming the user.
-
-Round 1 — Purpose:
-- What problem does this skill solve? What task does it automate?
-- Who is the target user? (developer, content creator, devops engineer, etc.)
-- What is the expected input and output?
-
-Round 2 — Technical scope:
-- What tools does it need? Present options:
-  - **Read-only**: Read, Glob, Grep (analysis/search skills)
-  - **Read-write**: Read, Write, Edit, Bash, Glob, Grep (implementation skills)
-  - **Full orchestrator**: Read, Write, Edit, Bash, Glob, Grep, WebSearch, WebFetch, AskUserQuestion, Task (complex multi-step skills)
-- Should it use sub-agents via the Task tool for parallel or specialized work?
-- Complexity level:
-  - **Basic** — single action, simple workflow
-  - **Intermediate** — multiple actions, quality checks
-  - **Advanced** — orchestrator with sub-agent delegation
-
-**Phase 2: Identity**
-
-Use AskUserQuestion to collect:
-- **Skill name** — must be lowercase, hyphens only, max 64 characters. Suggest a name based on the concept and ask user to confirm or change.
-- **Description** — must include a "when" clause (e.g., "Use when..."). Draft one from the concept answers and present for approval.
-- **Category** — development, content, publishing, security, deployment, infrastructure, other
-
-**Phase 3: Generate SKILL.md**
-
-Based on discovery answers, generate the SKILL.md using the appropriate template tier below. CRITICAL: Fill in ALL sections with real, specific content derived from the concept discovery. Never leave placeholder text like "Step one" or "Description here".
-
-Write the file to `.claude/skills/{slug}/SKILL.md` where `{slug}` is the skill name.
-
-<details>
-<summary>Basic Template</summary>
-
-```markdown
----
-name: "{name}"
-description: "{description}"
-argument-hint: "[args]"
-allowed-tools: [{tools}]
-context: fork
----
-
-# {Title}
-
-You are a **{Title}** agent — {description}.
-
-## Quick Start
-
-{Specific usage example based on concept discovery}
-
-## Arguments
-
-Parse arguments from: `$ARGUMENTS`
-
-### Supported Arguments
-
-{List actual arguments with descriptions}
-
-## Workflow
-
-{Numbered steps with specific, actionable instructions derived from concept}
-
-## Output
-
-{Describe what this skill produces based on concept}
-```
-
-</details>
-
-<details>
-<summary>Intermediate Template</summary>
-
-```markdown
----
-name: "{name}"
-description: "{description}"
-argument-hint: "[action] [args]"
-allowed-tools: [{tools}]
-context: fork
----
-
-# {Title}
-
-You are a **{Title}** agent — {description}.
-
-## Quick Start
-
-/{name} {primary-action} {example-args}
-
-## Arguments
-
-Parse action and arguments from: `$ARGUMENTS`
-
-### Actions
-
-#### `{action1}` - {Action One Description}
-
-{action1} [options]
-
-**Workflow:**
-{Specific numbered steps for this action}
-
-#### `{action2}` - {Action Two Description}
-
-{action2} [options]
-
-**Workflow:**
-{Specific numbered steps for this action}
-
-## Quality Checks
-
-Before completing any action:
-- [ ] {Specific validation relevant to this skill}
-- [ ] {Another specific check}
-- [ ] Confirm with user if uncertain
-
-## Error Handling
-
-- {Specific error scenario}: {How to handle it}
-- {Another error scenario}: {How to handle it}
-- Ask the user for clarification when requirements are ambiguous
-```
-
-</details>
-
-<details>
-<summary>Advanced Template (with sub-agents)</summary>
-
-```markdown
----
-name: "{name}"
-description: "{description}"
-argument-hint: "[action] [args] [--flag]"
-allowed-tools: [{tools}]
-context: fork
----
-
-# {Title}
-
-You are a **{Title} Orchestrator** — {description}.
-
-## Quick Start
-
-/{name} {primary-action} {example-args} --flag
-
-## Arguments
-
-Parse action, arguments, and flags from: `$ARGUMENTS`
-
-### Actions
-
-#### `{action1}` - {Primary Action}
-
-{action1} <required> [optional] [--verbose]
-
-**Workflow:**
-1. Analyze input and determine scope
-2. Delegate to specialized sub-agents via Task tool
-3. Collect and validate results
-4. Present unified output
-
-**Sub-agents:**
-- Use `Task` with `subagent_type=general-purpose` for {specific purpose}
-- Use `Task` with `subagent_type=Bash` for {specific purpose}
-
-#### `{action2}` - {Secondary Action}
-
-{action2} <required>
-
-**Workflow:**
-{Specific numbered steps}
-
-## Quality Standards
-
-- All outputs must be validated before presentation
-- Error messages must be actionable
-- Progress should be reported for long operations
-- User confirmation required for destructive operations
-
-## Error Handling
-
-- Tool failures: retry once, then explain and suggest alternatives
-- Missing dependencies: detect and provide installation instructions
-- Ambiguous requests: ask clarifying questions via AskUserQuestion
-```
-
-</details>
-
-**Phase 4: Iterative Refinement**
-
-After writing the SKILL.md:
-
-1. Read back the generated file
-2. Self-review against this checklist:
-   - Every section has real, specific content (no placeholders)
-   - Workflow steps are actionable and detailed
-   - Argument descriptions match the concept
-   - The agent persona instruction is clear and specific
-   - Error handling covers realistic scenarios
-3. Present the skill to the user and ask via AskUserQuestion: "Here is the generated skill. Would you like to refine any section, or does this look good?"
-4. If the user wants changes, apply them and re-present
-5. Loop until the user is satisfied
-
-**Phase 5: Validate**
-
-Run the CLI validator:
-
-```bash
-npx myaidev-method addon validate --dir .claude/skills/{slug}
-```
-
-- If errors: fix them automatically in the SKILL.md and re-validate
-- If warnings: present to user and ask if they want to address them
-- Loop until validation passes with no errors
-
-**Phase 6: Test**
-
-Guide the user through testing:
-
-1. Explain how to invoke the skill: `/{skill-name}` or `/{skill-name} {action} {args}`
-2. Generate 2-3 specific test invocation commands based on the skill's actions
-3. Ask the user to try invoking the skill and report results via AskUserQuestion
-4. If issues are reported, iterate on the SKILL.md to fix them
-
-**Phase 7: Publish Decision**
-
-Ask the user via AskUserQuestion: "Would you like to submit this skill to the MyAIDev marketplace for review?"
-
-- If yes: ensure user is authenticated (`npx myaidev-method login` if needed), then run:
-  ```bash
-  npx myaidev-method addon submit --dir .claude/skills/{slug} -y
-  ```
-  Display the submission ID and explain the review process (AI analysis + admin review).
-- If no: summarize what was created and how to submit later:
-  ```
-  Skill created at: .claude/skills/{slug}/SKILL.md
-  To submit later: npx myaidev-method addon submit --dir .claude/skills/{slug}
-  To check status: npx myaidev-method addon status
-  ```
-
----
-
-### `refine <path>` — Improve an Existing Skill
-
-Takes a path to an existing SKILL.md and improves it.
-
-**Workflow:**
-
-1. Read the existing SKILL.md at the provided path
-2. Analyze against marketplace quality standards:
-   - Frontmatter completeness (name, description with "when" clause, allowed-tools, context)
-   - Content structure (H1, H2 sections, Quick Start, Arguments, Workflow)
-   - Workflow specificity (no placeholder text)
-   - Error handling section present
-   - Security compliance (no dangerous commands or credential paths)
-3. Use AskUserQuestion to present findings:
-   - List strengths (what's good)
-   - List improvement areas (what needs work)
-   - Ask which areas to focus on
-4. Apply the improvements
-5. Run validation: `npx myaidev-method addon validate --dir {path}`
-6. Present the updated skill and ask if further changes are needed
-7. Iterate until the user is satisfied
-
----
-
-### `test <path>` — Test a Skill
-
-Validates a skill and provides a testing plan.
-
-**Workflow:**
-
-1. Read the SKILL.md at the provided path
-2. Run `npx myaidev-method addon validate --dir {path}`
-3. If validation errors: offer to fix them before proceeding
-4. Parse the SKILL.md to understand its actions and arguments
-5. Generate a test plan with specific invocation commands for each action
-6. Present the test plan to the user
-7. Ask the user to run the tests and report results via AskUserQuestion
-8. If issues are found, offer to fix the SKILL.md
-
----
-
-### `validate <path>` — Quick Validation
-
-Run validation with actionable fix suggestions.
-
-**Workflow:**
-
-1. Run `npx myaidev-method addon validate --dir {path}`
-2. If errors found:
-   - Read the SKILL.md
-   - Fix each error automatically (missing frontmatter fields, structure issues, security violations)
-   - Write the fixed file
-   - Re-validate to confirm fixes
-3. If warnings found: explain each and offer to address them
-4. Report final validation status
-
----
-
-### `publish <path>` — Submit to Marketplace
-
-Validate and submit a skill for review.
-
-**Workflow:**
-
-1. Run validation first — abort if errors remain after attempted fixes
-2. Show skill summary: name, description, category, section count
-3. Confirm with user via AskUserQuestion
-4. Check authentication: run `npx myaidev-method login` if needed
-5. Submit:
-   ```bash
-   npx myaidev-method addon submit --dir {path} -y
-   ```
-6. Display submission result, submission ID, and how to check status:
-   ```bash
-   npx myaidev-method addon status
-   ```
-
----
-
-### No Action — Interactive Menu
-
-If no action is specified:
-
-Use AskUserQuestion to present options:
-- **Create a new skill** — full guided workflow from concept to publication
-- **Refine an existing skill** — analyze and improve a SKILL.md
-- **Test a skill** — validate and generate test plan
-- **Submit a skill** — validate and publish to marketplace
-
-Execute the chosen action.
-
----
-
-## Skill Quality Standards
-
-When building or refining skills, enforce these standards:
-
-### Frontmatter Requirements
-
-| Field | Required | Rules |
-|-------|----------|-------|
-| `name` | Yes | Lowercase with hyphens, max 64 chars, descriptive |
-| `description` | Yes | Must include "when" clause (e.g., "Use when...") |
-| `allowed-tools` | Yes | Only tools the skill actually uses |
-| `argument-hint` | Yes | Show expected argument format |
-| `context` | Yes | Use `fork` for most skills (isolates execution) |
-
-### Content Checklist
-
-- [ ] H1 heading matches skill purpose
-- [ ] Quick Start section with concrete usage example
-- [ ] Arguments section documenting `$ARGUMENTS` parsing
-- [ ] Each action has a Workflow section with numbered steps
-- [ ] No placeholder text — every step must be specific
-- [ ] Error handling section with realistic scenarios
-- [ ] Output/result description
-
-### Security Rules (violations block submission)
-
-- Never reference credential paths (SSH keys, AWS configs, GPG keyrings, system password files)
-- Never include destructive commands (recursive force-delete on root, world-writable permissions, disk formatting, raw disk writes)
-- Avoid piping remote scripts directly into shell interpreters
-- Minimize dynamic code evaluation — these are flagged as warnings
-
-### Quality Signals for High AI Scores
-
-The marketplace AI analysis scores skills 0-100 on quality, security, completeness, originality, and usefulness. To score well:
-- Write specific, actionable workflow steps (not generic "do the thing")
-- Include clear input/output contracts for each action
-- Add error recovery strategies
-- Require user confirmation for destructive operations
-- Keep total file size under 50KB
-- Provide genuine value — avoid trivial wrappers
-
-## Error Handling
-
-- If `npx myaidev-method addon validate` fails to execute: check installation with `npx myaidev-method --version`
-- If SKILL.md parsing fails: verify YAML frontmatter syntax (content between `---` delimiters)
-- If submission fails with auth error: run `npx myaidev-method login` first
-- If validation passes locally but fails server-side: ensure running latest CLI version with `npx myaidev-method@latest`
-- For ambiguous requirements: always ask the user via AskUserQuestion rather than guessing