Showing 42331–42360 of 60223 skills
Make a repository's agent rulebook (AGENTS.md / CLAUDE.md) verifiable: vendor a deterministic checker, audit every rule and citation against the code, bootstrap a lean rulebook from what the code cannot say, and grow it from audit findings. Use when setting a repo up for agents, when asked to audit or slim AGENTS.md or CLAUDE.md, before the first EF feature in a repo, or after an audit proposes rulebook lines. Do NOT use to generate a codebase overview or documentation tour.
micaelcf/ef-harness
Design standards for cloud and on-prem infrastructure — Azure, AWS, GCP, Hetzner, OVHcloud and bare-metal data centers — organised by tier (baseline, production, enterprise landing zone) so recommendations match the real size of the project. Use whenever designing, provisioning or reviewing cloud networking, identity, managed Kubernetes (AKS/EKS/GKE), landing zones, VPC/VNet layouts or data-center infrastructure, even if the user only names a single provider service.
hoangminhung/devops-ai-kit
Container and software supply-chain security in CI/CD — vulnerability scanning gates with Trivy or Grype, SBOM generation with Syft, image signing with Cosign (keyless or key-based), admission policies that only allow signed images (Kyverno, Sigstore policy-controller), base-image update cadence and registry hygiene. Use whenever building or changing CI pipelines that produce images, setting up registries, adding admission policies, or reviewing image security. Dockerfile authoring rules live in the dockerfile rule.
hoangminhung/devops-ai-kit
Database reliability engineering standards for PostgreSQL (and MySQL) on Kubernetes — zero-downtime schema changes with expand/contract, safe DDL (lock_timeout, CREATE INDEX CONCURRENTLY, NOT VALID constraints), running migrations as Jobs/PreSync hooks instead of initContainers, connection pooling with PgBouncer, and operator-managed clusters (Crunchy PGO, CloudNativePG). Use whenever writing or reviewing schema migrations, deploying or tuning database clusters on Kubernetes, configuring poolers, or planning database upgrades.
hoangminhung/devops-ai-kit
Backup and disaster-recovery standards — defining RTO/RPO, 3-2-1 and offsite copies, immutable backups (S3 Object Lock, Azure immutable blob storage, GCS retention), backup layers for Kubernetes objects, volumes and databases (GitOps, Velero, Longhorn, pgBackRest), restore drills, and backup monitoring. Use whenever designing backups, before any stateful or irreversible change, when defining RTO/RPO for a service, or when planning or reviewing restore procedures and DR drills.
hoangminhung/devops-ai-kit
Cloud cost-control standards — cost estimation gates for Terraform changes (Infracost), NAT and data-transfer costs, orphaned resources, Kubernetes right-sizing, storage and log-ingestion costs (including Azure Log Analytics), and non-production savings. Use whenever a change adds or resizes cloud resources, when designing networking that affects data transfer, when reviewing monitoring/logging volume, or when the user asks why the bill is high or how to cut costs.
hoangminhung/devops-ai-kit
Write infrastructure documentation based on real evidence — change records of what was changed and why, concept/learning notes that explain how a tool or stack works, runbooks for operating a component, ADRs for architecture decisions, and blameless postmortems. Use whenever the user wants to document something, write handover or onboarding material, explain how a technology works for learning or for new team members, record a change, or write a runbook, ADR or postmortem.
hoangminhung/devops-ai-kit
Playbook for building or reworking an Azure Kubernetes Service (AKS) environment with Terraform — state backend, network and CIDR planning, Azure CNI Overlay, private vs public API server, Entra ID with Azure RBAC, workload identity, system and user node pools, upgrade channels and maintenance windows, monitoring and Log Analytics cost, policy, and a verification checklist. Use whenever the task is to build, extend, upgrade or review AKS or the Azure infrastructure around it.
hoangminhung/devops-ai-kit
Playbook for deploying, upgrading or extending a self-hosted Kubernetes observability stack — kube-prometheus-stack (Prometheus Operator, Prometheus, Alertmanager, Grafana), Loki, Grafana Alloy as the collector, persistent storage on Longhorn or cloud disks, retention and capacity sizing, alert routing, dashboards as code, and migrating off Promtail/Grafana Agent. Use whenever the task is to build, change, scale, upgrade or troubleshoot monitoring, logging or alerting infrastructure, even if only one component (e.g. just Loki or just Alloy) is mentioned.
hoangminhung/devops-ai-kit
科研学习与论文写作总入口,协调六个模块。帮助不知道提供什么材料的新手逐步产出、自动保存和恢复项目进度,也用于跨阶段研究任务;区分学习、执行和只读检查。
YCC-Lover/research-starter-skills
准备组会、论文汇报、开题与答辩,支持可编辑 PPTX 制作、既有模板改稿、讲稿与问答演练;也用于会议交流、研究记录与 AI 协作。只要提纲或练习时不启动制稿,现行会议与资助规则另行核验。
YCC-Lover/research-starter-skills
Inspect or address GitHub pull request review feedback using thread-aware state. Use for requested changes, unresolved inline review threads, or review comments; fixing feedback authorizes local edits, not GitHub writes.
Starfie1d1272/dsh-github-skills
Diagnose or fix failing GitHub Actions checks from real check and log evidence. Use when the user asks why CI failed or wants failing checks fixed; non-Actions CI is report-only.
Starfie1d1272/dsh-github-skills
Publish task-scoped changes to GitHub through a branch/commit/push/PR flow, including fork-based external contributions. Use when the user wants changes pushed or a PR opened; draft PR is the default.
Starfie1d1272/dsh-github-skills
Explains a topic in plain, literal language for someone who knows nothing about it. Use when someone new to a topic asks for an explanation from the basics.
coder-xieshijie/dev-skills
Enforces lean, surgical output. Suppresses conversational fluff and verbose reasoning traces. Use when agent output feels too chatty or repetitive.
AndrewBrown-USDA/aigb-skills-usda
Campaign-scale audit of exported claims, at campaign end.
Walsworth-Group/physkit
The project home above campaigns; new-campaign invokes it.
Walsworth-Group/physkit
Discover what internal data consumers actually need. Adapted Mom Test and JTBD for data teams. Use when conducting user research, interviewing stakeholders, gathering consumer requirements, running discovery sessions, or when someone asks "what do they need?" or "how do I figure out what to build?"
hollandkevint/data-product-operator
Dimensional modeling and schema design for data products. Star schema patterns, slowly changing dimensions, denormalization decisions, and architecture decision records. Use when designing data models, reviewing schema designs, choosing between normalization strategies, or when someone asks "how should I model this data?" or "should I denormalize?" For OMOP CDM patterns specifically, see healthcare-data-domain.
hollandkevint/data-product-operator
Help a data leader or data product manager choose the next decision, coordinate delivery and review outcomes across one product or a portfolio. Use to establish or improve a data-product operating rhythm, connect existing skills and preserve decision context. Domain agnostic; does not replace the team's tools or grant execution authority.
hollandkevint/data-product-operator
First-principles reasoning for data product decisions. Frames problems as data products, not dashboards or pipelines. Use when evaluating data product strategy, making build-vs-buy decisions, scoping data product features, assessing product-market fit for data offerings, or when someone asks "should we build this data product?"
hollandkevint/data-product-operator
Score whether a data product idea is worth building before committing resources. Validation scorecard, experiment design, and go/kill decisions. Use when evaluating feasibility, making go/no-go decisions, validating demand, sizing bets, or when someone asks "is this worth building?" or "should we invest in this?"
hollandkevint/data-product-operator
Systematic data quality evaluation covering completeness, accuracy, timeliness, consistency, and validity. Use when assessing data pipelines, reviewing data product quality, auditing data sources, defining quality SLAs, building data quality monitors, or when someone asks "is this data trustworthy?" or "how do we measure data quality?"
hollandkevint/data-product-operator
Data presentation and storytelling for data product operators. Narrative structures, chart selection, headline formulas, and anti-patterns. Use when presenting data to stakeholders, building a data presentation, writing an executive summary of findings, telling a data story, or making a case with data. For stakeholder alignment process, see stakeholder-alignment. For metric definitions, see metrics-definition.
hollandkevint/data-product-operator
Team structure and operating rhythm for data product teams. Product squads, Shape Up 6-week cycles, handoff contracts, and role assignments by lifecycle stage. Use when organizing a data team, planning data product development cycles, defining roles and responsibilities, improving team handoffs, or when someone asks "how should we structure our data team?" or "why do we keep losing context between discovery and delivery?"
hollandkevint/data-product-operator
Position data teams as strategic partners, not order-takers. The organizational "why" behind doing discovery work. Use when discussing team positioning, value exchange, demand shaping, escaping the order-taker trap, or when someone asks "how do we stop being order-takers?" or "how does the data team become strategic?"
hollandkevint/data-product-operator
Review a Databricks data product or proposed release using approved metadata and query evidence. Use for Unity Catalog scope, Delta change handling, reconciliation, or a release handoff. Does not provision infrastructure or authorize production writes.
hollandkevint/data-product-operator
Profile approved CSV or Parquet files with DuckDB and produce reproducible quality and join checks. Use for local exploratory analysis, schema drift, identifier preservation or source reconciliation. Does not authorize sensitive-data downloads or arbitrary SQL execution.
hollandkevint/data-product-operator
Ethical data risk evaluation, bias testing protocols, and governance practices for data products. Use when evaluating ML/AI features for fairness, designing bias testing protocols, planning phased rollouts for high-risk changes, reviewing data governance practices, or when someone asks "could this model be biased?" or "how do we ship AI features responsibly?" For HIPAA-specific guidance, see healthcare-data-domain.
hollandkevint/data-product-operator