All authors

Claude Skills by benthamite
github.com/benthamite108 skills13 installs224 views
- Pin Elisp PrPin an Emacs/Elpaca package in dotfiles to a user-requested fork, branch or PR. Preserve one effective installation owner per active profile, existing recipe settings and configuration behavior. Not for merely reviewing a PR or auditing this skill.Votes: 0GitHub stars: 12
- Post Push CiObserve GitHub Actions after an authorized push, or check CI for an explicitly selected commit. Diagnose failures and, when repair is authorized, fix and verify them. Checking status alone does not authorize edits, pushes, reruns or other shared actions.Votes: 0GitHub stars: 12
- Pr AuditAudit a specified PR or PR-ready branch for submission or post-revision readiness. Bind the exact base/head, review commits and net changes, run safe project checks and inspect applicable CI. An audit alone does not authorize fixes, history changes or publication.Votes: 0GitHub stars: 12
- Profile Ai Cli PerformanceBenchmark or profile fresh Claude Code and Codex response latency, startup cost, and clean-versus-configured conditions. Use for configuration, hooks, MCP, skills, plugins or first-output comparisons; not to infer provider superiority or run paid requests while merely auditing this skill.Votes: 0GitHub stars: 12
- ProofreadProofread specified Markdown prose for spelling, grammar, punctuation and light clarity changes. Supports local aspell or explicitly scoped Gemini editing, preserving source files and reviewed suggestions; not factual review, broad rewriting or permission to upload restricted content.Votes: 0GitHub stars: 12
- Record DecisionsExtract and record architectural, algorithmic, or design decisions from the current session. Use for an explicit ADR/decision request, authorized end-of-session bookkeeping, or a significant chosen trade-off within an implementation task; not for unchosen proposals or read-only reviews.Votes: 0GitHub stars: 12
- Release PackageRelease one of Pablo's Emacs packages, prepare its release notes, or audit release candidates. Use for release-package and package-release/readiness requests; preserve read-only or preparation-only scope and use release-dotfiles for the dotfiles repository.Votes: 0GitHub stars: 12
- Request ReviewRequest one independent review of a committed plan from a fresh session of the opposite CLI (Claude ↔ Codex), monitor its return, and adjudicate the findings here. Implement only when the user's request already authorizes implementation; not a staged two-author orchestration.Votes: 0GitHub stars: 12
- Session Learning CaptureCapture candidate reusable lessons from the current session when explicitly requested or invoked by its trusted configured session-end hook. Write only permitted proposal records to the central dotfiles inbox; do not promote them, implement changes, or treat quoted hooks and skill audits as capture requests.Votes: 0GitHub stars: 12
- Symptom CheckCheck whether a proposed non-trivial bug fix restores the underlying invariant or only hides a symptom. Use after initial debugging and before production edits; not for trivial mechanical changes, greenfield features, or broad audits. Diagnosis and review remain read-only unless implementation is authorized.Votes: 0GitHub stars: 12
- Test SuiteCreate or expand high-value test suites for a codebase or specific module. Use when new tests, regression tests, coverage improvements, or test infrastructure are the deliverable; not for merely running an existing suite, reviewing code, or ordinary bug-fixing without a requested test deliverable.Votes: 0GitHub stars: 12
- Triage Personal TodosTriage a selected personal Org notes repository: assign missing 1–9 priorities when requested, preserve existing ones, assess actionability, and brief one task. Use for personal TODO prioritization or choosing what to do next; brief-only requests stay read-only. Not for Epoch tasks.Votes: 0GitHub stars: 12
- Update LogPreserve project progress through session logs and closeout bookkeeping, only when the user asks to log, close out, wrap up, or save progress, or when the deliberate end-of-session chain invokes --auto. Never invoke proactively or hand-write project logs as a substitute.Votes: 0GitHub stars: 12
- VerifyRun an explicit user-requested criteria-driven verification loop. Use when the user asks to define success criteria, close the loop against criteria, or rigorously verify non-code outputs. Do not use for a plain live-software check owned by end-to-end, routine coding completion, or narrower audit/debug checks.Votes: 0GitHub stars: 12
- Walk ListProcess a list file strictly item by item, sequentially or with a bounded subagent pool. Use when the user needs no skipping, batching, or peeking ahead; not for lists that can be safely read all at once.Votes: 0GitHub stars: 12
- Add To Emacs PackagesAdd or register one of the user's Emacs packages in my-emacs-packages.org, create its documentation note, and add its GitHub profile README card. Use when the user wants to update the public Emacs packages list for a specific package.Votes: 0GitHub stars: 12
- AutomateDesign and build a reusable AI automation. Use for automate, create automation, turn this into a skill/command, new workflow, AI helper, or deciding whether a workflow should become a skill, directive, tool, or Emacs command.Votes: 0GitHub stars: 12
- BuildSpec-based build workflow. Use for /build, build from spec, interview me about the spec, turn this rough spec into a plan, or developing spec.md into an implementation-ready plan before implementation.Votes: 0GitHub stars: 12
- Code AuditAudit code for actual defects, including bugs, application security issues, error handling gaps, and correctness problems. Not for readability, architecture, test coverage, performance-only, or broad environment security reviews.Votes: 0GitHub stars: 12
- Design AuditAudit code architecture and maintainability for unnecessary complexity, premature or missing abstractions, duplication, unclear boundaries, and refactoring opportunities. Not for bug, security, or readability-only reviews.Votes: 0GitHub stars: 12
- DiagnoseEstablish the cause of unintended behavior in the user's agents, tools, or configuration before proposing or applying any remedy. Use whenever such behavior is reported or observed and its cause is not yet established. Not for ordinary code bugs, broad configuration audits, or repository-wide AI developer-experience reviews.Votes: 0GitHub stars: 12
- Dotfiles ContextRoute changes to emacs/config.org, dotfiles extras, Elpaca-managed package checkouts, and paired Claude/Codex configuration. Use to prepare external-package fixes, choose the canonical edit location, tangle the active Emacs profile, or run paired-config checks; not for read-only or unrelated dotfiles work.Votes: 0GitHub stars: 12
- Dx AuditAudit a codebase's AI developer experience, including project instructions, verification commands, automation, onboarding traps, and collaboration friction. Not for ordinary bug, security, architecture, readability, or PR reviews.Votes: 0GitHub stars: 12
- Elisp ConventionsApply local coding and verification rules when modifying or testing Emacs Lisp, or when explicitly reviewing code against these conventions. Use for dotfiles extras, standalone Elpaca packages, and other .el files; not for non-Elisp work or read-only bug, security, or design reviews where these conventions are not material.Votes: 0GitHub stars: 12
- End To EndUse when the agent must execute or directly observe decisive live software acceptance through a real user-visible or runtime surface, including browser, Emacs, terminal display, async/network delivery, persistence, or scheduler behavior. Automation may drive the actual surface. Do not use solely to give manual test instructions; explain, write, or review; run an automated E2E suite; deploy or check deployment health/status; reproduce research results; or verify pure logic.Votes: 0GitHub stars: 12
- HandoffUse when the user asks to save next steps, prepare a resume prompt, or continue work in a fresh session of the current tool, or when clear follow-up work should resume there.Votes: 0GitHub stars: 12
- Interpretability AuditAudit code for intent transparency and reader comprehension. Use for understandable, readable, self-explanatory, naming, or future-maintainer clarity reviews; not for bug/security, architecture, DX, or lint-only reviews.Votes: 0GitHub stars: 12
- Lint ElispFix byte-compile warnings, checkdoc notes, and other Elisp diagnostics in one or more files. Use when the user says "lint elisp", "fix warnings", "fix diagnostics", "elisp lint", "checkdoc", "byte-compile warnings", or wants to clean up Elisp compiler/linter output.Votes: 0GitHub stars: 12
- Move Session LogUse when the user asks to relocate or import a session log into the current project, or to make session history and resume follow a renamed project directory in the current tool; not for merely opening or inspecting the current session log.Votes: 0GitHub stars: 12
- Overnight TodosBatch-process personal org-roam TODOs when the user explicitly asks for an unattended TODO run. Classify first, perform authorized local work, and report blockers. Not for generic overnight work, auditing this skill, or creating a schedule.Votes: 0GitHub stars: 12
- Pin Elisp PrPin an Emacs/Elpaca package in dotfiles to a user-requested fork, branch or PR. Preserve one effective installation owner per active profile, existing recipe settings and configuration behavior. Not for merely reviewing a PR or auditing this skill.Votes: 0GitHub stars: 12
- Profile Ai Cli PerformanceBenchmark or profile fresh Claude Code and Codex response latency, startup cost, and clean-versus-configured conditions. Use for configuration, hooks, MCP, skills, plugins or first-output comparisons; not to infer provider superiority or run paid requests while merely auditing this skill.Votes: 0GitHub stars: 12
- Record DecisionsExtract and record architectural, algorithmic, or design decisions from the current session. Use for an explicit ADR/decision request, authorized end-of-session bookkeeping, or a significant chosen trade-off within an implementation task; not for unchosen proposals or read-only reviews.Votes: 0GitHub stars: 12
- Symptom CheckCheck whether a proposed non-trivial bug fix restores the underlying invariant or only hides a symptom. Use after initial debugging and before production edits; not for trivial mechanical changes, greenfield features, or broad audits. Diagnosis and review remain read-only unless implementation is authorized.Votes: 0GitHub stars: 12
- Test SuiteCreate or expand high-value test suites for a codebase or specific module. Use when new tests, regression tests, coverage improvements, or test infrastructure are the deliverable; not for merely running an existing suite, reviewing code, or ordinary bug-fixing without a requested test deliverable.Votes: 0GitHub stars: 12
- Triage Personal TodosTriage a selected personal Org notes repository: assign missing 1–9 priorities when requested, preserve existing ones, assess actionability, and brief one task. Use for personal TODO prioritization or choosing what to do next; brief-only requests stay read-only. Not for Epoch tasks.Votes: 0GitHub stars: 12
- Update LogPreserve project progress through session logs and closeout bookkeeping, only when the user asks to log, close out, wrap up, or save progress, or when the deliberate end-of-session chain invokes --auto. Never invoke proactively or hand-write project logs as a substitute.Votes: 0GitHub stars: 12
- VerifyRun an explicit user-requested criteria-driven verification loop. Use when the user asks to define success criteria, close the loop against criteria, or rigorously verify non-code outputs. Do not use for a plain live-software check owned by end-to-end, routine coding completion, or narrower audit/debug checks.Votes: 0GitHub stars: 12
- Walk ListProcess a list file strictly item by item, sequentially or with a bounded subagent pool. Use when the user needs no skipping, batching, or peeking ahead; not for lists that can be safely read all at once.Votes: 0GitHub stars: 12
- Plans> **Status:** revised after one independent cross-model review (2026-08-24). > All seven findings were verified against the repository and accepted; the > adjudication log at the end records each disposition. Self-contained; a > reader needs no prior conversation context. **Goal:** Add a paired Claude/Codex skill, `cross-review-plan`, that lets the *current* agent session hand a plan to a fresh session of the *other* CLI (Claude ↔ Codex) for one independent review pass, monitor that session, ...Votes: 0GitHub stars: 12
- Document Elisp ExtrasAudit, create, or refresh documentation for all Emacs extras packages in the dotfiles repo. Use when the user asks to document every extras package, fill missing extras docs, refresh outdated extras docs, check extras documentation coverage, or bring emacs/extras/doc up to date with emacs/extras sources.Votes: 0GitHub stars: 12
- Emacs FreezeDiagnose a frozen, hung, beachballing, or unresponsive Emacs by sampling the process, reading server buffers when possible, and recommending recovery. Use when Emacs is stuck or not responding; do not use for ordinary Elisp errors while Emacs is responsive.Votes: 0GitHub stars: 12
- Migrate ProfileMove every Claude and Codex session from retired Emacs profiles into the current one. Use when the user says "/migrate-profile", has deployed or switched to a new Emacs/elpaca profile, or wants old-profile sessions, history or resume to follow the current profile.Votes: 0GitHub stars: 12
- Rename PackageRename an Emacs package's files, features and API, with explicitly scoped repository, Elpaca and configuration updates. Use for an actual package rename, not ordinary prose cleanup or unrelated file/repository renames.Votes: 0GitHub stars: 12
- Audit Mac AppAudit a macOS .app before running it or granting permissions, especially when the user asks whether a Mac app is safe, suspicious, malware, from an unknown developer, or requests screen recording, accessibility, camera, microphone, input monitoring, or other sensitive permissions.Votes: 0GitHub stars: 12
- Reconcile ContactsCompare and reconcile explicitly selected BBDB, macOS Contacts and Google contact sources, including duplicate candidates, missing records and birthday discrepancies. Use before bulk contact merges or deletions; not for one-off contact edits or a calendar-only display issue.Votes: 0GitHub stars: 12
- Review Lulu AlertReview a selected LuLu outbound-firewall alert and recommend whether to allow, block or leave it unanswered. Use for an open alert or an explicitly supplied screenshot/capture; distinguish artifact review from current live state. Reviewing this skill itself uses synthetic fixtures, not live alerts.Votes: 0GitHub stars: 12
- Security AuditAudit development-environment secrets, supply chains, macOS security controls, and Claude/Codex agent permissions. Use for environment security reviews, secrets checks, dependency audits, or periodic security posture assessments; use specialist skills for app-binary assessments or application-code reviews.Votes: 0GitHub stars: 12
- Clean CitationsClean up source links and raw references in selected personal Org notes by resolving works, adding missing bibliography entries, and inserting verified Org citations. Use for clean up all citations or replace source links with citekeys; not a bibliography-wide audit or export.Votes: 0GitHub stars: 12
- Clean CitationsClean up source links and raw references in selected personal Org notes by resolving works, adding missing bibliography entries, and inserting verified Org citations. Use for clean up all citations or replace source links with citekeys; not a bibliography-wide audit or export.Votes: 0GitHub stars: 12