Agent skill

JavaScript Concept Page Workflow

by leonardomso in leonardomso/33-js-concepts

Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.

MITAuto-check passedWriting & Content

Install JavaScript Concept Page Workflow

skills CLI
$ npx skills add leonardomso/33-js-concepts --skill concept-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install leonardomso/33-js-concepts concept-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/leonardomso/33-js-concepts.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/concept-workflow .claude/skills/concept-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
concept-workflow
GitHub stars
67k
Token cost
~3.9k tokens
SKILL.md length
1,138 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.

  • Works in 5 steps: Resource Curation → Concept Writing → Test Writing → …
  • Creating a new JavaScript concept page from scratch with all quality checks
  • SKILL.md covers When to Use, Workflow Overview, Phase 1: Resource Curation and Phase 2: Concept Writing, plus 7 more sections
  • Calls npm

What it does

The skill runs the full pipeline for a new or fully rewritten concept page in the 33 JavaScript concepts repository. Five specialized skills run in order: resource curation, concept writing, test writing for the code examples, fact checking and an SEO review. For partial jobs it points to the matching single skill, such as resource-curator, write-concept, test-writer, fact-check or seo-review.

Each phase has a goal, steps, deliverables and quality gates that must pass before moving on. Resource curation, for example, targets 4-6 articles, 3-4 videos and 2-4 MDN links, verifies that every link responds, requires JavaScript-focused resources with specific descriptions and formats them as Card components ready to paste. Concept writing starts with category selection and frontmatter fields such as title, sidebarTitle and description.

When your agent uses it

  • Creating a new JavaScript concept page from scratch with all quality checks
  • Completely rewriting an existing concept page
  • Running research, writing, tests, fact-checking and SEO as one workflow

Example prompts

  • “Write a complete concept page on closures, from resources to final SEO review.”
  • “Rewrite the event loop page end to end with new resources and tests.”
  • “Create the promises page and run every quality gate before you stop.”

Requirements

  • The resource-curator, write-concept, test-writer, fact-check and seo-review skills

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Resource Curation
  2. Concept Writing
  3. Test Writing
  4. Fact Checking
  5. SEO Review

What it can do on your machine

Read from SKILL.md and the folder at commit 16d0d95. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

JavaScript Concept Page Workflow loads about 3.9k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 1,138 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~3.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from leonardomso/33-js-concepts at commit 16d0d95, republished under its MIT licence (© leonardomso). 1,138 words, ~3,937 tokens.

Download SKILL.mdSave it as .claude/skills/concept-workflow/SKILL.md (or your agent's skills folder).
name
concept-workflow
description
End-to-end workflow for creating complete JavaScript concept documentation, orchestrating all skills from research to final review

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

Show full SKILL.md (465 more words)Show less
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.

markdown
# 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)
- [ ] Videos found (3-4)
- [ ] All links verified working
- [ ] Descriptions written (specific, 2 sentences)
- [ ] Resources formatted as Cards

**Status:** ⬜ Not Started | 🟡 In Progress | ✅ Complete

---

## Phase 2: Concept Writing
- [ ] Frontmatter complete
- [ ] Opening hook written
- [ ] Opening code example added
- [ ] "What you'll learn" box added
- [ ] Main content sections written
- [ ] Key Takeaways added
- [ ] Test Your Knowledge added
- [ ] Related Concepts added
- [ ] Resources pasted from Phase 1
- [ ] Added to docs.json (if new)

**Status:** ⬜ Not Started | 🟡 In Progress | ✅ Complete

---

## Phase 3: Test Writing
- [ ] Code examples extracted and categorized
- [ ] Test file created
- [ ] DOM test file created (if needed)
- [ ] All testable examples have tests
- [ ] Source line references added
- [ ] Tests run and passing

**Test Results:** X passing, X failing

**Status:** ⬜ Not Started | 🟡 In Progress | ✅ Complete

---

## Phase 4: Fact Checking
- [ ] All tests passing
- [ ] Code examples verified accurate
- [ ] MDN links checked (X/X valid)
- [ ] External resources checked (X/X valid)
- [ ] Technical claims audited
- [ ] No misconceptions found
- [ ] Issues fixed

**Status:** ⬜ Not Started | 🟡 In Progress | ✅ Complete

---

## Phase 5: SEO Review
- [ ] Title tag optimized (50-60 chars)
- [ ] Meta description optimized (150-160 chars)
- [ ] Keywords placed correctly
- [ ] Content structure verified
- [ ] Featured snippet optimized
- [ ] Internal links complete

**SEO Score:** X/27 (X%)

**Status:** ⬜ Not Started | 🟡 In Progress | ✅ Complete

---

## Final Status

**All Phases Complete:** ⬜ No | ✅ Yes
**Ready to Publish:** ⬜ No | ✅ Yes
**Completed:** YYYY-MM-DD

Execution Instructions

When executing this workflow, follow these steps:

Step 1: Initialize
markdown
Starting concept workflow for: [CONCEPT NAME]

Category: [fundamentals/functions-execution/web-platform/etc.]
File: /docs/concepts/[concept-name].mdx
Tests: /tests/[category]/[concept-name]/
Step 2: Execute Each Phase

For each phase:

  1. Announce the phase:

    markdown
    ## Phase X: [Phase Name]
    Using skill: [skill-name]
  2. Load the skill to get detailed instructions

  3. Execute the phase following the skill's methodology

  4. Report completion:

    markdown
    Phase X complete:
    - [Deliverable 1]
    - [Deliverable 2]
    - Quality gates: ✅ All passed
  5. Move to next phase only after quality gates pass

Step 3: Final Report

After all phases complete:

markdown
# Workflow Complete: [Concept Name]

## Summary
- **Concept Page:** `/docs/concepts/[concept-name].mdx`
- **Test File:** `/tests/[category]/[concept-name]/[concept-name].test.js`
- **Word Count:** X,XXX words
- **Code Examples:** XX (XX tested)
- **Resources:** X MDN, X articles, X videos

## Quality Metrics
- **Tests:** XX passing
- **Fact Check:** ✅ All verified
- **SEO Score:** XX/27 (XX%)

## Files Created/Modified
1. `/docs/concepts/[concept-name].mdx` (created)
2. `/docs/docs.json` (updated navigation)
3. `/tests/[category]/[concept-name]/[concept-name].test.js` (created)

## Ready to Publish: ✅ Yes

Phase Dependencies

Some phases can be partially parallelized, but the general flow should be:

Phase 1 (Resources) ──┐
                      ├──► Phase 2 (Writing) ──► Phase 3 (Tests) ──┐
                      │                                             │
                      │         ┌───────────────────────────────────┘
                      │         ▼
                      └──► Phase 4 (Fact Check) ──► Phase 5 (SEO)
  • Phase 1 before Phase 2: Resources inform what to write
  • Phase 2 before Phase 3: Need content before writing tests
  • Phase 3 before Phase 4: Tests are part of fact-checking
  • Phase 4 before Phase 5: Fix accuracy issues before SEO polish

Skill Reference

PhaseSkillPurpose
1resource-curatorFind and evaluate external resources
2write-conceptWrite the documentation page
3test-writerGenerate tests for code examples
4fact-checkVerify technical accuracy
5seo-reviewOptimize for search visibility

Each skill has detailed instructions in its own SKILL.md file. Load the appropriate skill at each phase for comprehensive guidance.


Time Estimates

PhaseEstimated TimeNotes
Phase 1: Resources15-30 minDepends on availability of quality resources
Phase 2: Writing1-3 hoursDepends on concept complexity
Phase 3: Tests30-60 minDepends on number of code examples
Phase 4: Fact Check15-30 minMost automated via tests
Phase 5: SEO15-30 minMostly checklist verification
Total2-5 hoursFor a complete concept page

Quick Start

To start the workflow for a new concept:

1. Determine the concept name and category
2. Load this skill (concept-workflow)
3. Execute Phase 1: Load resource-curator, find resources
4. Execute Phase 2: Load write-concept, write the page
5. Execute Phase 3: Load test-writer, create tests
6. Execute Phase 4: Load fact-check, verify accuracy
7. Execute Phase 5: Load seo-review, optimize SEO
8. Generate final report
9. Commit changes

Example prompt to start:

"Create a complete concept page for 'hoisting' using the concept-workflow skill"

This will trigger the full end-to-end workflow, creating a complete, tested, verified, and SEO-optimized concept page.

© leonardomso, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/concept-workflow of leonardomso/33-js-concepts.

Open the folder on GitHubat commit 16d0d95

Compare with similar skills

JavaScript Concept Page Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

JavaScript Concept Page Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
JavaScript Concept Page Workflow this skillleonardomso/33-js-concepts67k—~3.9kAutomated safety check: PassMIT
Beads Documentation Style Guidegastownhall/beads28k—~3.2kAutomated safety check: PassMIT
Technical Writing Standardcursor/plugins10k10 repos~2.4kAutomated safety check: PassNone
Heym Documentation Articlesheymrun/heym1.4k—~780Automated safety check: PassCustom licence
Technical Writing Workflowtokenbender/agent-guides367—~1.3kAutomated safety check: PassApache-2.0
Developer Docs Technical Writervercel-labs/github-tools131—~3.9kAutomated safety check: PassMIT

Similar skills

  • Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.

    28k GitHub stars~3.2k tokensUpdated today
    Writing & ContentAuto-check passed
  • Official

    Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.

    10k GitHub starsUsed in 10 repos~2.4k tokens
    Writing & ContentAuto-check passed
  • Creates and updates documentation articles for the Heym platform: category choice, manifest entry, markdown file and cross-links from existing pages.

    1.4k GitHub stars~780 tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Technical Writing Workflow

    tokenbender/agent-guides

    A skill your agent uses for planning, researching, drafting, revising, or auditing technical write-ups, textbooks, papers, reports, READMEs, research notes, PR narratives, and public technical prose.

    367 GitHub stars~1.3k tokensUpdated 2 mo ago
    Writing & ContentAuto-check passed
  • Developer Docs Technical Writer

    vercel-labs/github-tools

    Official

    Writes, reviews and edits developer documentation for SDKs, libraries and frameworks, from getting-started guides and API references to migration guides.

    131 GitHub stars~3.9k tokensUpdated 8 days ago
    Writing & ContentAuto-check passed
  • Aholo Viewer Docs

    manycoretech/aholo-viewer

    Guides writing and maintaining Aholo Viewer documentation: README, AGENTS.md, architecture notes, bilingual manual pages and AI collaboration guides.

    1.1k GitHub stars~341 tokensUpdated 13 days ago
    Writing & ContentAuto-check passed

More from leonardomso/33-js-concepts

  • JavaScript Concept Fact Checker

    leonardomso/33-js-concepts

    Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.

    67k GitHub starsUsed in 1 repo~5k tokens
    Auto-check passed
  • JS Concept Resource Curator

    leonardomso/33-js-concepts

    Finds, vets, writes up and maintains external articles, videos and courses for JavaScript concept pages, including audits for broken and outdated links.

    67k GitHub stars~4.9k tokensUpdated 26 days ago
    Auto-check passed
  • JavaScript Concept Page SEO Audit

    leonardomso/33-js-concepts

    Runs a five-step SEO audit on JavaScript concept pages: keyword clusters, on-page checks, featured snippets, internal links and a written report.

    67k GitHub stars~8.8k tokensUpdated 26 days ago
    Auto-check passed
  • Concept Page Test Writer

    leonardomso/33-js-concepts

    Generates Vitest tests for every runnable code example on a JavaScript concept documentation page, following a four-phase extraction and conversion process.

    67k GitHub stars~5.5k tokensUpdated 26 days ago
    Auto-check passed
  • JavaScript Concept Page Writer

    leonardomso/33-js-concepts

    Writes or reviews documentation pages for the 33 JavaScript Concepts project, following its structure, a beginner-friendly voice and rules against AI-sounding language.

    67k GitHub stars~14k tokensUpdated 26 days ago
    Auto-check passed

Works with

Questions about JavaScript Concept Page Workflow

What does JavaScript Concept Page Workflow do?

Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO. The skill runs the full pipeline for a new or fully rewritten concept page in the 33 JavaScript concepts repository. Five specialized skills run in order: resource curation, concept writing, test writing for the code examples, fact checking and an SEO review.

When should I use JavaScript Concept Page Workflow?

JavaScript Concept Page Workflow fits situations like: creating a new JavaScript concept page from scratch with all quality checks; completely rewriting an existing concept page; running research, writing, tests, fact-checking and SEO as one workflow.

How do I install JavaScript Concept Page Workflow in Claude Code?

Run `npx skills add leonardomso/33-js-concepts --skill concept-workflow -a claude-code`. Or copy the skill folder (.claude/skills/concept-workflow in leonardomso/33-js-concepts) into .claude/skills/concept-workflow in your project. Claude Code loads it when a task matches its description.

How do I install JavaScript Concept Page Workflow in Codex?

Run `npx skills add leonardomso/33-js-concepts --skill concept-workflow -a codex`. Or copy the skill folder (.claude/skills/concept-workflow in leonardomso/33-js-concepts) into .agents/skills/concept-workflow in your project. Codex loads it when a task matches its description.

Can I use JavaScript Concept Page Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add leonardomso/33-js-concepts --skill concept-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/concept-workflow, .gemini/skills/concept-workflow, .github/skills/concept-workflow and .opencode/skills/concept-workflow in your project.

What does JavaScript Concept Page Workflow need to run?

Going by SKILL.md and its folder, JavaScript Concept Page Workflow needs the command-line tools its instructions call (npm). Our summary lists: The resource-curator, write-concept, test-writer, fact-check and seo-review skills.

Does JavaScript Concept Page Workflow access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is JavaScript Concept Page Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does JavaScript Concept Page Workflow use?

JavaScript Concept Page Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does JavaScript Concept Page Workflow use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to JavaScript Concept Page Workflow?

Skills that share tags, products or a category with JavaScript Concept Page Workflow: Beads Documentation Style Guide (gastownhall/beads, 28k stars), Technical Writing Standard (cursor/plugins, 10k stars), Heym Documentation Articles (heymrun/heym, 1.4k stars) and Technical Writing Workflow (tokenbender/agent-guides, 367 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains JavaScript Concept Page Workflow?

leonardomso (a GitHub user) maintains it in leonardomso/33-js-concepts, which has 66,531 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 10, 2026.

Source: leonardomso/33-js-concepts on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.