Files
skills-public/README.md
T
BluscreamandClaude Opus 5 72834167b6 feat(cli-tooling): add generic CLI, tooling and script-placement rules
Extracted from the per-agent profile files and the private ai-agents skill,
where they were duplicated and environment-coupled:

- discovery over guessing: walk the help tree, never invent flags, never
  hand-roll a script when a dedicated CLI exists
- non-interactive invocation: explicit targets, the tool's own --wait
- machine-readable output flags (json/compact/csv) vs. never filtering
  diagnostics
- orient before starting: project instructions, git log, prior work records,
  and verifying TODOs against the code
- script placement: dedicated version-controlled dir, symlinked into PATH
- destructive/outward-facing command care; environment drift verification

coding-dev.md and code-languages/bash.md now cross-reference it instead of
carrying their own one-line versions.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-18 12:40:55 +02:00

3.8 KiB

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.

🔤 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:

  1. YAML frontmatter with name (kebab-case, matching the filename) and a description starting with "Use this skill when …" — the description is what an agent matches against to decide relevance, so it must enumerate concrete triggers.
  2. Numbered ## sections, sequential and unique, ending with a Related Skills section that cross-links sibling documents.
  3. CLI discovery over enumeration — document the non-obvious workflows, gotchas, and constraints. For the routine surface, point at <tool> --help rather than transcribing flag lists that will go stale.
  4. No secrets inline — reference the environment file that holds them (e.g. ~/.config/environment.d/…), never the values themselves.
  5. 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.