Public Agent Skills
A collection of public, reusable agent skills, cheatsheets, and operational workflows for AI coding assistants and automation agents.
📂 Skills Index
| Skill File | Scope / Topics Covered |
|---|---|
coding-dev.md |
Standing rules for all code work: maximum linter/compiler strictness, never filtering build output, reuse-before-reinvent dependency ordering, file/function size limits, test & regression discipline, verification gates, scope control, commit hygiene, and honest reporting. |
cli-tooling.md |
Using command-line tools correctly: reading the help tree instead of guessing flags, preferring an existing CLI over an ad-hoc script, non-interactive invocation, machine-readable output formats, orienting on prior work before starting, script placement & symlinking, and care around destructive commands. |
afk-sleep-work.md |
Operating unattended and autonomously: continuous forward momentum, avoiding polling traps and deadlocks, host preservation and resource budgeting (disk, packages, processes), isolated tool provisioning, avoiding "last breath" traps on token/quota exhaustion, bypassing or driving GUI launchers, and wake-up checkpoints. |
🔤 Per-Language Rules (code-languages/)
| Language | Skill File | Highlights |
|---|---|---|
| Rust | rust.md |
--workspace clippy gate, [workspace.lints] single source of truth, no unwrap/unsafe, core-crate split |
| TypeScript / JavaScript | js-typescript.md |
TS > JSDoc > plain JS, banned constructs table, React & hooks rules, resource lifecycle, sandbox boundaries |
| Bash / Shell | bash.md |
set -euo pipefail, shellcheck, no wait loops, destructive-command guards, build-gate structure |
| Python | python.md |
mypy --strict, broad ruff rule set, asyncio task discipline, rate-limit queueing |
| Go | go.md |
strict golangci-lint set, concrete types over interface{}, context everywhere, CGO-free static builds |
| C# / .NET | csharp-dotnet.md |
TreatWarningsAsErrors, nullable enabled, no .Result, trimming/single-file publish caveats, SDK shims |
| C / C++ | c-cpp.md |
full warning set + -Werror, sanitizers, RAII/Rule of Zero, target-based CMake, FFI ownership |
Each language file extends coding-dev.md rather than repeating it. A project's own
AGENTS.md / CLAUDE.md / .rules always overrides both.
✍️ Skill Document Conventions
Skills in this repo follow the same structure as the private counterpart repo, so agents can load either interchangeably:
- YAML frontmatter with
name(kebab-case, matching the filename) and adescriptionstarting with "Use this skill when …" — the description is what an agent matches against to decide relevance, so it must enumerate concrete triggers. - Numbered
##sections, sequential and unique. - Cross-link inline, at the point the other skill becomes relevant — never in a trailing "Related Skills" list. A link inside the sentence that raises the topic gets followed; a list at the bottom of a long document does not, and it drifts out of sync with the body.
- One home per fact. Content that belongs to another skill is replaced by a link to it, not duplicated. Where a skill needs its own specific values for something another skill owns the rules for (a container's own template fields, say), keep only the values and link out for the rules.
- Link between skills as
<repo>/<relative path>— e.g.[`cli-tooling.md`](skills-public/cli-tooling.md)or[`network.md`](skills-private/network.md). Links resolve from the shared parent directory holding both repos, so the same spelling works from either repo and from any subdirectory. Never./,../, or absolutefile://paths. The sole exception is the per-agent profile files, which state each repository root once in full, since they are loaded as global instructions with no implied working directory. - CLI discovery over enumeration — document the non-obvious workflows, gotchas, and constraints. For the routine surface, point at
<tool> --helprather than transcribing flag lists that will go stale. - No secrets inline — reference the environment file that holds them (e.g.
~/.config/environment.d/…), never the values themselves. - Verify before documenting — confirm hostnames, container names, and versions against the live system rather than carrying forward stale claims.
🛠️ Usage Across AI Agents & Tools
These skill documents are compatible across agentic developer assistants and environments:
- Claude Code / Claude Desktop: Symlink or reference in project instructions or memory.
- Codex: Include in workspace instructions or agent configuration.
- Antigravity: Mount or reference from workspace
.agents/skills/or global~/.gemini/config/skills/. - Other AI Tools (Cursor, OpenCode, Aider, Devin): Include as persistent project rules or context files.