837 件 ・ 関連度順
概要と使いどころ
Investor Email Specialist. Use to write fundraising outreach, warm intro blurbs, follow-ups, investor updates, and close-the-loop emails with founder-grade brevity and specificity.
日本語の概要は準備中です。原文の説明を表示しています。
Socratic code review and refactoring session — whether it's your own code, a teammate's PR, or something you inherited. Leads you to see the issues through questions, names smells and moves precisely, then closes with a concrete plan.
日本語の概要は準備中です。原文の説明を表示しています。
Explain what a piece of code does — a specific file, class, or method in close detail, or a user-facing flow as a concise system overview. What it does and why, not whether it's good.
日本語の概要は準備中です。原文の説明を表示しています。
"Calculate text similarity using lexical and semantic methods for matching and deduplication. Use this skill when the user needs to find similar documents, detect near-duplicates, or measure semantic closeness between texts — even if they say 'how similar are these texts', 'find duplicates', or 'semantic matching'.".
日本語の概要は準備中です。原文の説明を表示しています。
End-of-session ritual. Close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.
日本語の概要は準備中です。原文の説明を表示しています。
End-of-session ritual — close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.
日本語の概要は準備中です。原文の説明を表示しています。
Break the spell of local productivity. Ask whether completing all open beads actually closes the gap to the project goal. Use at milestones or when busy agents feel directionally off.
日本語の概要は準備中です。原文の説明を表示しています。
Dangling markup injection playbook. Use when HTML injection is possible but JavaScript execution is blocked (CSP, sanitizer strips event handlers, WAF blocks script tags) — exfiltrate CSRF tokens, session data, and page content by injecting unclosed HTML tags that capture subsequent page content.
日本語の概要は準備中です。原文の説明を表示しています。
Bug bounty findings secretary, tracker, and workspace initializer for the bb-huge portal. Use this skill for web security research, vulnerability hunting, and hunt workspace setup. Triggers on: "log finding", "save finding", "add to bb-huge", "record vulnerability", "update finding", "show findings", "bb-huge stats", "mark as confirmed", "mark as rewarded", "setup workspace", "pull evidence", "continue working on finding", "dump attachments", "list my skills", "what skills do I have", "/bb-huge init", "init hunt workspace", "new bug bounty program", "start hunting", "mobile bug bounty", "binary analysis", "source code review", "white-box audit", "h1-brain", "hack program", "hack()", "search disclosed", "fetch rewarded". Also auto-activates whenever a vulnerability is discovered during any recon, fuzzing, or manual testing session — do not wait to be asked.
日本語の概要は準備中です。原文の説明を表示しています。
Triages an Aikido security findings CSV against a local codebase. For each finding, reads the flagged file, traces the code path, and verdicts it as KEEP OPEN or CLOSE with a specific reason. Outputs a reviewed CSV and a self-contained HTML evidence report. Run this at the end of a pentest when an Aikido CSV is available.
日本語の概要は準備中です。原文の説明を表示しています。
Write Prisma Next queries for Postgres, SQLite, or Mongo — pick a lane (Postgres/SQLite `db.orm.<Model>` + `db.sql.<table>`; Mongo `db.orm.<root>` + `db.query.from(...)` pipeline builder), filter / project / sort / paginate, eager-load with `.include(...)`, Postgres/SQLite `db.transaction(...)`, Postgres/SQLite ORM `.aggregate(...)`, Mongo aggregations via query builder, namespace-aware accessors (`db.orm.<ns>.<Model>`, `db.sql.<ns>.<table>`). Triggers: query, where, match, select, project, orderBy, take, skip, include, lookup, first, all, count, aggregate, group, create, update, delete, upsert, returning, transaction, db.close, script teardown, variant, polymorphism, drizzle-style, kysely-style. Notes: `.all()` is a Thenable (just `await` it), iterators are single-use (`RUNTIME.ITERATOR_CONSUMED`), Postgres `count` is `number` while sum/avg/min/max are `number | null`, ranges use chained `.where()` or `and(...)` (no `.between(...)`).
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user wants the full existing-registry Trust Magnitude inspector: understand why a named Gaia skill has a particular star rank, what its Trust Magnitude (TM) score is, which evidence rows are contributing (or dead), how far it is from the next grade, or what evidence to add to move the needle. Also use when asked for a full leaderboard of all named skills ranked by TM. Triggers: "why does X have 3 stars", "what's the TM for X", "inspect TM", "explain the score for X", "what evidence would rank up X", "show leaderboard", "rank all skills by TM", "what's dragging down X's score", "dead evidence rows", "how close is X to grade A/S".
日本語の概要は準備中です。原文の説明を表示しています。
Triage the Gaia issue backlog and skill-batch intake queue. Use this skill when someone asks to: "triage issues", "clean up the issue tracker", "review the backlog", "close stale issues", "process the intake queue", "review skill-batches", "evaluate draft skill proposals", "approve or reject pending skills", "is this issue still valid?", "what's clogging the backlog?", "run a triage pass", or /gaia-triage. Covers two workstreams: (1) GitHub issue lifecycle — identifying resolved, stale, or need-more-info issues and acting on them via gh CLI; (2) skill-batch intake — evaluating draft proposals in registry-for-review/skill-batches/ and routing them toward promotion or rejection. This is the gatekeeping step before new skills enter the canonical registry; and (3) a cross-repo triage sweep — sizing, P0-P4 prioritization, umbrella/epic synthesis, and assignment across every gaia-research org repo, on the one headquarters tracker.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end plan → implement → review pipeline that takes one triaged Gaia issue to a merged-ready PR, with Kill Criteria on the issue and zero follow-up debt. Use when someone says: "resolve this issue", "take #N end-to-end", "work the P0 queue", "fix and ship this issue", "run the resolver", "close out this issue properly", or /gaia-issue-resolver. Works any gaia-research org repo — gaia-skill-tree, gaia-research, gaia-skill-heaven — while the issue itself lives on the headquarters tracker, gaia-research/gaia-skill-tree. Assumes the issue is already triaged and carries a P0–P4 label; if it does not, run /gaia-triage first.
日本語の概要は準備中です。原文の説明を表示しています。
Reference guide for the full manual Gaia curation pipeline. Invoke at any phase when unsure what command to type next: gaia-curate, L4 review, gaia push, ev-pipeline (Phases 0–4), gaia-ingest, or close. Trigger phrases: "/gaia-consult", "what's the command for", "remind me how to", "I'm lost in the pipeline", "what do I do next", "consult the pipeline doc", "pipeline reference".
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive, reusable playbook for multi-component suite intake under Yggdrasil III. Audits component installability, maps origin candidates to generic capabilities, ingests named components with shared-repo baseline caps, manifests suites via gaia dev fuse, calibrates capstone and component ranks, and closes out via Class S regeneration.
日本語の概要は準備中です。原文の説明を表示しています。
Post-review intake closing skill. After an intake is resolved (whether accepted via review/meta PR merge or rejected/deferred at triage/evidence review), run this skill to post standardized, personalized closing comments on the PR (if any) and each intake issue. Comments include: evidence pipeline findings with /trust-appraise TM output, per-row artifact scores, decisions rationale, path-to-promotion/acceptance guidance, and a mandatory badge status note including the universal Powered by Gaia badge. Use after curation completes, before or immediately after merge for accepted intakes, or immediately upon rejection.
日本語の概要は準備中です。原文の説明を表示しています。
Measure CI churn cost for a pull request: how many commits and how many CI-compute seconds were burned on avoidable "fix the CI" push rounds. Use when you want to understand the efficiency cost of a PR's iteration cycle, get actionable pre-push check suggestions, or include a churn summary in a pipeline report. Triggers: "ci churn", "how much CI did we burn", "avoidable commits", "ci efficiency", "wasted CI time", "churn report", "/ci-churn". Called automatically by /fp-drift at pipeline close.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user wants to understand why a named Gaia skill has a particular star rank, what its Trust Magnitude (TM) score is, which evidence rows are contributing (or dead), how far it is from the next grade, or what evidence to add to move the needle. Also use when asked for a full leaderboard of all named skills ranked by TM. Triggers: "why does X have 3 stars", "what's the TM for X", "inspect TM", "explain the score for X", "what evidence would rank up X", "show leaderboard", "rank all skills by TM", "what's dragging down X's score", "dead evidence rows", "how close is X to grade A/S".
日本語の概要は準備中です。原文の説明を表示しています。
Build a roll-forward schedule for a balance-sheet account or account group, tying beginning balance, activity, reversals, payments, adjustments, and ending balance to GL support. Use for month-end close packages and audit support.
日本語の概要は準備中です。原文の説明を表示しています。
Build a period-end accrual schedule by computing each accrual, citing support, and drafting journal entries for controller approval. Use during month-end close; this drafts entries only and must not post them.
日本語の概要は準備中です。原文の説明を表示しています。
Write flux commentary for P&L and balance-sheet lines over threshold, comparing current period against prior period and budget with drivers explained from underlying activity. Use for month-end close packages and management reporting.
日本語の概要は準備中です。原文の説明を表示しています。
SQL discipline for querying Pulp Perfetto traces (.pftrace) with trace_processor — idempotent CREATE OR REPLACE PERFETTO views, GLOB not LIKE, dur = -1 incomplete-slice handling, EXTRACT_ARG for span args, joining on stable utid/upid, SPAN_JOIN PARTITIONED, and the draft→validate→execute loop. Ships Pulp's CPU/UI trace stdlib plus closed GPU startup, health, and probe views. TRIGGER when writing or debugging SQL over a .pftrace, when `pulp trace query` returns wrong/empty rows, or when the trace-analysis skill needs a query primitive.
日本語の概要は準備中です。原文の説明を表示しています。
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.
日本語の概要は準備中です。原文の説明を表示しています。