Unique DivineMY PUBLIC TOOLBOX
Agent skills.
Less repeating myself.
The instructions and references I give AI agents for work I do often: reviewing code, investigating systems, querying chains, and writing clearly.
GET STARTED
Add a skill. Give it a task.
Each skill bundles a workflow with the references an agent needs. Use the installer to choose your agent and the skills you want.
Install one from its page, or browse the collection with this command. Some workflows also need their own CLI tools or service access; check the skill’s instructions.
npx skills add https://github.com/Unique-Divine/jiyuu The collection
22 skills
- SKILL
bash-defensive-patterns
Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.
- SKILL
drill-spec
Interview the user relentlessly about a plan, spec, or design until reaching shared understanding, resolving each branch of the decision tree. Ask up to five direct questions per turn; ask fewer only when one answer blocks the next useful question. Use when user wants to stress-test a plan, get grilled on their design, or mentions "drill the spec" or "drill the plan".
- SKILL
evm-rpc
Query EVM JSON-RPC methods for transaction debugging and endpoint triage, including eth_getTransactionReceipt and debug_traceTransaction. Use when the user asks to inspect tx status, retrieve receipts, run tracers, compare EVM vs Cosmos outcomes, or choose between EVM RPC and Comet RPC endpoints.
- SKILL
gh-actionlint
Validate GitHub Actions workflow YAML with actionlint when editing files under `.github/workflows/`, checking CI workflow syntax, diagnosing GitHub Actions expression or schema errors, or when the user asks to lint/check Actions workflows. Prefer `bunx github-actionlint` when `bun` is available and fall back to `npx --yes github-actionlint`; use this proactively after modifying GitHub Actions workflows.
- SKILL
gh-ci-watch
Watch GitHub PR checks with gh, poll until green/failure/timeout, fetch failed GitHub Actions logs, save logs locally, summarize actionable CI failures, and apply trivial local fixes when safe. Use when the user asks to watch PR checks, wait for CI, inspect failed actions, fix obvious CI failures, or summarize gh pr checks results.
- SKILL
gh-labels
Reference for what GitHub issue/PR labels mean in this workspace (S-triage, S-needs-scope, S-impl, prio-p0-critical, A-ext-dev-tools, A-perf, A-ux, and others under My Labels). Use when the user asks what a label means, which label to apply, or how to add missing labels to a repo. Secondary: bootstrap labels on a new repo that does not have them yet.
- SKILL
gh-pr
Writes clear pull request descriptions from the current branch diff against a base branch. Defaults to `main`, but supports `dev` or any other user-specified comparison branch. Use when the user asks for a PR description, pull request summary, or a markdown write-up for changes against a base branch.
- SKILL
gh-pr-review
Review GitHub pull requests for correctness, design quality, test coverage, security, performance, and backward compatibility. Use when reviewing PRs, when asked to review code changes, or when the user mentions "review PR", "code review", or "check this PR".
- SKILL
gh-rev
Use the gh-rev CLI to maintain a persistent Markdown review ledger for local branches and pull requests. Trigger when the user names gh-rev, asks to save or submit a durable review, inspect or implement existing findings, continue an independent review pass, or adopt branch history into a PR. Use the gh-pr-review skill for review content and judgment. Do not use this skill for a one-off review without a durable ledger.
- SKILL
herdr
Control or customize Herdr, a terminal multiplexer for coding agents. Use when the user explicitly mentions Herdr, asks about its local configuration or source, or asks to inspect or control panes, tabs, workspaces, commands, or another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Live session access requires HERDR_ENV=1; local config, docs, source, and CLI help inspection do not.
- SKILL
just
Prefer the nearest relevant `justfile` as the default command surface for build, test, lint, format, run, deploy, and repo automation workflows. Use when a repo or subproject has a `justfile`, or when the user mentions `just`, `justfile`, recipes, or Makefile-to-just migration.
- SKILL
md-tasks
Apply consistent Markdown checkbox task conventions in READMEs, epics/journals, specs, and design docs. Use when the user wants task lists with "- [ ]" / "- [x]", nested subtasks, context sub-bullets under items, or terminal commands (grep/rg) to list open versus completed tasks in Markdown files — especially in repo documentation and planning Markdown.
- SKILL
new-chat-prompt
Writes a ready-to-paste prompt for a fresh chat instead of completing the requested task directly. Use when the user asks to start a new chat, move work to a new chat, or says to write a prompt for tackling the task elsewhere.
- SKILL
nibiru-cli
Query Nibiru chain state and submit transactions with the `nibiru` CLI, including setup via `ud`, config inspection, key discovery with `nibiru keys list`, bank transfers, bank balance queries, EVM multi-VM balance checks such as `nibiru q evm balance` for Sai USDC, wasm contract queries, wasm execute/instantiate flows, and transaction lookups by hash. Use when the user mentions `nibiru`, Nibiru CLI, `nibiru keys list`, `--from`, `nibiru tx bank`, `nibiru tx wasm`, `nibiru q bank`, `nibiru q evm balance`, `nibiru q wasm`, `nibiru q tx`, balances, contract-state smart, or tx hashes.
- SKILL
nibiru-gov-upgrade
Queries Nibiru governance proposals (including software-upgrade proposals) using the `nibiru` CLI, maps explorer UI fields to on-chain queries, computes quorum/threshold/veto metrics, and correlates validator votes using staking queries. Use when the user mentions `nibiru q gov`, governance proposals, software upgrades, votes, deposits, tally, quorum/threshold, validators, proposal status, or `nibiru tx gov`.
- SKILL
nibiru-gql
Query the Nibiru Heart Monitor GraphQL API and its indexed chain data. Use for wallet balances, staking, validators, delegations, Cosmos transaction messages, Wasm events, indexing gaps, or comparisons with Sai Keeper. Read the matching reference before querying.
- SKILL
postgresql-psql
Comprehensive guide for PostgreSQL psql - the interactive terminal client for PostgreSQL. Use when connecting to PostgreSQL databases, executing queries, managing databases/tables, configuring connection options, formatting output, writing scripts, managing transactions, and using advanced psql features for database administration and development.
- SKILL
repo-map
Maps and routes between key repositories on my machine (boku, nibi-chain, nibi-geth, nibi-go-hm, nibi-ts-sdk, sai-web, sai-perps, nibi-iac, nibi-web, gh-io-ud, and the in-tree Wasm runtime and Rust contracts). Use when the user asks which repo to look at, where a feature lives, how repos connect, how services are deployed (Terraform/IaC), when a task spans chain, EVM, indexer, SDK, frontend, and docs, or when the user asks about the personal site, blog posts, official Nibiru docs, or Astro/gh-pages.
- SKILL
sai-perps
Query and reconcile Sai Perps data from live contracts, Sai Keeper GraphQL and Postgres, and DexPal REST. Use for markets, trades, fees, open interest, vaults, balances, referrals, or disagreements between on-chain and indexed data. Use agent skill `sai-ops` for mutations.
- SKILL
tailscale-serve
Troubleshoot, document, and operate Tailscale Serve for local development previews, HTTPS `.ts.net` URLs, MagicDNS, admin-console HTTPS certificate setup, WSL or localhost proxy targets, phone testing over a tailnet, and curl/OpenSSL diagnosis of Serve TLS failures. Use when a user says Tailscale Serve, `tailscale serve`, `.ts.net`, MagicDNS, HTTPS certs, SSL protocol error, TLS alert, Funnel versus Serve, localhost preview, Next.js preview over Tailscale, or sharing a dev server with a phone or another tailnet device.
- SKILL
ud-writing-tech
Improve technical writing for specs, implementation notes, READMEs, engineering references, and agent-authored docs. Use when drafting, editing, reviewing, or polishing technical prose; when the user mentions technical writing, style, clarity, ambiguity, specs, docs, documentation, or Google developer docs; or when docs contain many code symbols, database names, API endpoints, GraphQL schema items, commands, or skills.
- SKILL
unslop
Cut AI tells from any writing. Must always apply.
No matching skills. Try another term or clear your search.