Coding & Development

LITE SUBSET of ProGoals Permission Gate. Classify every planned agent action as READ, REVERSIBLE or IRREVERSIBLE, and require the human's explicit approval (with an exact approval card) before sends, DMs, payments, deletes and shares. Use before any tool call that leaves the agent's own workspace.

Run tarot reading practice sessions with Jeff. Use this skill whenever Jeff wants to practice tarot card readings, says "let's do tarot practice", "I want to practice readings", "give me a tarot scenario", "deal me some cards", or anything suggesting he wants to drill his card interpretation skills. This skill sets up realistic seeker scenarios, draws random cards (with reversals), coaches Jeff through his interpretations, and gives targeted feedback — including honest pushback when the read goes off the rails. Always use this skill when Jeff wants tarot practice — even if he just says "let's do a round" in the context of a prior tarot session.

Verify factual claims before delivering them. Use before any answer or deliverable the user will act on, forward, or share with others — rules, policy, legal, financial, date, or product facts — and whenever they say 'is that right', 'double-check that', 'verify this', 'fact-check', 'are you sure', or 'source?'. Exception: vetting a claim someone else handed the user is critical-thinking-walkthrough; fetching page text is reliable-fetch (this skill calls it).

Test a ready-made list of deliverables, documents or artifacts before anyone commits to tracking it. Use when someone is handed a list from a template, vendor, consultant, PMO framework or AI (\"standard project documents\", \"required artifacts\", \"deliverables checklist\") and asks whether to adopt it, what is really required, what to drop, or what is missing. Tags each item by who requires it (funder, law or regulation with citation, a named person, or standard practice that nobody requires), reads the funder's or agency's own template section by section to find required items the list leaves out, and returns a table plus a drop / keep / add list. Not for building a list from scratch with no list in hand, and not for checking whether finished documents are good.

Read-only preflight check of a repo's git/GitHub setup before pushing — especially the first push. Reports which GitHub account the push will authenticate as, which identity the commits will be authored with, whether the remote URL is being rewritten by insteadOf, and whether the branch and remote state will actually accept the push. Use this whenever the user says "check my github setup", "am I ready to push", "before first push", "which account will this push as", "did I set the remote right", "verify my remote", "wrong git account", "pushing as the wrong user", or hits "src refspec main does not match any", "Repository not found", "403", "GH007", "updates were rejected", or "Permission denied (publickey)". Also use it proactively before helping someone set up or push to a brand-new repository, and whenever a machine has more than one GitHub account or SSH host alias, since the failure mode there is silent — the push succeeds under the wrong identity.

Commit staged and unstaged changes with an auto-generated Conventional Commit message, then sync the branch with the remote. Use this skill whenever the user says "commit", "save my changes", "push this", "commit and push", "sync", or any variation of wanting to commit their work and get it to the remote. Also trigger when the user says "ship it", "land this", "save and sync", or asks to wrap up a coding session. Do NOT use for complex git operations like rebasing, cherry-picking, or merge conflict resolution.

Use this skill for backend development — server logic, authentication, microservices, serverless functions, middleware, background jobs, caching strategies, and backend architecture patterns. Trigger on keywords: backend, server, API endpoint, middleware, authentication, authorization, microservice, serverless, background job, queue, caching, session.

Use this skill when using AI to learn new technologies, navigate unfamiliar codebases, do interview prep, identify skill gaps, or build a personal learning system. Also use when helping someone learn rather than just doing the work for them. Trigger on keywords: learn, learning, understand, explain, teach me, how does X work, unfamiliar codebase, interview prep, skill gap, study, tutorial.

Load general development standards. Applies to all repos. Invoke at the start of a session or when standards need reinforcing.

Run work through a self-grill, prove, challenge, simplify, clean-up loop, installing its companion skills first. Use when the user says autopilot or principal mode, or hands over a multi-file change, a bug with no known cause, or work they will review later.

Planning and approval gates for state-changing work.

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Finish real work with a Builder-Challenger pass. The building agent hands its finished work to a different model (Codex or Claude, called read-only) that challenges it under the Builder-Challenger Protocol, loops for up to 5 rounds (the Operator can extend once), and presents the objection ledger to the Operator (the human who owns the work) for go/no-go. Use when work is ready for completion approval, when AGENTS.md says "Finish with a challenge", or when asked to run BCP, challenge this, or get a second-model review. Skip for quick, obvious, easy-to-undo changes.

This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.

Use when about to edit, create, or delete an agent skill. Shared skills are sourced from the agent-skills repository; downstream-local skills stay with their owning repository.

为16:9横屏AI漫剧创作、改编、审查和修订可生产剧本。用于将故事、小说或既有剧本转为90-180秒单集、可分镜和可连续制作的剧集文本；不负责资产图或视频生成。

코드가 다음 변경을 싸게 만드는지 본다. 기존 추상화를 우회한 중복, 레이어 위반, 변경 이유가 둘 이상인 단위, 호출자마다 같은 처리를 반복하게 만드는 API를 찾아 blocking과 suggestion으로 나눈다. "유지보수성 봐줘", "구조 리뷰", "설계 괜찮아?", "중복 없나", "머지 전에 점검", 에이전트 PR 리뷰, 커밋 전 셀프 체크, 기존 모듈 점검에 사용한다.

Keep a project's dependencies up to date and free of known vulnerabilities. Finds outdated packages and security advisories, applies security fixes and safe patch/minor bumps, then takes major upgrades one at a time (reading the migration guide, fixing breakage, re-running lint/tests/build), and finishes with a branch, focused commits, and a PR. Works for npm/pnpm/yarn, Python (pip, uv, poetry), Rust (cargo), Go modules, and others through an OSV lockfile scan. Use this whenever the user mentions outdated packages, dependency updates, bumping versions, upgrading a library or framework to a new major, npm audit / pip-audit / cargo audit warnings, CVEs or GHSAs in dependencies, Dependabot or Renovate alerts, "is anything vulnerable", or routine dependency maintenance, even if they only ask to check and not to change anything.

Pre-indexed local code knowledge graph for navigating and understanding codebase structure (symbols, call paths, dependencies, blast radius) without a grep/read loop. Use when answering "how does X work", "what calls Y", managing CodeGraph daemons/indexes across Git branches or worktrees, or surveying an unfamiliar part of the active repository. Do not use for external/public repositories not yet indexed locally, or a repository with no .codegraph/ index — run codegraph init there first, or use deepwiki for public repos instead.

Verify every citation and quotation in an article draft against the real sources — cases via CourtListener + official reporters, scholarship via the user's Zotero library then the open web — and return a graded, footnote-by-footnote report with a "needs your attention" section first, plus a citation-form section (short cites per Bluebook R. 10.9/4.2 and italics/small caps per R. 2.1(a)) decided from the draft alone. Trigger when the user wants a draft cite-checked ("cite-check this", "check the citations/quotes in this draft", "run cite-check on <file>"). Input: a .docx with real Word footnotes (markdown/plain-text fallback). Not a full Bluebook linter — signal order, citation order and cite composition stay out.

Gather the full document set for a SCOTUS case being prepped for a podcast episode, class, or article — cert-stage filings, merits briefs, lower-court opinion, questions presented, and oral-argument transcript — and load them onto the user's reMarkable in a per-case folder. Manual trigger — use when the user says "prep <case>", "grab the briefs for <case>", "load up <case>", or similar.

>- Use when installing or using a Croct SDK in application code: rendering slot content, evaluating CQL queries, server or client fetching, prerendering, identifying users, app ID / API key env vars, testing, or debugging. Covers JavaScript (`@croct/plug`, `croct.fetch`, `croct.evaluate`), React (`@croct/plug-react`, `<CroctProvider>`, `useContent`, `<Slot>`, `useEvaluation`, `useCroct`), Next.js (`@croct/plug-next`, `fetchContent`, `cql`, middleware/proxy, `NEXT_PUBLIC_CROCT_APP_ID`, `CROCT_API_KEY`), Vue (`@croct/plug-vue`), Nuxt (`@croct/plug-nuxt`), Shopify Hydrogen (`@croct/plug-hydrogen`), PHP (`croct/plug-php`), Laravel, Symfony, and Drupal. Triggers: slot IDs like `home-hero@1`, `SlotContent`, "Croct is not plugged in", "initial content is required for server-side rendering", "Did you forget to configure Croct's middleware?", CORS errors.

Set up CountWatch monitoring for business counts (orders, sign-ups, payments, traffic): create an account with one API call, send or import counts, add a webhook and prove it with a test alert. Use when the user asks to monitor, watch or get alerted on a count or rate, or to find out when something stops, spikes or drops.

Vigila sismos y temblores cerca de la ubicación del usuario (por defecto Copiapó, Chile) usando USGS, EMSC y, si está configurado, GlobalQuake Server o el backend sismo-rt, y avisa en la conversación (y con notificación push) apenas se detecta uno. Úsala cuando el usuario diga "avísame si tiembla", "vigila los sismos", "¿hubo temblores cerca?", "¿tembló?", "último sismo", "GlobalQuake", "alerta sísmica" o pregunte por terremotos recientes o en curso.