skill-atlas
Skill0 starsChanged 5 months agoMITView on GitHub
Find the right public AI-agent skill for a job — and know whether to trust it. Load when about to start a task type (Upwork freelancing, technical interviews, office documents, MCP/tool building, prompt engineering, web/frontend, data analysis, learning English) and you want to know which existing public skills to pull in, rated by source reputation and freshness. Answers "which skill do I load for X, and can I trust it?
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Jorgut/skill-atlastheir own version, first seen Nov 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Jorgut/skill-atlas★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 61
Read the ranked list for your job.
- Distinctive: line 62
Treat 🟡 C as "read before trusting" and 🔴 D as "stale — caution."
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill Atlas
A trust-rated index of public AI-agent skills, organized by job. Use it to answer: "I'm about to do X — which public skills should I load, and can I trust them?"
The skills themselves live in their original repos. This atlas catalogs which ones are good, where they come from, and how stale they are — the trust layer most skill lists skip.
When to load this skill
At the start of a task that matches a known job, before hunting for tools yourself:
| If the task is about… | Read |
| Winning work on Upwork | jobs/upwork.md |
| Technical interview prep | jobs/interview-prep.md |
| Algorithms / system design | jobs/algorithms-system-design.md |
| Career planning / what to learn | jobs/career-roadmaps.md |
| Word/PDF/PowerPoint/Excel | jobs/office-documents.md |
| Building an MCP server / agent tool | jobs/mcp-and-agent-tools.md |
| Writing better prompts | jobs/prompt-engineering.md |
| Frontend / web app build or test | jobs/web-frontend.md |
| Writing idiomatic Go | jobs/go-development.md |
| Choosing Go backend libraries (HTTP, CLI, log, test) | jobs/go-backend-libraries.md |
| Git: rebase, recovery, history | jobs/git-version-control.md |
| Terraform / Kubernetes / infra | jobs/devops-infrastructure.md |
| Dockerfile / compose / containers | jobs/docker-containers.md |
| Schema design, SQL, migrations (Postgres) | jobs/databases-sql.md |
| Designing a REST or gRPC API | jobs/api-design.md |
| Metrics / traces / logs / dashboards | jobs/observability-monitoring.md |
| Caching, queues, scaling, Kafka/Redis | jobs/scalability-distributed-systems.md |
| Async messaging, task queue, workflows | jobs/message-queues-streaming.md |
| Applying a design pattern / refactor | jobs/software-design-patterns.md |
| AWS or GCP — CLI, SDK, services | jobs/cloud-aws-gcp.md |
| CI/CD — GitHub Actions, GitOps deploy | jobs/cicd-pipelines.md |
| Login, OAuth/OIDC, JWT, access control | jobs/authentication-authorization.md |
| Building a UI (React/Vue/Svelte/Next) | jobs/frontend-frameworks.md |
| Writing Go tests, mocks, integration | jobs/go-testing.md |
| Securing an app / authorized pentest | jobs/security.md |
| Exploring / cleaning / charting data | jobs/data-analysis.md |
| Social media / X research | jobs/social-media-research.md |
| Data pipelines, ETL, Airflow/Spark/dbt | jobs/data-engineering.md |
| Building a mobile app (Flutter/RN/iOS) | jobs/mobile-development.md |
| Building an app on LLMs (RAG, agents) | jobs/llm-app-development.md |
| Serving/running LLMs (Ollama/vLLM) | jobs/llm-serving-inference.md |
| Bash scripting, CLI, shell debugging | jobs/linux-shell.md |
| Configuring nginx / reverse proxy / TLS | jobs/nginx-web-servers.md |
| Finding a course/book to learn something | jobs/learning-resources.md |
| Improving English for work | jobs/learning-english.md |
How to use an entry
Each entry carries a trust tier plus source URL, reputation signal, and a
last_validated date. Workflow:
- Read the ranked list for your job. Prefer 🟢 A (canonical) and 🔵 B (community-proven).
- Treat 🟡 C as "read before trusting" and 🔴 D as "stale — caution."
- Load the public skill, then fork it private and adapt it to yourself. The public skill is the starting point; your private version encodes your voice, creds, and rules.
Trust tiers
- 🟢 A — Canonical: official vendor source (Anthropic, the spec author). Trust by authorship.
- 🔵 B — Community-proven: high reputation (stars/installs) and actively maintained.
- 🟡 C — Useful, verify: plausible but low/unknown reputation. Read before trusting.
- 🔴 D — Caution: stale (>12mo), unmaintained, or known-broken. Listed so you don't rediscover it.
Keeping it honest
scripts/revalidate.sh re-checks every source's liveness + GitHub stars/last-push (uses
gh for 5000 req/hr if available). An entry whose last_validated is >6 months old is
treated as C until reproven. A monthly GitHub Action runs this automatically and opens a
tracking issue if any source dies or goes stale — so the atlas can't silently rot. See
_meta/SCHEMA.md for the full schema and CONTRIBUTING.md for the trust bar on new entries.
Index repo: https://github.com/luongs3/skill-atlas — skills remain property of their original authors under their own licenses; this repo provides only the trust assessment.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.