Skill atlas

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:

1. Read the ranked list for your job. Prefer 🟢 A (canonical) and 🔵 B (community-proven).
2. Treat 🟡 C as "read before trusting" and 🔴 D as "stale — caution."
3. 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.