Showing 32671–32700 of 77202 skills
This repo is indexed by graft/. For ANY task here, whether understanding how something works, finding where code lives, tracing what calls a symbol or what a change breaks, or scoping an edit, get your context from graft before grepping or reading source files.
gaia-research/gaia-skill-tree
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
gaia-research/gaia-skill-tree
Consult this skill BEFORE proposing a fix to any CLI gap or schema gap that touches evidence, trust magnitude, evidence types, evidence grades, the TM formula, or star-level promotion gates. Also read it whenever an issue mentions citations, stars, commits, contributors, views, reviewers, percentile, arxiv, github-stars-own, repo-own, social-signal, benchmark-result, peer-review, self-attestation, fusion-recipe, verifier-attestation, or proxy-containment — those are the 10 canonical evidence types and the raw inputs that feed their formulas. Also read it when asked whether a skill qualifies for a given star level (0★–6★): the Star Bar and promotion gates live in `META.md`, not in the TM methodology page. Reading both prevents proposing a calibration that satisfies the TM grade threshold but violates a Star Bar installability or link requirement.
gaia-research/gaia-skill-tree
Playbook for correcting a named skill's star level to match its computed Trust Magnitude grade, with an independent post-calibration verification pass and a CLI-logged timeline event (never hand-written). Use when: recalibrating a skill's level, fixing a stale or drifted star rating, running a batch of `gaia dev calibrate` corrections, or confirming a past calibration actually landed. Triggers: "calibrate <skill>", "recalibrate the trust magnitude backlog", "promote/demote <skill> to N stars", "why is <skill> still N stars", "verify a calibration actually landed", "Hall of Heroes ranking is wrong".
gaia-research/gaia-skill-tree
Playbook for landing one evidence-approved single-skill intake whose L4 topology is a NEW fusion generic plus one named implementation: create the generic and its prerequisites, create the named skill, ingest each verified evidence row, and appraise Trust Magnitude — then stop at the calibration gate. Use when: an intake issue carries intake:topology-approved and intake:evidence-approved, the promotion PR review/meta/intake-<N> is open, and a reviewed evidence manifest exists. Triggers: "ingest the approved intake", "land intake #N", "add the generic and named skill for this intake", "run the ingest for the evidence-approved batch". Not for suites (use gaia-fuse-full-suite), not for an existing generic (add the named skill with `gaia dev add --named` directly), and not for star calibration (dev-calibrate).
gaia-research/gaia-skill-tree
Broad, pre-curation evidence reconnaissance for a declared Gaia skill, intake batch, upstream repository, or proposed generic capability. Run before choosing a discovery strategy or mapping topology, to give the curator independent research leads and counterevidence. Context only: never scores, grades, ratifies, ingests, or mutates the registry. Later ev-discovery and ev-pipeline phases validate/promote any selected leads.
gaia-research/gaia-skill-tree
Inspect scope and unexpected registry drift against the actual PR base and leave a concise final receipt. Use for "check for PR drift" or the final stage of feature-pipeline; never silently discard unknown changes or infer a clean diff from validator success.
gaia-research/gaia-skill-tree
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.
gaia-research/gaia-skill-tree
Implement a scoped feature-pipeline plan in coherent commits and push each meaningful unit. Use for "implement the plan", "apply the plan", or the implementation stage; routine lean/economy work does not require planApproved, while explicit human gates remain binding.
gaia-research/gaia-skill-tree
Turn verified findings into a bounded file-aware plan and reuse or prepare a draft PR. Use for "plan the fix", "draft the implementation plan", or the planning stage of feature-pipeline; preserve actual human gates without making every plan require approval.
gaia-research/gaia-skill-tree
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.
gaia-research/gaia-skill-tree
Use for explicitly requested fixed-topology, discovery-only Gaia curation; for one source page use gaia-curate. Atomically checkpoints each candidate transition, retries only the failed field, and stops at human L4 review.
gaia-research/gaia-skill-tree
User-invoked bounded discovery of external agent ecosystems and narrowly scoped challenger reconnaissance for existing Gaia capabilities. Use when asked to scout an external source or investigate a possible challenger; never use as verification, intake approval, trust scoring, or canonical mutation.
gaia-research/gaia-skill-tree
This repo is indexed by graft/. For ANY task here, whether understanding how something works, finding where code lives, tracing what calls a symbol or what a change breaks, or scoping an edit, get your context from graft before grepping or reading source files.
gaia-research/gaia-skill-tree
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
gaia-research/gaia-skill-tree
Consult this skill BEFORE proposing a fix to any CLI gap or schema gap that touches evidence, trust magnitude, evidence types, evidence grades, the TM formula, or star-level promotion gates. Also read it whenever an issue mentions citations, stars, commits, contributors, views, reviewers, percentile, arxiv, github-stars-own, repo-own, social-signal, benchmark-result, peer-review, self-attestation, fusion-recipe, verifier-attestation, or proxy-containment — those are the 10 canonical evidence types and the raw inputs that feed their formulas. Also read it when asked whether a skill qualifies for a given star level (0★–6★): the Star Bar and promotion gates live in `META.md`, not in the TM methodology page. Reading both prevents proposing a calibration that satisfies the TM grade threshold but violates a Star Bar installability or link requirement.
gaia-research/gaia-skill-tree
The Balanced Coupling model for software design. Use when: designing modular architectures, evaluating coupling between components, reviewing code modularity, deciding whether to split or merge modules/services, assessing integration patterns, classifying coupling as balanced or unbalanced, applying DDD strategic and tactical patterns, reasoning about cohesion vs coupling trade-offs, identifying distributed monolith risks, or explaining why a system is hard to change. Provides the three-dimensional framework (integration strength, distance, volatility) and the balance rule for making coupling decisions.
vladikk/modularity
Designs modular high-level architectures from functional requirements and produces design documents for each module. Use when designing a new system, creating architecture documentation, or producing module-level design specs with integration contracts and test specifications.
vladikk/modularity
Use this skill when designing APIs, module boundaries, or any public interface. Create stable, well-documented interfaces that are hard to misuse — REST endpoints, GraphQL schemas, module contracts, component props. Covers contract-first design, error semantics, validation boundaries, idempotency, and consistent naming.
JPeetz/agent-skills
Use this skill when designing, implementing, or optimizing a GraphQL API: schema-first design, resolver architecture with DataLoader to prevent N+1 queries, mutation patterns with idempotency, real-time subscriptions, Apollo Federation for distributed graphs, security hardening (depth limiting, rate limiting, authorization), and production performance (persisted queries, caching, CDN integration). Activates on requests to design a GraphQL schema, review resolvers for N+1 queries, set up federation, add subscriptions, fix pagination, or harden a GraphQL API.
JPeetz/agent-skills
Use this skill when reviewing any code change, PR, or diff before merge — whether written by yourself, another agent, or a human. Conducts multi-axis code review across correctness, readability, architecture, security, and performance with structured severity labeling and verification gates.
JPeetz/agent-skills
Use this skill when mapping code, architecture, or infrastructure changes to specific control IDs in financial services compliance frameworks — PCI-DSS v4.0 for payment card data and MAS TRM for Singapore-regulated institutions — producing an audit-traceable findings report with per-control remediation. Use this instead of a general security review whenever a compliance framework (PCI-DSS, MAS TRM), regulator, audit, or cardholder-data scope is mentioned, even if the request is phrased as a code review or a yes/no compliance question. Triggers on: "PCI-DSS check", "MAS TRM", "is this compliant", "compliance review", "audit this change for banking regulations", "does logging this violate PCI", "cardholder data handling review".
JPeetz/agent-skills
Use this skill when handling global privacy compliance work — GDPR, CCPA/CPRA, HIPAA Privacy Rule, EU AI Act, LGPD, cross-border data transfer mechanisms (SCCs, BCRs, EU-US DPF), PII identification and classification, data minimization, consent management, privacy-by-design patterns, DPIA workflows, data subject access request (DSAR) handling, and breach notification procedures. Provides procedural knowledge for compliance workflows — NOT legal advice. Designed for agentic platforms including Claude Code, Codex, Cursor, Gemini CLI, OpenClaw, GitHub Copilot, Windsurf, and OpenCode.
JPeetz/agent-skills
Use this skill when analyzing structured datasets: load, clean, explore, visualize, and report on data from CSV, JSON, Excel, or SQL sources. Produces statistical summaries, correlation matrices, time series analysis, regression models, hypothesis tests, and publication-quality visualizations.
JPeetz/agent-skills
Use this skill when working with dbt (data build tool): model development, testing, documentation, semantic layer (MetricFlow), dbt Mesh governance, incremental strategies, and migration workflows. Follows dbt Labs best practices for data transformation and multi-project collaboration.
JPeetz/agent-skills
Use this skill when exploring an unfamiliar dataset, investigating data quality issues, validating data pipeline outputs before production use, reviewing SQL queries for correctness and performance, or producing a data quality scorecard for a data asset.
JPeetz/agent-skills
Use this skill when setting up or modifying build and deployment pipelines. Automate quality gates so no change reaches production without passing lint, type-checking, tests, and build. Configures CI runners, deployment strategies, and rollback plans. Use when CI fails, is missing, or needs optimization.
JPeetz/agent-skills
Use this skill when authoring, securing, or managing infrastructure as code in Terraform, Pulumi, CloudFormation, Ansible, or Bicep — or when selecting an IaC tool, reviewing modules for security, detecting drift, optimizing cost, or planning a multi-tool migration. Covers AWS, Azure, GCP, and hybrid cloud, with per-tool authoring patterns, CIS/SOC 2 security checklists, drift detection, and cost guardrails across the full IaC lifecycle.
JPeetz/agent-skills
Use this skill when running a full software development lifecycle as quality-gated agent workflows — spec, plan, test-driven build, automated testing, code review, web performance audit, code simplification, and production deployment. Exposes slash-command entry points (/spec, /plan, /build, /test, /review, /webperf, /code-simplify, /ship) covering SDLC automation, feature-flag deployment, production readiness review, and incremental rollout.
JPeetz/agent-skills
Use this skill when processing documents programmatically — PDF manipulation (extract, merge, split, rotate, watermark, form-fill, OCR), DOCX creation and editing (templates, mail-merge, style management), XLSX spreadsheet handling (formulas, charts, pivot tables, data analysis), PPTX presentation generation (layouts, charts, media, speaker notes), and cross-format document conversion via pandoc and native libraries. Designed for agentic platforms — Claude Code, Codex, Cursor, Gemini CLI, OpenClaw, GitHub Copilot, Windsurf, and OpenCode.
JPeetz/agent-skills