CO

concept-workflow

Manages the JavaScript documentation lifecycle from resource curation and writing to testing and SEO optimization.

Install

mkdir -p .claude/skills/concept-workflow && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2264" && unzip -o skill.zip -d .claude/skills/concept-workflow && rm skill.zip

Installs to .claude/skills/concept-workflow

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

End-to-end workflow for creating complete JavaScript concept documentation, orchestrating all skills from research to final review
130 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Curate external learning resources
  • Generate documentation pages with frontmatter
  • Create tests for code examples
  • Verify technical accuracy of content
  • Optimize documentation for search visibility

How it works

The workflow orchestrates five specialized skills in a fixed sequence to research, write, test, verify, and optimize JavaScript documentation.

Inputs & outputs

You give it
Concept name
You get back
Tested, verified, and SEO-optimized documentation page

When to use concept-workflow

  • Creating new concept documentation
  • Rewriting technical guides
  • Documenting complex JS topics

About this skill

Skill: Complete Concept Workflow

Use this skill to create a complete, high-quality concept page from start to finish. This skill orchestrates all five specialized skills in the optimal order:

  1. Resource Curation — Find quality learning resources
  2. Concept Writing — Write the documentation page
  3. Test Writing — Create tests for code examples
  4. Fact Checking — Verify technical accuracy
  5. SEO Review — Optimize for search visibility

When to Use

  • Creating a brand new concept page from scratch
  • Completely rewriting an existing concept page
  • When you want a full end-to-end workflow with all quality checks

For partial tasks, use individual skills instead:

  • Just adding resources? Use resource-curator
  • Just writing content? Use write-concept
  • Just adding tests? Use test-writer
  • Just verifying accuracy? Use fact-check
  • Just optimizing SEO? Use seo-review

Workflow Overview

┌─────────────────────────────────────────────────────────────────────────────┐
│                     COMPLETE CONCEPT WORKFLOW                                │
├─────────────────────────────────────────────────────────────────────────────┤
│                                                                              │
│  INPUT: Concept name (e.g., "hoisting", "event-loop", "promises")           │
│                                                                              │
│  ┌──────────────────┐                                                        │
│  │ PHASE 1: RESEARCH │                                                       │
│  │ resource-curator  │  Find MDN refs, articles, videos                      │
│  └────────┬─────────┘                                                        │
│           ▼                                                                  │
│  ┌──────────────────┐                                                        │
│  │ PHASE 2: WRITE   │                                                        │
│  │ write-concept    │  Create the documentation page                         │
│  └────────┬─────────┘                                                        │
│           ▼                                                                  │
│  ┌──────────────────┐                                                        │
│  │ PHASE 3: TEST    │                                                        │
│  │ test-writer      │  Generate tests for all code examples                  │
│  └────────┬─────────┘                                                        │
│           ▼                                                                  │
│  ┌──────────────────┐                                                        │
│  │ PHASE 4: VERIFY  │                                                        │
│  │ fact-check       │  Verify accuracy, run tests, check links               │
│  └────────┬─────────┘                                                        │
│           ▼                                                                  │
│  ┌──────────────────┐                                                        │
│  │ PHASE 5: OPTIMIZE│                                                        │
│  │ seo-review       │  SEO audit and final optimizations                     │
│  └────────┬─────────┘                                                        │
│           ▼                                                                  │
│  OUTPUT: Complete, tested, verified, SEO-optimized concept page              │
│                                                                              │
└─────────────────────────────────────────────────────────────────────────────┘

Phase 1: Resource Curation

Skill: resource-curator Goal: Gather high-quality external resources before writing

What to Do

  1. Identify the concept category (fundamentals, async, OOP, etc.)
  2. Search for MDN references — Official documentation
  3. Find quality articles — Target 4-6 from trusted sources
  4. Find quality videos — Target 3-4 from trusted creators
  5. Evaluate each resource — Check quality criteria
  6. Write specific descriptions — 2 sentences each
  7. Format as Card components — Ready to paste into the page

Deliverables

  • List of 2-4 MDN/reference links with descriptions
  • List of 4-6 article links with descriptions
  • List of 3-4 video links with descriptions
  • Optional: 1-2 courses or books

Quality Gates

Before moving to Phase 2:

  • All links verified working (200 response)
  • All resources are JavaScript-focused
  • Descriptions are specific, not generic
  • Mix of beginner and advanced content

Phase 2: Concept Writing

Skill: write-concept Goal: Create the full documentation page

What to Do

  1. Determine the category for file organization
  2. Create the frontmatter (title, sidebarTitle, description)
  3. Write the opening hook — Question that draws readers in
  4. Add opening code example — Simple example in first 200 words
  5. Write "What you'll learn" box — 5-7 bullet points
  6. Write main content sections:
    • What is [concept]? (with 40-60 word definition for featured snippet)
    • Real-world analogy
    • How it works (with diagrams)
    • Code examples (multiple, progressive complexity)
    • Common mistakes
    • Edge cases
  7. Add Key Takeaways — 8-10 numbered points
  8. Add Test Your Knowledge — 5-6 Q&A accordions
  9. Add Related Concepts — 4 Cards linking to related topics
  10. Add Resources — Paste resources from Phase 1

Deliverables

  • Complete .mdx file at /docs/concepts/{concept-name}.mdx
  • File added to docs.json navigation (if new)

Quality Gates

Before moving to Phase 3:

  • Frontmatter complete (title, sidebarTitle, description)
  • Opens with question hook
  • Code example in first 200 words
  • "What you'll learn" Info box present
  • All required sections present
  • Resources section complete
  • 1,500+ words

Phase 3: Test Writing

Skill: test-writer Goal: Create comprehensive tests for all code examples

What to Do

  1. Scan the concept page for all code examples
  2. Categorize examples:
    • Testable (console.log, return values)
    • DOM-specific (needs jsdom)
    • Error examples (toThrow)
    • Conceptual (skip)
  3. Create test file at tests/{category}/{concept}/{concept}.test.js
  4. Create DOM test file (if needed) at tests/{category}/{concept}/{concept}.dom.test.js
  5. Write tests for each code example with source line references
  6. Run tests to verify all pass

Deliverables

  • Test file: tests/{category}/{concept-name}/{concept-name}.test.js
  • DOM test file (if applicable): tests/{category}/{concept-name}/{concept-name}.dom.test.js
  • All tests passing

Quality Gates

Before moving to Phase 4:

  • All testable code examples have tests
  • Source line references in comments
  • Tests pass: npm test -- tests/{category}/{concept}/
  • DOM tests in separate file with jsdom directive

Phase 4: Fact Checking

Skill: fact-check Goal: Verify technical accuracy of all content

What to Do

  1. Verify code examples:

    • Run tests: npm test -- tests/{category}/{concept}/
    • Check any untested examples manually
    • Verify output comments match actual outputs
  2. Verify MDN/spec claims:

    • Click all MDN links — verify they work
    • Compare API descriptions to MDN
    • Check ECMAScript spec for nuanced claims
  3. Verify external resources:

    • Check all article/video links work
    • Skim content for accuracy
    • Verify descriptions match content
  4. Audit technical claims:

    • Look for "always/never" statements
    • Verify performance claims
    • Check for common misconceptions
  5. Generate fact-check report

Deliverables

  • Fact-check report documenting:
    • Code verification results
    • Link check results
    • Any issues found and fixes made

Quality Gates

Before moving to Phase 5:

  • All tests passing
  • All MDN links valid
  • All external resources accessible
  • No technical inaccuracies found
  • No common misconceptions

Phase 5: SEO Review

Skill: seo-review Goal: Optimize for search visibility

What to Do

  1. Audit title tag:

    • 50-60 characters
    • Primary keyword in first half
    • Ends with "in JavaScript"
    • Contains compelling hook
  2. Audit meta description:

    • 150-160 characters
    • Starts with action word (Learn, Understand, Discover)
    • Contains primary keyword
    • Promises specific value
  3. Audit keyword placement:

    • Keyword in title
    • Keyword in description
    • Keyword in first 100 words
    • Keyword in at least one H2
  4. Audit content structure:

    • Question hook opening
    • Code in first 200 words
    • "What you'll learn" box
    • Short paragraphs
  5. Audit featured snippet optimization:

    • 40-60 word definition after "What is" H2
    • Question-format H2s
    • Numbered steps for how-to content
  6. Audit internal linking:

    • 3-5 related concepts linked
    • Descriptive anchor text
    • Related Concepts section complete
  7. Calculate score and fix any issues

Deliverables

  • SEO audit report with score (X/27)
  • All high-priority fixes implemented

Quality Gates

Before marking complete:

  • Score 24+ out of 27 (90%+)
  • Title optimized
  • Meta description optimized
  • Keywords placed naturally
  • Featured snippet optimized
  • Internal links complete

Complete Workflow Checklist

Use this master checklist to track progress through all phases.

# Concept Workflow: [Concept Name]

**Started:** YYYY-MM-DD
**Target Category:** {category}
**File Path:** `/docs/concepts/{concept-name}.mdx`
**Test Path:** `/tests/{category}/{concept-name}/`

---

## Phase 1: Resource Curation
- [ ] MDN references found (2-4)
- [ ] Articles found (4-6)
- [ 

---

*Content truncated.*

When not to use it

  • When performing only a single, isolated documentation task

Limitations

  • Requires manual execution of individual phases
  • Total time commitment ranges from two to five hours

How it compares

This approach provides a structured, end-to-end lifecycle for documentation instead of manual, fragmented writing processes.

Compared to similar skills

concept-workflow side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
concept-workflow (this skill)67moNo flagsIntermediate
seo-review97moNo flagsIntermediate
schema-markup106moNo flagsIntermediate
docs-writer-reference16moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

seo-review

leonardomso

Perform a focused SEO audit on JavaScript concept pages to maximize search visibility, featured snippet optimization, and ranking potential

953

schema-markup

davila7

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.

1042

docs-writer-reference

reactjs

Reference page structure, templates, and writing patterns for src/content/reference/. For components, see /docs-components. For code examples, see /docs-sandpack.

13

write-concept

leonardomso

Write or review JavaScript concept documentation pages for the 33 JavaScript Concepts project, following strict structure and quality guidelines

00

markdown-to-html

github

Convert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, CommonMark, and standard Markdown flavors.

1662

fact-check

leonardomso

Verify technical accuracy of JavaScript concept pages by checking code examples, MDN/ECMAScript compliance, and external resources to prevent misinformation

746

Search skills

Search the agent skills registry