Atlas / Skills / leonardomso / Concept Workflow

Concept WorkflowSAFE

skills/leonardomso/concept-workflow

πŸ“œ 33 JavaScript concepts every developer should know.

Verdict
SAFE
Grade
B
Trust score
89 /100
Version
β€”
Hosts
β€”
License
MIT
Stars
66,530
01

Overview

πŸ“œ 33 JavaScript concepts every developer should know.

Read from source at commit 6a2a0c0ec722OBSERVED Β· 2026-10-20
Advertisement
02

What it tells the agent

The instruction file, verbatim from the audited commit β€” this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
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, des
03

Trust audit

SAFEgrade B Β· trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeNA
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.

Audited 2026-10-20 Β· audit v0.4.1 Β· source sha 6a2a0c0ec722full audit observations/trust-audit/skill/leonardomso__concept-workflow.json Β· Report an issue / request a re-scan
04

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-206a2a0c0ec722SAFEB89first audit
05

Questions

What does the concept-workflow β€” leonardomso/33-js-concepts skill do?

πŸ“œ 33 JavaScript concepts every developer should know.

Is concept-workflow β€” leonardomso/33-js-concepts safe to install?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.

What can concept-workflow β€” leonardomso/33-js-concepts access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

How current is this page?

The grade is for one exact copy of the source (6a2a0c0ec722), read on 2026-10-20. The repository is watched, and a new audit runs when it changes β€” this is the first audit.

Add this badge to your README

Shows this page's audit result and links back to it. It updates when the audit does.

ModelsAtlas audit badge

Markdown
[![ModelsAtlas audit: Concept Workflow](https://modelsatlas.com/skills/leonardomso/concept-workflow/badge.svg)](https://modelsatlas.com/skills/leonardomso/concept-workflow/)

Not your listing, or something out of date? Claim or update your listing.

Advertisement