1.5万 件 ・ 関連度順
概要と使いどころ
Android pentesting playbook. Use when testing Android applications for SSL pinning bypass, exported component abuse, WebView vulnerabilities, intent redirection, root detection bypass, tapjacking, and backup extraction during authorized mobile security assessments.
日本語の概要は準備中です。原文の説明を表示しています。
Prevent common AI report pitfalls — bug blending, inflated threat models, and generic language. Train Claude with your best past reports for concise, technical submissions. Based on Critical Thinking Bug Bounty Podcast Episode 166.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Append a session/state snapshot to MEMORY.md (regardless of where it lives — for this repo it's `founder/MEMORY.md`). Use when the user says "snapshot memory", "save state to memory", "/memory-snapshot", "log what happened in MEMORY", or otherwise asks to record the current session's outcomes for the next orchestrator. Locates the project's MEMORY.md, prepends a dated entry above the previous snapshot (newest first), preserves every existing entry (NEVER overwrites or truncates), and reports back the file path + byte delta. Not for one-off feedback memories (use the user-level memory system at ~/.claude/.../memory/ for those). Not for trimming or deleting old entries.
日本語の概要は準備中です。原文の説明を表示しています。
Dry-run Trust Magnitude for proposed named skills or suites before curation. Use when deciding whether a proposed suite deserves A/S treatment, when checking Fusion Score structural inputs, when comparing repo stars vs suite component counts, or when asked to appraise a candidate before adding it to the registry.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap a new standalone skill repo under gaia-research/ from the canonical template set at gaia-research/gaia-research/templates/skill-repo/. Handles the full flow: interactive prompts for all placeholders, fetches templates via the GitHub API, substitutes values, creates the new repo (gaia-research/skill-<name>), writes README.md / SKILL.md / install.sh / .gitignore / LICENSE / powered-by-gaia.svg, makes the initial commit and pushes. Also supports update mode: re-applies the template structure to a pre-existing skill repo and opens a draft PR with the drift. Use when the user says "new skill repo", "bootstrap a skill repo", "/skill-template", "create skill-foo", "spin up a gaia-research skill repo", "template a new skill", "align skill-fuse to the template", or "/skill-template update <repo>". Requires: gh CLI (authenticated with gaia-research org access), python3, git.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect or exercise the paused gaia curate orchestration scaffold for one source URL. The command currently persists an INITIALIZED run ledger and reports status; its 25 named workflow states and transition methods are a design skeleton, not an implemented automated curation or merge pipeline. Use only for scaffold development, status inspection, or dry-run contract work. For live curation, use gaia-full-pipeline or gaia-consult. Trigger phrases: "/gaia-quick-curate", "inspect gaia curate", "curate scaffold", "quick curate status". For batch/multi-page runs use gaia-curate-dynamic; for crawler branches use gaia-bot-curate; for pending intake proposals use gaia-draft-curate.
日本語の概要は準備中です。原文の説明を表示しています。
Explore a feature or CLI, reproduce defects and record bounded findings. Use for "explore X", "find issues with X", or the exploration stage of feature- pipeline; standalone runs return findings without automatically expanding scope.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and repair Gaia user-tree timelines so every skill's current rank is explained by a chain of Hero's Journey events. Trigger this skill when: a contributor's profile chart shows a stale rank (e.g. still shows 3★ after a demotion to 1★); someone asks to "trace what happened" to a skill's rank; `validate_timelines.py` is failing in CI; you need to backfill missing `demote` or `rank_up` events before cutting a release; a skill was reclassified or Star-Bar-reset and the user tree was never updated; or any time the registry node and user tree disagree on a skill's current level. Uses `scripts/trace_timeline.py` (dry-run + apply) and `scripts/validate_timelines.py` (CI gate). Do NOT hand-edit `timeline[]` arrays — the script synthesises properly labelled events with `previousValue`/`newValue` so the rank chart plots correctly.
日本語の概要は準備中です。原文の説明を表示しています。
Repair verified review and CI failures and monitor bounded CI windows at the current SHA. Use for "address review items", "run to green", or the CI stage; diagnose and repair authorized failures without waiting at routine milestones.
日本語の概要は準備中です。原文の説明を表示しています。
Batch wrapper for /gaia-ingest. Ingests a bounded set of already-verified evidence rows through CLI-only writes, uses --no-build on every row, appraises Trust Magnitude for every affected named skill, then runs exactly one build and validation pass. Use for an L4-approved intake after /ev-pipeline; benchmark-result rows also require a Phase 2B report and explicit human gate approval.
日本語の概要は準備中です。原文の説明を表示しています。
Pick up one bounded Gaia Steward maintenance dispatch, do exactly it, and hand the result back for independent verification. Use when the user says "check the steward lane", "pick up maintenance work", "is there anything for me to fix", "run the steward lane", "/gaia-steward-lane", or when a scheduled routine wakes you with no other instruction. Also use before starting speculative repository cleanup: if Steward has not found the work, the work probably does not exist.
日本語の概要は準備中です。原文の説明を表示しています。
Regenerate and commit Class S site-served artifacts after registry changes, then sync documentation across the main repo and the adjacent wiki. Use this skill when: you've changed registry/nodes/, registry/named/, or named-skills.json and need to regenerate docs/graph/* so the live website reflects the update; CI Guard E (docs-cohesion.yml) is failing because Class S artifacts are out of date; someone says "sync the docs", "regenerate docs", "run gaia dev docs", "update the site graph", "commit the Class S artifacts", "website is stale", or "update the wiki"; or you're finishing a registry PR and need to ensure docs/graph/gaia.json, docs/graph/gaia.gexf, docs/graph/gaia.svg, and docs/graph/named/index.json are committed alongside the source change. Also covers updating README.md, docs/index.html, and mirroring changes to the adjacent wiki repo at ../gaia-wiki.
日本語の概要は準備中です。原文の説明を表示しています。
Firecrawl gives AI agents and apps fast, reliable web context with strong search, scraping, and interaction tools. One install command sets up three skill segments: live CLI tools, app-integration build skills, and outcome-focused workflow skills. Route the reader to the right usage path after install.
日本語の概要は準備中です。原文の説明を表示しています。
Canonical entry point for the full Gaia evidence verification pipeline. Invoke as /evidence-verification-pipeline or /ev-pipeline — both names trigger this skill. Use whenever you need to run the evidence phases end-to-end: collecting raw evidence from the data lake, verifying live GitHub star counts, running Phase 2B benchmark-source verification, running adversarial auditing for noise and URL errors, and checking link health via Firecrawl. Also use when someone says "run the evidence pipeline", "verify the evidence lake", "audit evidence", "run ev-pipeline", "full evidence check", "pipeline run", "prepare evidence for ingestion", or "refresh the data lake". This is the pre-ingestion step — run it before importing any evidence into the registry.
日本語の概要は準備中です。原文の説明を表示しています。
Produce the rendered evidence a human-gated frontend PR owes its reviewer: capture each changed surface (plus the before state for anything modified, plus mobile width), then generate one self-contained local HTML page the founder can open and review without checking anything out. Use when a PR is gated by the "Frontend changes are HUMAN-GATED" section of CLAUDE.md, or when the user says "/design-gate", "screenshot evidence for this PR", "prep this for founder review", "build the design evidence page", "what does this look like before and after". The page comes from a template script, not hand-written markup. Output is session-local and never committed. Do NOT use for non-gated changes: typo/grammar/factual fixes in an unchanged block, dead link targets, alt/ARIA fixes with no visual change, cache-bust bumps, or refactors with no rendered diff.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate a whole-registry sweep of Gaia — fan out 13 parallel audit agents across every skill, run adversarial verification, surface Semantic Fusion candidates, propose new generic skill references, and synthesize a publish-ready HTML report under docs/meta/reports/. Use this skill for broad, systemic analysis across many skills at once: "run a meta sweep", "sweep the meta", "full meta audit", "audit the whole registry against META.md", "widespread nomenclature issues", "find all skills missing a GitHub link", "produce a meta report", "check for evidence type mismatches across the registry", "find skills that document a third-party tool with no attribution", or explicitly types /gaia-meta-sweep. This is the registry-wide macro companion to /gaia-meta-audit (a prioritized queue, single-pass) and /gaia-audit (fixes one skill). Use it when you need the full surface — 13 audit dimensions, adversarial verification, fusion proposals, and a durable findings artifact — not just a queue.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a prioritized review queue of registry skills and catalog items that need attention. Use this skill whenever someone asks: "what needs review?", "what's overdue for audit?", "where are the weak spots in the registry?", "what should I audit next?", "run a health check on the registry", "show me flagged skills", "find problems in the registry", "what skills need fixing?", or "triage the registry". This is the triage layer — it surfaces candidates ranked P0–P4 so that focused work (via /gaia-audit) targets the right things first. Run this before any audit pass. Also invoke proactively when a PR changes registry/named/ at scale, or before a release, to catch regressions early.
日本語の概要は準備中です。原文の説明を表示しています。
Combine two AI agent skills into one. Trigger phrases: /fuse, "fuse these skills", "combine skills", "merge these two skills", "create a fusion skill"
日本語の概要は準備中です。原文の説明を表示しています。
Discovery-only Gaia curation for one manually selected source page. Fetches and normalizes up to five real SKILL.md candidates, deduplicates and maps them for human L4 review, then stops without evidence scoring or registry mutation.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarially review the full relevant PR diff with isolated probes and meaningful before/after checks. Use for "review the PR", "sandbox review", or the review stage; retain required reviewer independence and report self- review limits honestly.
日本語の概要は準備中です。原文の説明を表示しています。
Developer-Figma collaboration: dev mode, design tokens, component inspection, handoff, and design-system alignment. Use when implementing designs from Figma or aligning code with a design system.
日本語の概要は準備中です。原文の説明を表示しています。
Master Figma workflows with auto layout, components, variables, prototyping, and team collaboration.
日本語の概要は準備中です。原文の説明を表示しています。
Manage energy, not just time: map your ultradian rhythms, align tasks to energy states, and design recovery. Use when time management alone isn't fixing fatigue or afternoon slumps.
日本語の概要は準備中です。原文の説明を表示しています。