New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Atopile Skills

by atopile in atopile/atopile

How to write and maintain .claude/skills//SKILL.md files: source-of-truth-first process, verification steps, and conventions.

MITAuto-check passedAgent Workflows

Install Atopile Skills

skills CLI
$ npx skills add atopile/atopile --skill atopile-skills -a claude-code

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

GitHub CLI
$ gh skill install atopile/atopile atopile-skills --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/atopile/atopile.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/atopile-skills .claude/skills/atopile-skills && 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
atopile-skills
GitHub stars
4k
Token cost
~893 tokens
SKILL.md length
439 words
Files
1
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

How to write and maintain .claude/skills//SKILL.md files: source-of-truth-first process, verification steps, and conventions.

  • Works in 5 steps: Inventory the skill’s scope → Read the docs, then the code that… → Fix wrong statements (don’t preserve… → …
  • Tasks that involve Skill authoring
  • SKILL.md covers Quick Start, What “Good” Looks Like, Standard Workflow… and Style/Structure Conventions
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Atopile Skills is an agent skill from atopile/atopile. How to write and maintain .claude/skills//SKILL.md files: source-of-truth-first process, verification steps, and conventions.

Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Skill authoring. The repository describes itself as: Design circuit boards with code! ✨ Get software-like design reuse 🚀, validation, version control and collaboration in hardware; starting with electronics ⚡️. The licence is MIT.

When your agent uses it

  • Tasks that involve Skill authoring

Example prompts

  • “/atopile-skills”

Requirements

  • Python 3

Workflow steps

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

  1. Inventory the skill’s scope
  2. Read the docs, then the code that enforces invariants
  3. Fix wrong statements (don’t preserve broken history)
  4. Add a minimal, correct ## Quick Start
  5. Validation checklist (required)

What it can do on your machine

Read from SKILL.md and the folder at commit 619eda7. 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.

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

  • Network

    No URLs in SKILL.md.

    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

Atopile Skills loads about 893 tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 439 words of instructions outside code blocks.

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

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 atopile/atopile at commit 619eda7, republished under its MIT licence (© atopile). 439 words, ~893 tokens.

Download SKILL.mdSave it as .claude/skills/atopile-skills/SKILL.md (or your agent's skills folder).
name
atopile-skills
description
How to write and maintain `.claude/skills/*/SKILL.md` files: source-of-truth-first process, verification steps, and conventions.

Skills Skill (Maintaining Skill Docs)

This skill describes the process for maintaining the skill documentation under .claude/skills/*/SKILL.md.

The goal is that future LLM edits stay accurate, actionable, and grounded in the repo (not vibes).

Quick Start

When updating any skill:

  1. Find the module’s “source-of-truth” docs (README/design notes).
  2. Verify claims directly in code (entrypoints + invariant-enforcing files).
  3. Fix incorrect paths/APIs/tests by searching the repo.
  4. Add/update a small ## Quick Start that actually runs in this repo.
  5. Validate frontmatter + referenced paths.

What “Good” Looks Like

A good skill doc is:

  • Specific: points at exact files and the real entrypoints.
  • Invariant-driven: documents the correctness rules enforced by the code (not aspirational design).
  • Runnable: Quick Start snippets compile/import (or at least match the current API surface).
  • Traceable: any non-obvious claim can be traced to a file path in the repo.

Standard Workflow (Source-of-Truth First)

1) Inventory the skill’s scope
  • Identify the module boundary (directories, packages) and key consumers (“call sites”).
  • Prefer using rg over memory: look for imports, entrypoints, and key classes/functions.
2) Read the docs, then the code that enforces invariants

Use this hierarchy:

  1. A module README/design doc (if present)
  2. The runtime entrypoint(s) used by the rest of the repo
  3. The files that enforce invariants (the places that must remain correct)
  4. Tests that codify behavior

Examples:

  • Solver: src/faebryk/core/solver/README.md + src/faebryk/core/solver/symbolic/invariants.py
  • Graph: src/faebryk/core/zig/src/graph/graph.zig + src/faebryk/core/zig/src/python/graph/graph_py.zig + generated stubs
  • Library: tools/library/gen_F.py is the source-of-truth for _F.py
Show full SKILL.md (204 more words)Show less
3) Fix wrong statements (don’t preserve broken history)

Common failure modes in skill docs:

  • stale file paths (atopile/src/... vs src/...)
  • renamed entrypoints (lsp_server.py vs imaginary server.py)
  • test paths that no longer exist
  • claims about behavior that conflict with the actual API surface (especially Zig bindings)

Rule: if you can’t prove it from the repo, either remove it or label it as a hypothesis with a pointer to where to verify.

4) Add a minimal, correct ## Quick Start

Quick Start should be:

  • 5–20 lines
  • uses the public API surface as used elsewhere in the repo
  • avoids placeholders like src/.../something.zig

Good patterns:

  • CLI snippet for user-facing flows (ato build, ato dev test --llm)
  • Python snippet for core APIs (GraphView.create() / TypeGraph.create(...))
5) Validation checklist (required)
  • Frontmatter YAML parses and contains name and description.
  • Every referenced src/, tools/, and test/ path exists (exclude generated build outputs).
  • Any code identifiers mentioned (classes/functions) exist (rg check).
  • Quick Start uses correct import paths and function signatures.

Style/Structure Conventions

Prefer this ordering:

  1. One-paragraph summary
  2. ## Quick Start
  3. ## Relevant Files
  4. ## Dependants (Call Sites)
  5. ## How to Work With / Develop / Test
  6. ## Best Practices / ## Invariants (when applicable)

Keep the doc concise and “repo-local”: avoid external links unless they’re stable standards docs.

© atopile, 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/atopile-skills of atopile/atopile.

Open the folder on GitHubat commit 619eda7

Compare with similar skills

Atopile Skills 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.

Atopile Skills compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Atopile Skills this skillatopile/atopile4k—~893Automated safety check: PassMIT
Skill CreatorAzure/azqr79689 repos~8.2kAutomated safety check: PassApache-2.0
Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase10k11 repos~3.5kAutomated safety check: PassMIT
Darwin Skill Optimizeralchaincyf/darwin-skill6.2k1 repos~4.7kAutomated safety check: PassMIT
Claude Code Command Developmentanthropics/claude-plugins-official38k10 repos~4.8kAutomated safety check: PassApache-2.0
Claude Code Plugin Structureanthropics/claude-plugins-official38k10 repos~3.4kAutomated safety check: PassApache-2.0

Similar skills

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    796 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Skill Developer Guide

    diet103/claude-code-infrastructure-showcase

    A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.

    10k GitHub starsUsed in 11 repos~3.5k tokens
    Agent WorkflowsAuto-check passed

  • Darwin Skill Optimizer

    alchaincyf/darwin-skill

    Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.

    6.2k GitHub starsUsed in 1 repo~4.7k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Command Development

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.

    38k GitHub starsUsed in 10 repos~4.8k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Plugin Structure

    anthropics/claude-plugins-official

    Official

    Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.

    38k GitHub starsUsed in 10 repos~3.4k tokens
    Agent WorkflowsAuto-check passed

  • Skill Release Gate

    rohitg00/ai-engineering-from-scratch

    Evaluates an Agent Skill bundle before release for structure, trigger quality, artifact improvement, script correctness, safety, installed-tree integrity and host portability.

    67k GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from atopile/atopile

All 19 skills in this repo

  • Ato Language

    atopile/atopile

    Reference for the .ato declarative DSL: type system, connection semantics, constraint model, and standard library.

    4k GitHub stars~3.5k tokensUpdated 4 mo ago
    Auto-check passed

  • Compiler

    atopile/atopile

    How the atopile compiler builds and links TypeGraphs from .ato (ANTLR front-end → AST → TypeGraph → Linker → DeferredExecutor), plus the key invariants and test entrypoints.

    4k GitHub stars~1k tokensUpdated 4 mo ago
    Auto-check passed

  • Domain Layer

    atopile/atopile

    Instructions for electronics-specific logic and build processes: netlists, PCBs, build steps, and exporters.

    4k GitHub stars~791 tokensUpdated 4 mo ago
    Auto-check passed

  • Fabll

    atopile/atopile

    How FabLL (faebryk.core.node) maps Python node/trait declarations into the TypeGraph + instance graph, including field/trait invariants and instantiation patterns.

    4k GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed

  • Faebryk

    atopile/atopile

    How Faebryk's TypeGraph works (GraphView + Zig edges), how to traverse/resolve references, and how FabLL types/traits map onto edge types.

    4k GitHub stars~861 tokensUpdated 4 mo ago
    Auto-check passed

  • Graph

    atopile/atopile

    How the Zig-backed instance graph works (GraphView/NodeReference/EdgeReference), the real Python API surface, and the invariants around allocation, attributes, and cleanup.

    4k GitHub stars~952 tokensUpdated 4 mo ago
    Auto-check passed

Categories

Questions about Atopile Skills

What does Atopile Skills do?

How to write and maintain .claude/skills//SKILL.md files: source-of-truth-first process, verification steps, and conventions. Atopile Skills is an agent skill from atopile/atopile.md files: source-of-truth-first process, verification steps, and conventions.

When should I use Atopile Skills?

Atopile Skills fits situations like: tasks that involve Skill authoring.

How do I install Atopile Skills in Claude Code?

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

How do I install Atopile Skills in Codex?

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

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

What does Atopile Skills need to run?

SKILL.md names no scripts, command-line tools or credentials: Atopile Skills is instructions for the agent only. Our summary lists: Python 3.

Does Atopile Skills access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Atopile Skills 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 Atopile Skills use?

Atopile Skills 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 Atopile Skills use?

About 893 tokens (SKILL.md is roughly 3.6k 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 Atopile Skills?

Skills that share tags, products or a category with Atopile Skills: Skill Creator (Azure/azqr, 796 stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars), Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars) and Claude Code Command Development (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Atopile Skills?

atopile (a GitHub organization) maintains it in atopile/atopile, which has 3,980 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on June 13, 2026.

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