Showing 42571–42600 of 42726 skills
Audit and converge README.md across every local urmzd/* checkout so the fleet reads as one product: skip archived repos, flag renamed repos and stale identities, score each README against write-readme, then fix in priority order. Use when the user asks to consolidate, unify, standardize, or audit READMEs across repos, or after a rename wave. Do NOT use for a single repo's README (use write-readme), prose cleanup alone (use clean-docs), or whole-repo convention drift (use sync-ecosystem).
urmzd/dotfiles
Write or rewrite text in ASD-STE100 Simplified Technical English (STE): the approved-word dictionary discipline, controlled verb forms, sentence and paragraph limits, procedural vs descriptive rules, and safety-instruction structure. Use when the user asks for Simplified Technical English, STE, ASD-STE100, controlled language, or aerospace-style technical writing, or when authoring procedures, maintenance instructions, or safety warnings that must be unambiguous. Do NOT use for general documentation cleanup (use clean-docs), README structure (use write-readme), or ordinary prose style.
urmzd/dotfiles
Foundational quality framework: the five questions (readable, easy to start, expands without bloat, consistent, intentional) every other dev skill is judged against, plus the dual-audience and workshop principles. Use when onboarding to a project, defining a quality bar, setting an assessment checklist, or arbitrating between review-design and write-code. Do NOT use for the design "why" layer (use review-design) or concrete tool/pattern picks (use write-code). For day-to-day "review my staged/unstaged changes" asks, use review-diff instead.
urmzd/dotfiles
Scans a repo and host for leaked keys and secrets (gitleaks, trufflehog), audits SSH/GPG/.env file permissions, checks git hygiene, investigates suspicious processes and listeners, and hardens config (FileVault, firewall, SIP, SSH). Use when auditing for leaked credentials or secrets, checking for security issues before a commit, investigating an unknown process or open port, or hardening a machine. Do NOT use for storing, injecting, or rotating secrets at rest (1Password, op read, vaults) -> use manage-secrets; this skill only detects and reports exposure.
urmzd/dotfiles
Design and audit CLI tools end-to-end: output modes, TTY detection, JSON piping, stderr/stdout separation, color/symbol semantics, the ui module pattern, signal handling, exit codes, and install.sh. Use when building, reviewing, or releasing any CLI and you need general CLI design guidance. Do NOT use for the mandatory urmzd/* portfolio CLI rules (argument-parser choice, self-update requirement, --format flag, global flags, install.sh template): cli-standards owns those and overrides this skill where they conflict.
urmzd/dotfiles
Validate project structure against scaffold conventions -- check for required files, CI consistency, documentation completeness, sub-package/workspace members, and optional directory usage, reporting PASS/WARN/FAIL with fix suggestions. Use to audit an existing project or verify a scaffold was applied correctly. Do NOT use to create or modify project files; this is a read-only auditor (use the scaffold-* skills to generate structure).
urmzd/dotfiles
Canonical tech-stack reference organized by purpose: release/versioning (sr), docs/demos (teasr, fsrc), codegen (oag), and per-language tools (cargo, clippy, clap, golangci-lint, biome, tsdown, uv, ruff, ty, pytest, pydantic, fastapi). Use when choosing a library, picking the standard CLI/linter/logging tool for a language, setting up a project, or asking "what do we use for X." Do NOT use for coding patterns or error-handling idioms (use write-code) or testing frameworks in depth (use test-code).
urmzd/dotfiles
Clean and modernize documentation in place. Enforce no em dashes, readable structure, proper Markdown formatting, accurate commands, current examples, resolved internal links, and user-focused guidance. Use when the user invokes /clean-docs, asks to clean docs, make docs up to date, improve README/AGENTS prose, remove AI-looking punctuation, or make docs easier for users to act on.
urmzd/dotfiles
Scaffold the GitHub Community Standards files (CODE_OF_CONDUCT, SECURITY, ISSUE_TEMPLATE, pull_request_template) using $COMMUNITY_HEALTH_CONTACT or git config user.email as the contact. Use when bootstrapping a new repo or backfilling community-health coverage.
urmzd/dotfiles
Authors AGENTS.md and defines the skills-vs-docs boundary for a repo. Configures AI coding tools (Claude Code, Codex, Antigravity CLI, Copilot) and the skills-as-docs philosophy. Use when creating or auditing AGENTS.md, setting up AI tooling for a project, or deciding what belongs in a skill versus docs/. Do NOT use for README structure -> use write-readme; for llms.txt generation -> use create-llms-txt; for Claude-specific skill features (invocation control, subagents, model overrides) -> use extend-oss-skills-to-claude.
urmzd/dotfiles
Generate a spec-compliant llms.txt file for any project by analyzing its codebase, docs, and public URLs. Use when creating an llms.txt, making a project LLM-discoverable, or when the user mentions "llms.txt" in the context of generating or scaffolding one.
urmzd/dotfiles
Create well-formed Agent Skills following the agentskills.io specification. Scaffold directories, write SKILL.md files, bundle scripts, and structure instructions for progressive disclosure. Use when creating a new skill, reviewing skill structure, optimizing a skill description, or setting up evals for skill quality.
urmzd/dotfiles
Investigate failing REMOTE CI runs on GitHub Actions: find the failed run, pull the failed-step logs with gh, identify the root cause (compile error, test failure, lint, missing secret, timeout), and recommend a fix. Read-only: it does not commit, push, or edit. Use when CI is red, a GitHub Actions run failed, or the user asks "why did the pipeline fail". Do NOT use for local build/test/runtime failures on your machine (use diagnose-runtime); do NOT apply the fix and re-ship (use fix-and-retry) -- this skill investigates and recommends only.
urmzd/dotfiles
Triage LOCAL runtime failures on your own machine: crashes and errors, hangs and deadlocks, slowness and high CPU/memory, and hardware/serial/USB issues. Method: reproduce, isolate (bisect, log, strace/dtruss, sample), form a hypothesis, verify the fix holds. Read-mostly: it inspects processes and logs, it does not commit, push, or edit source. Use when the user asks "why does this error", "why does the system hang after generating the PDF", "why is the computer running hot", "why is image loading slow", or "this process is stuck". Do NOT use for CI/pipeline failures (use diagnose-ci) or for applying and re-shipping a fix (use fix-and-retry) -- this skill investigates and recommends only.
urmzd/dotfiles
Chezmoi dotfiles conventions and patterns. Use when modifying dotfiles, adding new managed files, working with chezmoi templates, or syncing agent skills and subagents through agentspec. Do NOT use for installing tools, running doctor, or updating a machine through the `dotfiles` CLI; use manage-machine.
urmzd/dotfiles
Extend standard agentskills.io skills with Claude Code-specific features. Invocation control, subagent execution, dynamic context injection, string substitutions, model/effort overrides, and deployment scoping. Use when adapting a portable skill for Claude Code, adding Claude-specific frontmatter, setting up subagent delegation, or configuring skill permissions.
urmzd/dotfiles
Diagnose a failing CI run, apply the code fix, commit it, push, and watch the re-run until it passes or fails -- the full fix-and-retry loop in one shot. Use after a pipeline fails and the user says "fix it and retry", "fix the CI and push", or "make CI green". Do NOT use for a read-only investigation that stops at a recommendation (use diagnose-ci); do NOT use for a routine commit unrelated to a CI failure (use ship).
urmzd/dotfiles
Operate a machine set up by urmzd/dotfiles through its `dotfiles` CLI: install or remove optional tools from the package catalog, diagnose a broken setup with `dotfiles doctor`, update the CLI, dotfiles, or packages, and add company tools to a pack's catalog.toml, and stack packs (company, team, role overlays). Use when the user says "install linear", "remove discord", "what can I install", "why is python broken", "update everything", "add our VPN for everyone at work", "add the backend-engineer pack", or "is this machine healthy". Do NOT use for editing the chezmoi source repo itself (templates, run_ scripts, naming; use dotfiles), for a project's own toolchain or .envrc (use setup-devenv), for colors and themes (use manage-theme), or for a known shell/nvim/gpg error signature (use triage-dotfiles-env).
urmzd/dotfiles
1Password-based secret storage workflow: vault layout, 1p:// references in .envrc, op run for local execution. Use when storing or rotating credentials with 1Password. (Other backends not covered.)
urmzd/dotfiles
Switch, create, or debug the color theme of a machine set up by urmzd/dotfiles: one theme colors Ghostty, Neovim (colorscheme and lualine), tmux (catppuccin flavour and colors), and the dotfiles' own output. Covers `dotfiles theme` / `dotfiles theme set`, writing a themes/<name>.toml or a pack's theme.toml, and per-shell output overrides (DOTFILES_UI_*). Use when the user says "switch to tokyonight", "change my terminal colors", "make a theme for our team", "my nvim colors did not change", or "use ASCII output in CI". Do NOT use for a project's brand identity, fonts, or demo capture (use style-brand), for installing apps or other machine upkeep (use manage-machine), or for editing unrelated chezmoi templates (use dotfiles).
urmzd/dotfiles
Drive an existing pull request to a mergeable state: get CI green, resolve merge conflicts with the base branch, address and resolve review comments, trigger required bot reviews/approvals (e.g. commenting '@claude review'), link associated issues, and clean up the PR title and description. Ends with a readiness report listing any remaining human-only blockers (required reviewer approvals, CODEOWNERS). Uses the CLI matching the repo's forge: gh for GitHub, glab for GitLab merge requests, tea for Gitea/Forgejo. Use when the user says "get this PR ready to merge", "make this PR mergeable", "get the PR green", "address the review comments", "babysit this PR", "get this MR merged", or "why is this PR blocked". Do NOT merge the PR or enable auto-merge; do NOT open a new PR (use pr); do NOT use for a failing pipeline with no PR context (use fix-and-retry / diagnose-ci).
urmzd/dotfiles
Orchestrate multiple agent CLIs (Claude, Codex, Antigravity) via tmux with a shared fleet store, dispatching one guardian subagent per pane. Survey-first: inspects and adopts existing tmux sessions, windows, and agent panes before creating anything new. Use when running a multi-agent session, dispatching parallel work, or coordinating subagents across panes.
urmzd/dotfiles
Open a pull request via gh pr create with a reviewer-ready body: What, Why, How, Verification with real evidence, and a Demo (screenshot, GIF, terminal capture, or plan output). Follows the repo's pull_request_template.md when one exists. Use when the user says "create a pull request", "open a PR", "gh pr create", "raise a PR", or "make a PR for this branch", and whenever an agent opens a PR as part of a larger task. Also use to rewrite the body of a thin existing PR (gh pr edit). Assumes commits already exist and only opens the PR. Do NOT commit changes or watch CI (use ship); do NOT diagnose or fix a failing pipeline (use fix-and-retry / diagnose-ci).
urmzd/dotfiles
Publish notes from an Obsidian vault folder into another folder (usually a repo's content directory) by one-way mirroring top-level Markdown files (add, update, remove). Discovers vaults and likely targets, asks the user where to publish from and to, previews, then mirrors with a bundled script. Use when the user says "publish the blog", "sync the vault to the repo", "push my Obsidian posts", or "publish-vault". Do NOT commit or push (use ship); do NOT edit note content.
urmzd/dotfiles
Audit GitHub releases, git tags, and release assets for one repo or every repo in a directory. Flags orphaned tags, missing binaries/checksums, draft releases, floating tag drift, pre-release remnants, and (when sr.yaml is present) sr config issues. Read-only: never deletes or modifies tags/releases. Use when checking "release health", "orphaned tags", "missing assets", "draft releases stuck", or "is sr.yaml configured right". Do NOT use to cut or publish a release, and do NOT use to set up the release pipeline -- this only audits and reports.
urmzd/dotfiles
End-to-end repo bootstrap: creates the GitHub repo (gh repo create), adds an Apache-2.0 LICENSE, dispatches to scaffold-project for CI/release/config, invokes community-health, writes a README, sets topics/description, and makes the initial commit and push. Use when starting a brand-new project from zero and you need the GitHub repo, metadata, and first push handled, not just local files. Do NOT use to scaffold files inside an existing repo; invoke scaffold-project directly for that.
urmzd/dotfiles
Scan a folder of git repos and report each repo's local dirty/clean state, ahead/behind divergence from upstream, recent activity, and latest CI run status. Read-only: never commits, pushes, or edits. Defaults to the folder argument or your repo root. Use when checking "what's live", "which repos are dirty", or "repo status across my projects". Sibling skills overlap on folder scanning: do NOT use for "what should I work on next" prioritization (use get-work); do NOT use for a recent-activity-only overview without dirty/CI detail (use status). repo-status is the local dirty/ahead/behind + CI-state report.
urmzd/dotfiles
Pragmatic Programmer principles: DRY, orthogonality, ETC, reversibility, tracer bullets, design by contract, decoupling/Law of Demeter, pragmatic paranoia. The 'why' layer between assess-quality (framework) and write-code (operational). Use when reasoning about design tradeoffs, coupling, or whether a decision is reversible. Do NOT use for the underlying quality framework (use assess-quality) or for concrete tool/idiom/library picks (use write-code).
urmzd/dotfiles
Standardized review of the CURRENT working-tree changes -- staged, unstaged, and untracked -- against an explicit five-dimension rubric (correctness, security, tests, scope-creep, conventions). Emits a prioritized findings list, each with file:line, severity, and a suggested fix. Read-only: it reviews and reports, it does not commit, push, or edit. Use when the user says "review my changes", "review the diff", "look over my staged changes before I commit", or "what's wrong with this PR locally". Do NOT use for red CI/pipeline failures (use diagnose-ci) or whole-repo quality-framework questions (use assess-quality); this reviews the working-tree diff only. assess-quality and review-design both EXCLUDE day-to-day review and name this skill as its home.
urmzd/dotfiles
Run a project's own eval suite end to end without babysitting: locate the harness, launch it in the background, monitor to completion, parse the report into a normalized summary (pass rate, latency percentiles, tokens, cost), and diff against the previous run with per-case regressions explained. Use when asked to "run the evals", re-run after a change, or score a new dataset in any repo with an eval harness. Do NOT use for the GAP benchmark suite (use run-evals), SAIGE provider-boundary checks (use verify), or designing new eval sets (that is authoring work, not a run).
urmzd/dotfiles