Agent skill

JS Concept Resource Curator

by leonardomso in 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.

MITAuto-check passedWriting & Content

Install JS Concept Resource Curator

skills CLI
$ npx skills add leonardomso/33-js-concepts --skill resource-curator -a claude-code

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

GitHub CLI
$ gh skill install leonardomso/33-js-concepts resource-curator --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/resource-curator .claude/skills/resource-curator && 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
resource-curator
GitHub stars
67k
Token cost
~4.9k tokens
SKILL.md length
1,322 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 9 steps: Audit Existing Resources → Identify Resource Gaps → Find New Resources → …
  • Adding resources to a new concept page
  • SKILL.md covers When to Use, Resource Curation Methodology, Trusted Sources and Quality Criteria, plus 4 more sections
  • Reaches youtube.com and developer.mozilla.org

What it does

This skill finds, evaluates, adds and maintains external learning resources, such as articles, videos and courses, for JavaScript concept documentation pages, including audits for broken and outdated links. It follows five phases: audit what is already on the page, identify gaps against target counts, find new resources, write descriptions, then format and order everything.

The audit checks that each link returns 200, the content is still accurate, publication dates are not too old for the topic, the syntax is current and descriptions are specific. Targets per page are 2-4 MDN reference links, 4-6 articles, 3-4 videos and optional courses and books, with a mix for beginners and advanced learners and some visual material. Searches use site-restricted queries against trusted sites such as javascript.info, freeCodeCamp, dev.to, YouTube and MDN. Each description takes two sentences, one on what makes the resource unique and one on why to click, and entries use the project's Card syntax with icons.

When your agent uses it

  • Adding resources to a new concept page
  • Refreshing resources on existing pages
  • Auditing a docs site for broken or outdated links
  • Reviewing community-contributed resources

Example prompts

  • “Audit the resources on the closures concept page and replace anything broken or outdated.”
  • “Find beginner-friendly videos and two MDN references for the event loop page.”
  • “Review this contributed link for the promises page and write its two-sentence description.”

Requirements

  • Web search access for finding resources and checking links

Workflow steps

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

  1. Audit Existing Resources
  2. Identify Resource Gaps
  3. Find New Resources
  4. Write Descriptions
  5. Format and Organize
  6. Check Each Link
  7. Content Verification
  8. Description Review
  9. Gap Analysis

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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • youtube.com
    • developer.mozilla.org
    • dev.to
    • github.com
    • medium.com

    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

JS Concept Resource Curator loads about 4.9k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 1,322 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~41
When it runs · the whole SKILL.md, loaded when a task matches
~4.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,322 words, ~4,914 tokens.

Download SKILL.mdSave it as .claude/skills/resource-curator/SKILL.md (or your agent's skills folder).
name
resource-curator
description
Find, evaluate, and maintain high-quality external resources for JavaScript concept documentation, including auditing for broken and outdated links

Skill: Resource Curator for Concept Pages

Use this skill to find, evaluate, add, and maintain high-quality external resources (articles, videos, courses) for concept documentation pages. This includes auditing existing resources for broken links and outdated content.

When to Use

  • Adding resources to a new concept page
  • Refreshing resources on existing pages
  • Auditing for broken or outdated links
  • Reviewing community-contributed resources
  • Periodic link maintenance

Resource Curation Methodology

Follow these five phases for comprehensive resource curation.

Phase 1: Audit Existing Resources

Before adding new resources, audit what's already there:

  1. Check link accessibility — Does each link return 200?
  2. Verify content accuracy — Is the content still correct?
  3. Check publication dates — Is it too old for the topic?
  4. Identify outdated content — Does it use old syntax/patterns?
  5. Review descriptions — Are they specific or generic?
Phase 2: Identify Resource Gaps

Compare current resources against targets:

SectionTarget CountIcon
Reference2-4 MDN linksbook
Articles4-6 articlesnewspaper
Videos3-4 videosvideo
Courses1-3 (optional)graduation-cap
Books1-2 (optional)book

Ask:

  • Are there enough resources for beginners AND advanced learners?
  • Is there visual content (diagrams, animations)?
  • Are official references (MDN) included?
  • Is there diversity in teaching styles?
Phase 3: Find New Resources

Search trusted sources using targeted queries:

For Articles:

[concept] javascript tutorial site:javascript.info
[concept] javascript explained site:freecodecamp.org
[concept] javascript site:dev.to
[concept] javascript deep dive site:2ality.com
[concept] javascript guide site:css-tricks.com

For Videos:

YouTube: [concept] javascript explained
YouTube: [concept] javascript tutorial
YouTube: jsconf [concept]
YouTube: [concept] javascript fireship
YouTube: [concept] javascript web dev simplified

For MDN:

[concept] site:developer.mozilla.org
[API name] MDN
Phase 4: Write Descriptions

Every resource needs a specific, valuable description:

Formula:

Sentence 1: What makes this resource unique OR what it specifically covers
Sentence 2: Why reader should click (what they'll gain, who it's best for)
Phase 5: Format and Organize
  • Use correct Card syntax with proper icons
  • Order resources logically (foundational first, advanced later)
  • Ensure consistent formatting

Trusted Sources

Reference Sources (Priority Order)
PrioritySourceURLBest For
1MDN Web Docsdeveloper.mozilla.orgAPI docs, guides, compatibility
2ECMAScript Spectc39.es/ecma262Authoritative behavior
3Node.js Docsnodejs.org/docsNode-specific APIs
4Web.devweb.devPerformance, best practices
5Can I Usecaniuse.comBrowser compatibility
Article Sources (Priority Order)
PrioritySourceWhy Trusted
1javascript.infoComprehensive, exercises, well-maintained
2MDN GuidesOfficial, accurate, regularly updated
3freeCodeCampBeginner-friendly, practical
42ality (Dr. Axel)Deep technical dives, spec-focused
5CSS-TricksDOM, visual topics, well-written
6dev.to (Lydia Hallie)Visual explanations, animations
7LogRocket BlogPractical tutorials, real-world
8Smashing MagazineIn-depth, well-researched
9Digital OceanClear tutorials, examples
10Kent C. DoddsTesting, React, best practices
Video Creators (Priority Order)
PriorityCreatorStyleBest For
1FireshipFast, modern, entertainingQuick overviews, modern JS
2Web Dev SimplifiedClear, beginner-friendlyBeginners, fundamentals
3Fun Fun FunctionDeep-dives, personalityUnderstanding "why"
4Traversy MediaComprehensive crash coursesFull topic coverage
5JSConf/dotJSExpert conference talksAdvanced, in-depth
6AcademindThorough explanationsComplete understanding
7The Coding TrainCreative, visualVisual learners
8Wes BosPractical, real-worldApplied learning
9The Net NinjaStep-by-step tutorialsFollowing along
10Programming with MoshProfessional, clearCareer-focused
Course Sources
SourceTypeNotes
javascript.infoFreeComprehensive, exercises
PiccalilliFreeWell-written, modern
freeCodeCampFreeProject-based
Frontend MastersPaidExpert instructors
Egghead.ioPaidShort, focused lessons
Udemy (top-rated)PaidCheck reviews carefully
CodecademyFreemiumInteractive

Quality Criteria

Must Have (Required)
  • Link works — Returns 200 (not 404, 301, 5xx)
  • JavaScript-focused — Not primarily about C#, Python, Java, etc.
  • Technically accurate — No factual errors or anti-patterns
  • Accessible — Free or has meaningful free preview
Should Have (Preferred)
  • Recent enough — See publication date guidelines below
  • Reputable source — From trusted sources list or well-known creator
  • Unique perspective — Not duplicate of existing resources
  • Appropriate depth — Matches concept complexity
  • Good engagement — Positive comments, high views (for videos)
Red Flags (Reject)
Red FlagWhy It Matters
Uses var everywhereOutdated for ES6+ topics
Teaches anti-patternsHarmful to learners
Primarily other languagesWrong focus
Hard paywall (no preview)Inaccessible
Pre-2015 for modern topicsLikely outdated
Low quality commentsOften indicates issues
Factual errorsSpreads misinformation
Clickbait title, thin contentWastes reader time

Publication Date Guidelines

Topic CategoryMinimum YearReasoning
ES6+ Features2015+ES6 released June 2015
Promises2015+Native Promises in ES6
async/await2017+ES2017 feature
ES Modules2018+Stable browser support
Optional chaining (?.)2020+ES2020 feature
Nullish coalescing (??)2020+ES2020 feature
Top-level await2022+ES2022 feature
Fundamentals (closures, scope, this)AnyCore concepts don't change
DOM manipulation2018+Modern APIs preferred
Fetch API2017+Widespread support

Rule of thumb: For time-sensitive topics, prefer content from the last 3-5 years. For fundamentals, older classic content is often excellent.


Description Writing Guide

The Formula
Sentence 1: What makes this resource unique OR what it specifically covers
Sentence 2: Why reader should click (what they'll gain, who it's best for)
Good Examples
markdown
<Card title="JavaScript Visualized: Promises & Async/Await — Lydia Hallie" icon="newspaper" href="https://dev.to/lydiahallie/javascript-visualized-promises-async-await-5gke">
  Animated GIFs showing the call stack, microtask queue, and event loop in action. 
  The visuals make Promise execution order finally click for visual learners.
</Card>

<Card title="What the heck is the event loop anyway? — Philip Roberts" icon="video" href="https://www.youtube.com/watch?v=8aGhZQkoFbQ">
  The legendary JSConf talk that made the event loop click for millions of developers. 
  Philip Roberts' live visualizations are the gold standard — a must-watch.
</Card>

<Card title="You Don't Know JS: Scope & Closures — Kyle Simpson" icon="book" href="https://github.com/getify/You-Dont-Know-JS/blob/2nd-ed/scope-closures/README.md">
  Kyle Simpson's deep dive into JavaScript's scope mechanics and closure behavior. 
  Goes beyond the basics into edge cases and mental models for truly understanding scope.
</Card>

<Card title="JavaScript Promises in 10 Minutes — Web Dev Simplified" icon="video" href="https://www.youtube.com/watch?v=DHvZLI7Db8E">
  Quick, clear explanation covering Promise creation, chaining, and error handling. 
  Perfect starting point if you're new to async JavaScript.
</Card>

<Card title="How to Escape Async/Await Hell — Aditya Agarwal" icon="newspaper" href="https://medium.com/free-code-camp/avoiding-the-async-await-hell-c77a0fb71c4c">
  The pizza-and-drinks ordering analogy makes parallel vs sequential execution crystal clear. 
  Essential reading once you know async/await basics but want to write faster code.
</Card>
Bad Examples (Avoid)
markdown
<!-- TOO GENERIC -->
<Card title="Promises Tutorial" icon="newspaper" href="...">
  A comprehensive guide to Promises in JavaScript.
</Card>

<!-- NO VALUE PROPOSITION -->
<Card title="Learn Closures" icon="video" href="...">
  This video explains closures in JavaScript.
</Card>

<!-- VAGUE, NO SPECIFICS -->
<Card title="JavaScript Guide" icon="newspaper" href="...">
  Everything you need to know about JavaScript.
</Card>

<!-- JUST RESTATING THE TITLE -->
<Card title="Understanding the Event Loop" icon="video" href="...">
  A video about understanding the event loop.
</Card>
Words and Phrases to Avoid
AvoidWhyUse Instead
"comprehensive guide to..."Vague, overusedSpecify what's covered
"learn all about..."GenericWhat specifically will they learn?
"everything you need to know..."HyperbolicBe specific
"great tutorial on..."Subjective fillerWhy is it great?
"explains X"Too basicHow does it explain? What's unique?
"in-depth look at..."VagueWhat depth? What aspect?
Show full SKILL.md (555 more words)Show less
Words and Phrases That Work
Good PhraseExample
"step-by-step walkthrough""Step-by-step walkthrough of building a Promise from scratch"
"visual explanation""Visual explanation with animated diagrams"
"deep dive into""Deep dive into V8's optimization strategies"
"practical examples of""Practical examples of closures in React hooks"
"the go-to reference for""The go-to reference for array method signatures"
"finally makes X click""Finally makes prototype chains click"
"perfect for beginners""Perfect for beginners new to async code"
"covers X, Y, and Z""Covers creation, chaining, and error handling"

For each resource in the concept page:

  1. Click the link — Does it load?
  2. Note the HTTP status:
StatusMeaningAction
200OKKeep, continue to content check
301/302RedirectUpdate to final URL
404Not FoundRemove or find replacement
403ForbiddenCheck manually, may be geo-blocked
5xxServer ErrorRetry later, may be temporary
Step 2: Content Verification

For each accessible link:

  1. Skim the content — Is it still accurate?
  2. Check the date — When was it published/updated?
  3. Verify JavaScript focus — Is it primarily about JS?
  4. Look for red flags — Anti-patterns, errors, outdated syntax
Step 3: Description Review

For each resource:

  1. Read current description — Is it specific?
  2. Compare to actual content — Does it match?
  3. Check for generic phrases — "comprehensive guide", etc.
  4. Identify improvements — How can it be more specific?
Step 4: Gap Analysis

After auditing all resources:

  1. Count by section — Do we meet targets?
  2. Check diversity — Beginner AND advanced? Visual AND text?
  3. Identify missing types — No MDN? No videos?
  4. Note recommendations — What should we add?

Resource Section Templates

Reference Section
markdown
## Reference

<CardGroup cols={2}>
  <Card title="[Main Topic] — MDN" icon="book" href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/...">
    Official MDN documentation covering [specific aspects]. 
    The authoritative reference for [what it's best for].
  </Card>
  <Card title="[Related API/Concept] — MDN" icon="book" href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/...">
    [What this reference covers]. 
    Essential reading for understanding [specific aspect].
  </Card>
</CardGroup>
Articles Section
markdown
## Articles

<CardGroup cols={2}>
  <Card title="[Article Title]" icon="newspaper" href="...">
    [What makes it unique/what it covers]. 
    [Why read this one/who it's for].
  </Card>
  <Card title="[Article Title]" icon="newspaper" href="...">
    [Specific coverage]. 
    [Value proposition].
  </Card>
  <Card title="[Article Title]" icon="newspaper" href="...">
    [Unique angle]. 
    [Why it's worth reading].
  </Card>
  <Card title="[Article Title]" icon="newspaper" href="...">
    [What it covers]. 
    [Best for whom].
  </Card>
</CardGroup>
Videos Section
markdown
## Videos

<CardGroup cols={2}>
  <Card title="[Video Title] — [Creator]" icon="video" href="https://www.youtube.com/watch?v=...">
    [What it covers/unique approach]. 
    [Why watch/who it's for].
  </Card>
  <Card title="[Video Title] — [Creator]" icon="video" href="https://www.youtube.com/watch?v=...">
    [Specific focus]. 
    [What makes it stand out].
  </Card>
  <Card title="[Video Title] — [Creator]" icon="video" href="https://www.youtube.com/watch?v=...">
    [Coverage]. 
    [Value].
  </Card>
</CardGroup>
Books Section (Optional)
markdown
<Card title="[Book Title] — [Author]" icon="book" href="...">
  [What the book covers and its approach]. 
  [Who should read it and what they'll gain].
</Card>
Courses Section (Optional)
markdown
<CardGroup cols={2}>
  <Card title="[Course Title] — [Platform]" icon="graduation-cap" href="...">
    [What the course covers]. 
    [Format and who it's best for].
  </Card>
</CardGroup>

Resource Audit Report Template

Use this template to document audit findings.

markdown
# Resource Audit Report: [Concept Name]

**File:** `/docs/concepts/[slug].mdx`
**Date:** YYYY-MM-DD
**Auditor:** [Name/Claude]

---

## Summary

| Metric | Count |
|--------|-------|
| Total Resources | XX |
| Working Links (200) | XX |
| Broken Links (404) | XX |
| Redirects (301/302) | XX |
| Outdated Content | XX |
| Generic Descriptions | XX |

## Resource Count vs Targets

| Section | Current | Target | Status |
|---------|---------|--------|--------|
| Reference (MDN) | X | 2-4 | ✅/⚠️/❌ |
| Articles | X | 4-6 | ✅/⚠️/❌ |
| Videos | X | 3-4 | ✅/⚠️/❌ |
| Courses | X | 0-3 | ✅/⚠️/❌ |

---

## Broken Links (Remove or Replace)

| Resource | Line | URL | Status | Action |
|----------|------|-----|--------|--------|
| [Title] | XX | [URL] | 404 | Remove |
| [Title] | XX | [URL] | 404 | Replace with [alternative] |

---

## Redirects (Update URLs)

| Resource | Line | Old URL | New URL |
|----------|------|---------|---------|
| [Title] | XX | [old] | [new] |

---

## Outdated Resources (Consider Replacing)

| Resource | Line | Issue | Recommendation |
|----------|------|-------|----------------|
| [Title] | XX | Published 2014, uses var throughout | Replace with [modern alternative] |
| [Title] | XX | Pre-ES6, no mention of let/const | Find updated version or replace |

---

## Description Improvements Needed

| Resource | Line | Current | Suggested |
|----------|------|---------|-----------|
| [Title] | XX | "A guide to closures" | "[Specific description with value prop]" |
| [Title] | XX | "Learn about promises" | "[What makes it unique]. [Why read it]." |

---

## Missing Resources (Recommendations)

| Type | Gap | Suggested Resource | URL |
|------|-----|-------------------|-----|
| Reference | No main MDN link | [Topic] — MDN | [URL] |
| Article | No beginner guide | [Title] — javascript.info | [URL] |
| Video | No visual explanation | [Title] — [Creator] | [URL] |
| Article | No advanced deep-dive | [Title] — 2ality | [URL] |

---

## Non-JavaScript Resources (Remove)

| Resource | Line | Issue |
|----------|------|-------|
| [Title] | XX | Primarily about C#, not JavaScript |

---

## Action Items

### High Priority (Do First)
1. **Remove broken link:** [Title] (line XX)
2. **Add missing MDN reference:** [Topic]
3. **Replace outdated resource:** [Title] with [alternative]

### Medium Priority
1. **Update redirect URL:** [Title] (line XX)
2. **Improve description:** [Title] (line XX)
3. **Add beginner-friendly article**

### Low Priority
1. **Add additional video resource**
2. **Consider adding course section**

---

## Verification Checklist

After making changes:

- [ ] All broken links removed or replaced
- [ ] All redirect URLs updated
- [ ] Outdated resources replaced
- [ ] Generic descriptions rewritten
- [ ] Missing resource types added
- [ ] Resource counts meet targets
- [ ] All new links verified working
- [ ] All descriptions are specific and valuable

Quick Reference

Icon Reference
Content TypeIcon Value
MDN/Official docsbook
Articles/Blog postsnewspaper
Videosvideo
Coursesgraduation-cap
Booksbook
Related conceptsContext-appropriate
Character Guidelines
ElementGuideline
Card titleKeep concise, include creator for videos
Description sentence 1What it covers / what's unique
Description sentence 2Why read/watch / who it's for
Resource Ordering

Within each section, order resources:

  1. Most foundational/beginner-friendly first
  2. Official references before community content
  3. Most highly recommended prominently placed
  4. Advanced/niche content last

Quality Checklist

  • All links return 200 (not 404, 301)
  • No redirect chains
  • No hard paywalls without notice
  • All URLs are HTTPS where available
Content Quality
  • All resources are JavaScript-focused
  • No resources teaching anti-patterns
  • Publication dates appropriate for topic
  • Mix of beginner and advanced content
  • Visual and text resources included
Description Quality
  • All descriptions are specific (not generic)
  • Descriptions explain unique value
  • No "comprehensive guide to..." phrases
  • Each description is 2 sentences
  • Descriptions match actual content
Completeness
  • 2-4 MDN/official references
  • 4-6 quality articles
  • 3-4 quality videos
  • Resources ordered logically
  • Diversity in teaching styles

Summary

When curating resources for a concept page:

  1. Audit first — Check all existing links and content
  2. Identify gaps — Compare against targets (2-4 refs, 4-6 articles, 3-4 videos)
  3. Find quality resources — Search trusted sources
  4. Write specific descriptions — What's unique + why read/watch
  5. Format correctly — Proper Card syntax, icons, ordering
  6. Document changes — Use the audit report template

Remember: Resources should enhance learning, not pad the page. Every link should offer genuine value. Quality over quantity — a few excellent resources beat many mediocre ones.

© 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/resource-curator of leonardomso/33-js-concepts.

Open the folder on GitHubat commit 16d0d95

Compare with similar skills

JS Concept Resource Curator 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.

JS Concept Resource Curator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
JS Concept Resource Curator this skillleonardomso/33-js-concepts67k—~4.9kAutomated safety check: PassMIT
Dynamo Content DesignerDynamoDS/Dynamo2k—~1.6kAutomated safety check: PassApache-2.0
Contrarian And Opinionsocial-media-skills/skills134—~2kAutomated safety check: PassMIT
Install Anti Sloptrycompai/crm11k1 repos~881Automated safety check: PassMIT
Beads Documentation Style Guidegastownhall/beads28k—~3.2kAutomated safety check: PassMIT
Technical Writing Standardcursor/plugins11k10 repos~2.4kAutomated safety check: PassNone

Similar skills

  • Technical writing specialist for Dynamo product documentation, blog posts, tutorials, and educational content.

    2k GitHub stars~1.6k tokensUpdated today
    Writing & ContentAuto-check passed
  • Contrarian And Opinion

    social-media-skills/skills

    The point-of-view content type — articulate, sharpen, and argue a genuinely-held contrarian stance / hot take / opinion / thought-leadership position that builds authority and real debate.

    134 GitHub stars~2k tokensUpdated 8 days ago
    Writing & ContentAuto-check passed
  • Install Anti Slop

    trycompai/crm

    Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.

    11k GitHub starsUsed in 1 repo~881 tokens
    Writing & ContentAuto-check passed
  • 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.

    11k GitHub starsUsed in 10 repos~2.4k tokens
    Writing & ContentAuto-check passed
  • Translate

    tagspaces/tagspaces

    Translate new or untranslated i18n strings from the English locale files (core.json + peri.json) into all other locales, maintaining consistency with each language's existing translations.

    5.3k GitHub stars~2.2k tokensUpdated 3 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
  • JavaScript Concept Page Workflow

    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.

    67k GitHub stars~3.9k tokensUpdated 29 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 29 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 29 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 29 days ago
    Auto-check passed

Works with

Questions about JS Concept Resource Curator

What does JS Concept Resource Curator do?

Finds, vets, writes up and maintains external articles, videos and courses for JavaScript concept pages, including audits for broken and outdated links. This skill finds, evaluates, adds and maintains external learning resources, such as articles, videos and courses, for JavaScript concept documentation pages, including audits for broken and outdated links. It follows five phases: audit what is already on the page, identify gaps against target counts, find new resources, write descriptions, then format and order everything.

When should I use JS Concept Resource Curator?

JS Concept Resource Curator fits situations like: adding resources to a new concept page; refreshing resources on existing pages; auditing a docs site for broken or outdated links; reviewing community-contributed resources.

How do I install JS Concept Resource Curator in Claude Code?

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

How do I install JS Concept Resource Curator in Codex?

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

Can I use JS Concept Resource Curator 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 resource-curator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/resource-curator, .gemini/skills/resource-curator, .github/skills/resource-curator and .opencode/skills/resource-curator in your project.

What does JS Concept Resource Curator need to run?

SKILL.md names no scripts, command-line tools or credentials: JS Concept Resource Curator is instructions for the agent only. Our summary lists: Web search access for finding resources and checking links.

Does JS Concept Resource Curator access the network?

SKILL.md names 5 domains. In commands or code: youtube.com, developer.mozilla.org, dev.to, github.com and medium.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is JS Concept Resource Curator 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 JS Concept Resource Curator use?

JS Concept Resource Curator 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 JS Concept Resource Curator use?

About 4.9k tokens (SKILL.md is roughly 20k 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 JS Concept Resource Curator?

Skills that share tags, products or a category with JS Concept Resource Curator: Dynamo Content Designer (DynamoDS/Dynamo, 2k stars), Contrarian And Opinion (social-media-skills/skills, 134 stars), Install Anti Slop (trycompai/crm, 11k stars) and Beads Documentation Style Guide (gastownhall/beads, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains JS Concept Resource Curator?

leonardomso (a GitHub user) maintains it in leonardomso/33-js-concepts, which has 66,530 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.