Menu
Skills in this repository
SkillsMP has collected 75 skills from robert-chiniquy/dotfiles. Open a skill to review its source and details.
robert-chiniquy/dotfilesShowing 35 of 75 collected skills.
Create and manage Squire ephemeral development environments for parallel agent work. Use when delegating implementation tasks to remote environments, creating fire-and-forget work sessions, or monitoring parallel agents. Triggers on: squire, ephemeral env,…
Reviewer persona for Server-Side Request Forgery and confused-deputy classes. Covers user-controllable URLs fetched server-side, DNS rebinding, IPv6 / IPv4-mapped sidesteps of allowlists, internal metadata service exposure (AWS/GCP/Azure IMDS), egress to…
Convert output from custom or experimental static analysis tooling into actionable bug fixes. Use when working with novel linters, in-house detectors, or recently-shipped analysis passes whose findings haven't yet been triaged into PRs. Covers detector volume…
Review a prompt about to be sent to a subagent (Agent tool, sqfan dispatch, squire env, scheduled remote agent, MCP-driven worker) for defects that cause silent failure, wasted runs, or runaway scope. Single-axis review: is this prompt fit-to-dispatch? Use…
Tactical situation report scoped to ONE proximate goal with a hard deadline. Pulls real-world signals from multiple nebulous sources (ticketing system + git host + wiki + chat + local tracker) and synthesizes a calibrated A/B/C readiness call, plus the single…
Builds and queries multi-language source code graphs for security analysis. Includes pre-analysis passes for blast radius, taint propagation, privilege boundaries, and entry point enumeration. Use when analyzing call paths, mapping attack surface, finding…
Helps coding agents use vit to discover, follow, skim, and ship software capabilities (caps) over ATProto. Activates when the user mentions vit, beacons, caps, shipping, skimming, following, vetting, or social coding.
Check the progress and liveness of background agent worktrees with one pre-authorized command instead of ad hoc shell. Use when monitoring dispatched background agents, when the user asks for interim status on agent work, when deciding whether an agent is…
Apply a reusable dark, flattering, countercultural image-generation style with underground hacker energy, grungy warehouse texture, ransom-note collage typography, bright focal accents, and spacious post-cyberpunk composition. Use when creating or editing…
Produce a rigorous, adversarially-reviewed RFC (build-plan / design doc) through a multi-phase pipeline — investigate → judges → plan → judges (loop until clean) → owner approval. Stops at the approved RFC; does NOT dispatch implementation agents or open PRs.…
Proactive quality-of-life for the computing environment. Activates when working in dotfiles, shell config, system settings, or when the user mentions friction or inefficiency. Suggests only passive, automatic changes.
Project framework defining mandatory artifacts, practices, and organization. Always active. Defines DATA_SOURCES.md, LEARNINGS.md, GLOSSARY.md, and other project files. Read references/ for details on each topic.
Reviewer persona for authorization models — RBAC, ABAC, ReBAC, and hybrids. Catches the bugs that ship after auth is correct but authz is wrong: missing tenant scoping, IDOR via predictable IDs, role escalation through unchecked write paths, permission…
c1-specific values for the general squire dispatch protocols defined in squire-env-management. Provides the c1 gate bundle's contents, the task-family table for c1 work, the c1 always-actives, and the list of c1 skills that should NOT be spent on a squire…
Reviewer persona for detecting hand-rolled cryptography. Distinct from `sharp-edges` (which catches footgun APIs) and `key-lifecycle-review` (which covers lifecycle hygiene): this skill catches the class where someone wrote their own MAC, KDF, AEAD, signature…
Code comment review persona. Focuses on a single axis: comments must describe what is in the code, not the process of writing it. Strips phase numbers, bead/issue references, "added for X" notes, dogfood/debug history, and other narration that ages poorly.…
Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports.…
Comprehensive Go code review skill for PR reviews, architecture assessment, and test quality analysis. Use when reviewing Go code to ensure adherence to Go best practices, security standards, and project-specific patterns. Applies to full PR reviews, single…
Behavioral dispositions for emotionally and psychologically healthy interaction with the user. Covers honest disagreement, absence of performative warmth, respect for user agency, non-replacement of human connection, and how to respond when the user expresses…
Detects fail-open insecure defaults (hardcoded secrets, weak auth, permissive security) that allow apps to run insecurely in production. Use when auditing security, reviewing config management, or analyzing environment variable handling.
Triage open GitHub pull requests for actionable feedback, unresolved review threads, requested changes, CI or merge blockers, and ready-to-merge links. Use when the user asks for a PR pass, review/mergeability sweep, status check across their open PRs, a…
Functional-analysis protocol for iteratively improving subagent performance. Adapted from Antecedent-Behavior-Consequence (ABC) analysis in applied behavior analysis. Use when delegating to a subagent, when an agent returns a poor result, when a pattern of…
Informal communication for Slack, chat, DMs, and quick check-ins. Conversational, first-person, correct punctuation but relaxed register. Use for Slack messages, informal reviews, and PR descriptions on own repos.
Systematically find problems in a design before building it. Four lenses: unnecessary complexity, missing fundamentals, feasibility gaps, and scope mismatch. Use after creating an implementation plan or when a design feels wrong. Invoked via /critique.
Feature design methodology. Covers research, comparison, requirements refinement, ideation, implementation planning, and DX completeness. Use when starting a new feature, planning a refactor, or designing APIs. Invoked via /design [topic].
Documentation methodology: process, content patterns, templates, verification, organization, and merging. Use when writing docs, planning doc structure, reviewing docs for quality, or merging documentation across sources.
Find uncommitted changes, unpushed commits, unmerged branches, and incomplete code markers (TODO, FIXME, HACK) across repositories. Use at end of day, before context switches, or to audit work in progress.
Multi-phase workspace cleanup. Inventories uncommitted work, switches to main, prunes branches, cleans worktrees. Safe by default. Use for end-of-day cleanup or when a repo is messy.
Safe git-to-PR workflow. Stages changes, runs quality checks, commits with approval, pushes, creates PR. Use when ready to ship code.
Pragmatic architecture judgment. Six-pass analysis for design decisions: what works, what breaks, what ships, what costs, what simplifies, what stays. Use when choosing between approaches or evaluating whether to build something. Invoked via /pqthink.
Initialize a directory with the project framework. Creates DATA_SOURCES.md, LEARNINGS.md, GLOSSARY.md, .claude/CLAUDE.md, .envrc with accent color. Usage: /project-init [topic]
Protobuf and gRPC architecture patterns. Use when working with .proto files, protoc plugins, gRPC services, or code generation pipelines. Read references/ for schema design, database mapping, and testing.
Guide architecture toward compile-time safety over runtime checks. Use when designing subsystems, reviewing architecture, or choosing between runtime and compile-time enforcement. Covers type systems, enums, interfaces.
Long-form technical writing voice for blog posts, deep dives, architecture explanations, and talks. Use when writing articles, READMEs with narrative, or any content for external audiences beyond the team.
Terraform and OpenTofu patterns: modules, native tests, CI/CD, security. Use when creating modules, writing tests, reviewing HCL, debugging state, or setting up infrastructure pipelines. Read references/ for deep content.