agentsclimarketplace

Test

10,628 rows, by stacks then stars

1,559 of these skill files have been read, by 1,201 distinct authors, and what they tell an agent counted. What Test authors agree on, and what they forbid

  • Command line interface testing

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/command-line-interface-testing Skill

    16★ repo

    Use when after installing a Python package or before running a computational workflow for the first time, to verify that the CLI entry point is properly configured, the Python environment is correctly set up, and to discover available command-line arguments and their defaults (e.

  • Integration test development

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/integration-test-development Skill

    16★ repo

    Use when when you have implemented or modified a data ingestion module (e.g., mzML parser) and need to verify that file deserialization produces correct internal representations.

  • Interoperability testing

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/interoperability-testing Skill

    16★ repo

    Use when when a new file format specification exists as a living document (e.

  • Module import testing

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/module-import-testing Skill

    16★ repo

    Use when releasing a new version of a Python package, validating packaging infrastructure changes, or confirming that distribution channels (PyPI, Bioconda) remain functional after upstream updates. Use it as a gate before finalizing a release to catch installation or import breakage early.

  • Package installation verification and testing

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/package-installation-verification-and-testing Skill

    16★ repo

    Use when a Python package has been relocated to a new repository location, reorganized to conform to new organizational standards (e.g., metabolomics-cloud conventions), or its dependencies, metadata, or CI/CD workflows have been modified.

  • Package integration testing

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/package-integration-testing Skill

    16★ repo

    Use when you need to verify that a Python package (or similar installable software) passes its declared integration test suite as a prerequisite to trusting its reliability in production or downstream analysis. Specifically, apply it when you observe a periodic testing CI workflow badge (e.

  • Permanova statistical testing multivariate groups

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/permanova-statistical-testing-multivariate-groups Skill

    16★ repo

    Use when you have normalized peak intensities or abundance matrices from mass spectrometry (e.

  • Rust library compilation and testing

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/rust-library-compilation-and-testing Skill

    16★ repo

    Use when when you have access to Rust source code in a repository with a Cargo manifest (Cargo.toml) and need to verify that a library's read and write APIs produce byte-equivalent or structurally equivalent output.

  • Score distribution analysis and statistical significance testing

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/score-distribution-analysis-and-statistical-significance-testing Skill

    16★ repo

    Use when after computing a scoring function over all possible genomic-metabolomic candidate pairs (e.g., all 2966 MIBiG-GNPS BGC-spectrum pairs), when you have a subset of known validated links and need to assess whether the scoring function ranks them significantly higher than expected by chance.

  • Software testing unit validation

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/software-testing-unit-validation Skill

    16★ repo

    Use when after making code modifications (bug fixes, new features, or refactoring) to the MS2Query codebase, or when contributing changes via pull request. The skill is essential before pushing feature branches to the repository or merging changes into master.

  • Statistical hypothesis testing biology

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/statistical-hypothesis-testing-biology Skill

    16★ repo

    Use when you have a metabolite abundance table (rows=metabolites, columns=samples) from Metabolomics Workbench format and need to test whether specific metabolites or metabolite classes are significantly enriched in particular biological pathways or conditions, beyond what would be expected by.

  • Statistical significance testing

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/statistical-significance-testing Skill

    16★ repo

    Use when when you have computed rank-based accuracy metrics (top-1, top-5, top-10 hit rates) for two or more competing methods on the same test dataset (e.g., Orbitrap spectra), and need to determine whether performance differences are genuine rather than noise.

  • Test driven database development

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/test-driven-database-development Skill

    16★ repo

    Use when when you have an existing tool or library with file-based storage (JSON, CSV, binary formats) that needs to support efficient querying across large datasets, and you want to migrate to a relational database without breaking existing functionality or performance expectations.

  • Two layer architecture dispatch testing

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/two-layer-architecture-dispatch-testing Skill

    16★ repo

    Use when when you need to verify that a wrapper package (e.g., rawrr) correctly bridges R and a managed .NET assembly (such as RawFileReader), specifically to confirm that internal dispatch functions can retrieve assembly location and version string before attempting actual spectral data extraction.

  • Unit test design for analytical chemistry

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/unit-test-design-for-analytical-chemistry Skill

    16★ repo

    Use when when implementing or modifying metabolomics feature detection pipelines (e.g., adduct detection, m/z matching, feature labeling) where correctness directly impacts downstream analysis.

  • Unit test design for biochemical filters

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/unit-test-design-for-biochemical-filters Skill

    16★ repo

    Use when after implementing a custom Filter subclass (e.g., MetabolomicsFilter, TanimotoFilter) in minedatabase/filters.py, you must write unit tests to validate that _choose_cpds_to_filter correctly identifies compounds to retain/remove.

  • Unit test design for file parsing

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/unit-test-design-for-file-parsing Skill

    16★ repo

    Use when when implementing or extending file format parsers in a spectral data pipeline, you need unit tests to ensure that format-specific parsers correctly instantiate spectrum objects with expected m/z arrays, intensity arrays, and metadata attributes before releasing to users or integrating.

  • Unit test development for spectral loaders

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/unit-test-development-for-spectral-loaders Skill

    16★ repo

    Use when when you have implemented parser functions for one or more mass spectrometry file formats and need to verify that metadata and peak lists are correctly extracted and converted into matchms Spectrum objects before committing to a feature branch.

  • Unit test validation for preprocessing

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/unit-test-validation-for-preprocessing Skill

    16★ repo

    Use when after implementing or modifying basic peak filtering operations (e.g., low-intensity peak removal, intensity normalization) on mass spectrometry spectral data in supported formats (mzML, mzXML, msp, MGF, JSON).

  • Vocabulary coverage validation

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-generic/skills/vocabulary-coverage-validation Skill

    16★ repo

    Use when after merging separate vocabularies for distinct data modalities (e.g., spectral tokens for m/z values and intensities, structural tokens for SMILES or graphs) and before deploying the unified vocabulary in a language model.

  • Bonferroni multiple testing correction

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-imaging/skills/bonferroni-multiple-testing-correction Skill

    16★ repo

    Use when when you have performed many pairwise correlation tests between candidate parent and adduct ion intensity pairs in MSI data and need to identify statistically significant relationships while controlling for multiple-comparison bias.

  • Multiple testing correction bonferroni

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/ms-imaging/skills/multiple-testing-correction-bonferroni Skill

    16★ repo

    Use when when you have computed raw p-values for multiple independent statistical tests (e.g., Pearson correlation tests across all pairwise ion combinations in MSI data) and need to report which results remain significant after accounting for multiple comparisons.

  • Multiple testing correction metabolomics

    HolobiomicsLab/asb-skill-collections/packs/metabolomics/nmr/skills/multiple-testing-correction-metabolomics Skill

    16★ repo

    Use when you have computed raw p-values from partial Spearman correlations (or other univariate tests) between each metabolite in a SummarizedExperiment object and a phenotype of interest, adjusted for epidemiological confounders (e.

  • Security regression tests

    ShieldNet-360/secure-vibe/dist/agent-skills/.agents/skills/security-regression-tests Skill

    15★ repo

    Lock every confirmed security fix with a deterministic regression test so CI re-verifies it on every build (no live probing) — Applies to: when a security finding has been confirmed and fixed; when generating or changing security-sensitive code (authz, input handling, secrets); when wiring a security gate into CI/CD

  • Security regression tests

    ShieldNet-360/secure-vibe/dist/claude-skills/.claude/skills/security-regression-tests Skill

    15★ repo

    Lock every confirmed security fix with a deterministic regression test so CI re-verifies it on every build (no live probing) — Applies to: when a security finding has been confirmed and fixed; when generating or changing security-sensitive code (authz, input handling, secrets); when wiring a security gate into CI/CD

  • Security regression tests

    ShieldNet-360/secure-vibe/dist/copilot-skills/.github/skills/security-regression-tests Skill

    15★ repo

    Lock every confirmed security fix with a deterministic regression test so CI re-verifies it on every build (no live probing) — Applies to: when a security finding has been confirmed and fixed; when generating or changing security-sensitive code (authz, input handling, secrets); when wiring a security gate into CI/CD

  • Security regression tests

    ShieldNet-360/secure-vibe/skills/security-regression-tests Skill

    15★ repo

    Lock every confirmed security fix with a deterministic regression test so CI re-verifies it on every build (no live probing)

  • Tdd

    eduwxyz/my-awesome-skills/skills/tdd Skill

    no license15★ repo

    Drives feature work and bug fixes through a tight failing-test-first loop. Trigger when implementing, fixing, or refactoring behavior in a codebase that already has tests. Skip for spikes, visual-only edits, throwaway scripts, and generated files.

  • Verify

    eduwxyz/my-awesome-skills/skills/verify Skill

    no license15★ repo

    Verify that a spec.md's Acceptance criteria are observably covered by green tests before opening a PR. Reads the spec, finds the tests that cover each AC, runs the suite to confirm everything green, and reports gaps (uncovered AC, skipped tests, missing edge-case coverage). When gaps exist, automatically iterates with `tdd` until the spec is satisfied — does not stop while gaps remain. Surfaces tests not mapping to any AC as warnings (no auto-fix; user decides). Trigger after `tdd` is green and before sending the work for review, when the user says "verify the spec", "are we done", "check coverage against spec", "ready for review", "is this PR-ready".

  • App ai guardrails

    a-tokyo/agent-skills/skills/app-ai-guardrails Skill

    15★ repo

    Scaffold a new production application with the full agentic-AI guardrail canon baked in from commit #1: a uniform 7-gate interface (lint, typecheck, test, coverage, build, e2e, audit) on each stack's native runner, strict types, maximal static analysis, coverage thresholds with teeth plus seed tests, pre-commit hooks, hardened CI with optional SonarCloud, supply-chain pinning, and an agent-ready AGENTS.md — every gate verified green before the first commit. Native adapters: Next.js, NestJS, Django, Go, Rust, Spring Boot; a discovery method maps the canon to other stacks. USE FOR: creating or scaffolding a new app, service, or API from scratch; bootstrapping a greenfield repo that AI agents will build in. DO NOT USE FOR: retrofitting an existing codebase or scaffolding a new package into an existing monorepo (both assume repo-root ownership), LLM-safety or content-moderation guardrails, or adding a single tool to an existing project.

  • Safe testing 14

    Teycir/SkillsGuard/testskills/realworld/skills/safe-testing-14 Skill

    no license15★ repo

    Static security scanner for AI agent skill packages. Detects malicious SKILL.md files and bundled scripts before they run.

  • Safe testing 2

    Teycir/SkillsGuard/testskills/realworld/skills/safe-testing-2 Skill

    no license15★ repo

    Static security scanner for AI agent skill packages. Detects malicious SKILL.md files and bundled scripts before they run.

  • Safe testing 26

    Teycir/SkillsGuard/testskills/realworld/skills/safe-testing-26 Skill

    no license15★ repo

    Static security scanner for AI agent skill packages. Detects malicious SKILL.md files and bundled scripts before they run.

  • Safe testing 38

    Teycir/SkillsGuard/testskills/realworld/skills/safe-testing-38 Skill

    no license15★ repo

    Static security scanner for AI agent skill packages. Detects malicious SKILL.md files and bundled scripts before they run.

  • Safe testing 50

    Teycir/SkillsGuard/testskills/realworld/skills/safe-testing-50 Skill

    no license15★ repo

    Static security scanner for AI agent skill packages. Detects malicious SKILL.md files and bundled scripts before they run.

  • Test

    domengabrovsek/claude/skills/test Skill

    no license15★ repo

    Write tests using TDD workflow. Use when the user says 'write tests', 'add tests', 'TDD', or 'prove-it pattern'.

  • Derive tests

    teklabsdigital/x2-method/skills/derive-tests Skill

    no license15★ repo

    AI builds faster than anyone, with no skin in the game and no memory of yesterday. How do you govern that? With X2, decisions stay in files people own, unbreakable rules fail the build, code is disposable, and every human turn is counted. Done is an audited report, never the agent's word.

  • Coding discipline

    viktorbezdek/skillstack/coding-discipline/skills/coding-discipline Skill

    15★ repo

    Research-grounded 5-principle behavioral contract for production LLM coding agents — Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution, and Calibrated Communication. Each principle names its anti-patterns and failure modes with empirical backing (SWE-bench, FeatBench, DELEGATE-52, SE literature). Apply when implementing features, fixing bugs, refactoring, or any coding task where production engineering discipline must be enforced. Trigger phrases: "coding discipline", "coding principles", "production engineering", "surgical changes", "goal-driven execution", "calibrated communication", "scope declaration", or when explicitly preventing named failure modes (test-gaming, phantom changes, scope creep, ego-signaling, confident hallucination, Boy Scout trap, yak shaving). NOT for code review of human-written code (use code-review), NOT for CI/CD setup (use cicd-pipelines), NOT for API design (use api-design), NOT for test framework setup without discipline framing (use testing-framework), NOT for debugging without discipline framing (use debugging).

  • Debugging

    viktorbezdek/skillstack/debugging/skills/debugging Skill

    15★ repo

    Finds and fixes bugs through systematic root cause analysis, stack trace interpretation, browser DevTools automation, CI/CD pipeline debugging, performance profiling, test pollution detection, and AI-powered error analysis. Use when the user asks to debug, fix a bug, investigate an error, analyze a stack trace, find root cause of a failure, profile performance, diagnose test failures (unit/integration/E2E), troubleshoot CI/CD pipelines, debug flaky tests, use Chrome DevTools, or trace data flow to source. NOT for writing new tests or setting up test frameworks (use testing-framework), NOT for TDD methodology or writing tests before code (use test-driven-development), NOT for reviewing code quality or PRs (use code-review), NOT for designing CI/CD pipelines (use cicd-pipelines), NOT for feature development or refactoring (use language-specific plugins).

  • Edge case coverage

    viktorbezdek/skillstack/edge-case-coverage/skills/edge-case-coverage Skill

    15★ repo

    Identify and document boundary conditions, corner cases, error scenarios, and validation requirements that implementations must handle. Use when the user asks to find edge cases, identify corner cases, specify validation rules, enumerate error scenarios, harden a function against bad inputs, or think through what can go wrong at the boundaries of a system. NOT for writing the actual tests (use testing-framework or test-driven-development). NOT for structured risk registers around project-level risks (use risk-management). NOT for security vulnerability scanning (use code-review).

  • Plugin evaluation

    viktorbezdek/skillstack/plugin-dev/skills/plugin-evaluation Skill

    15★ repo

    Measures whether a Claude Code plugin actually works by running triggering evals (does the model pick the skill?) and output evals (does it produce correct results?). Use when you need to evaluate a plugin, run skill activation testing, set up an eval harness, measure plugin quality, write trigger rate tests, check output quality, compare plugin iterations, or iterate on a SKILL description based on eval results. Covers the two eval file formats (trigger-evals.json and evals.json), the grader/analyzer/comparator pattern from Anthropic's skill-creator, quality criteria for eval queries (realistic, varied, near-miss negatives), and the iteration methodology for fixing a skill that fails activation. NOT for writing the plugin's code itself — use plugin-architecture, plugin-hooks, or plugin-validation.

  • Api to production

    viktorbezdek/skillstack/skillstack-workflows/skills/api-to-production Skill

    15★ repo

    End-to-end workflow for taking an API from design through TDD, code review, CI/CD, and containerized deployment. Composes five phases — REST/GraphQL/gRPC design with schemas and error contracts (api-design), red-green-refactor on every endpoint (test-driven-development), multi-perspective code review (code-review), pipeline wiring with automated testing (cicd-pipelines), and Docker containerization with multi-stage builds and optimization (docker-containerization). Use when building a new API endpoint or service that needs to ship to production. Use when converting a prototype API into production-grade infrastructure. NOT for frontend-only work — use frontend-design or react-development. NOT for existing API maintenance without deployment changes — use code-review directly.

  • Security hardening audit

    viktorbezdek/skillstack/skillstack-workflows/skills/security-hardening-audit Skill

    15★ repo

    Systematic security audit workflow for hardening a codebase through structured multi-pass analysis. Composes four skills across five phases — threat surface mapping with attack vector identification (risk-management), security-focused code review targeting OWASP and language-specific vulnerabilities (code-review), boundary condition and validation gap analysis (edge-case-coverage), and security test suite construction with fuzzing and property-based tests (testing-framework). Use when hardening an existing codebase before launch, after a security incident, during compliance preparation, or for periodic security reviews. Use when you want a structured audit rather than ad-hoc scanning. NOT for real-time intrusion detection or incident response — use your SIEM. NOT for infrastructure/network security — this covers application code only.

  • Write your own skill

    viktorbezdek/skillstack/skillstack-workflows/skills/write-your-own-skill Skill

    15★ repo

    Meta-workflow for creating your own Claude Code skill that actually activates when needed and delivers genuine value. Starts with skill-creator as the canonical starting point, adds elicitation frameworks when the skill is for a human/domain area (interviewing, research, therapy-adjacent), designs the examples that will illustrate the skill (example-design), aligns with repo conventions (consistency-standards), writes structural validation tests before the content (test-driven-development), audits the draft against anti-patterns (critical-intuition), and generates the README with scenario tables (documentation-generator). Use when creating any new Claude Code skill that you want to be activation-reliable, well-scoped, and maintainable. NOT for quick-and-dirty prompts — use prompt-engineering directly.

  • Test driven development

    viktorbezdek/skillstack/test-driven-development/skills/test-driven-development Skill

    15★ repo

    Guides the Test-Driven Development methodology: the Red-Green-Refactor cycle of writing failing tests before implementation code, then making them pass with minimal code, then refactoring. Use when the user asks to do TDD, practice test-driven development, follow red-green-refactor, write tests first, apply test-first methodology, or implement a feature using TDD workflow with pytest, Vitest, ERT, or Zod. NOT for choosing or setting up test frameworks (use testing-framework), NOT for finding and fixing bugs or analyzing stack traces (use debugging), NOT for reviewing existing code or PRs (use code-review).

  • Testing framework

    viktorbezdek/skillstack/testing-framework/skills/testing-framework Skill

    15★ repo

    Test framework router and infrastructure setup across multiple languages and platforms. Use when the user asks to choose a test framework, scaffold test infrastructure, add focused unit/integration/E2E/accessibility coverage, or integrate tests into CI/CD. Covers Rust, TypeScript/React, PHP/TYPO3, Shell, Playwright, accessibility, mutation, and fuzz testing as selectable modules. NOT for TDD methodology or red-green-refactor workflow (use test-driven-development), NOT for diagnosing and fixing bugs or analyzing errors (use debugging), NOT for reviewing existing code or PRs (use code-review).

  • A11y test

    zivtech/accessibility-skills/.agents/skills/a11y-test Skill

    15★ repo

    Use when you need to run real accessibility tests — Playwright keyboard interactions, axe-core scanning, visual regression, and WCAG 2.2 compliance checks. The measurement layer that feeds evidence into a11y-critic reviews.

  • Webapp testing

    adryanmoldokkr32-pixel/anthropics-skills/skills/webapp-testing Skill

    no license15★ repo

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    The same file is in 45 other repositories

  • Principles

    hellotern/Sextant/skills/principles Skill

    15★ repo

    Fallback for general coding work that does not match any specific sextant sub-skill. Use for lightweight tasks: config changes, style fixes, utility functions, one-off scripts, or tasks too small to warrant a dedicated workflow. All dedicated sub-skills take priority over this one — check these first: sextant:fix-bug (broken behavior), sextant:debug (unknown bug location), sextant:add-feature (new functionality), sextant:modify-feature (changing existing behavior), sextant:review-code (evaluating code), sextant:write-tests (test coverage), sextant:refine-requirements (ambiguous scope), sextant:plan (multi-step sequencing), sextant:ship (release prep), sextant:migrate (cross-module upgrade), sextant:security (vulnerability audit). Only use this skill when none of the above match.

  • Write tests

    hellotern/Sextant/skills/write-tests Skill

    15★ repo

    You MUST use this skill before writing any test cases or adding test coverage. Use when the goal is to verify code behavior through tests — new tests, missing coverage, or a reproduction test after a bug fix. Stronger signals: "write tests", "add tests", "unit test", "integration test", "test coverage", "TDD", "test this function", "add a regression test". Also apply automatically after completing sextant:fix-bug, before marking the bug as resolved.

  • St test

    mumez/smalltalk-dev-plugin/skills/st-test Skill

    15★ repo

    Run SUnit tests in the running Pharo image. Use when verifying changes after import, or when checking results for a specific test class or package.

  • Android testing

    piyushverma0/android-agent-skills/skills/android-testing Skill

    15★ repo

    Android testing for AI agents. Use this skill whenever writing unit tests, integration tests, UI tests, ViewModel tests, Repository tests, DAO tests, Compose UI tests, Hilt testing, @HiltAndroidTest, TestCoroutineDispatcher, runTest, turbine Flow testing, MockK, Mockito, FakeRepository, Robolectric, Espresso, Compose testing semantics, screenshot tests, Roborazzi, JUnit 4/5, test doubles, test dispatchers, MainCoroutineRule, or any testing in Android. Always apply before writing any test class. Production apps require tests.

  • Ci cd android

    piyushverma0/android-agent-skills/skills/ci-cd-android Skill

    15★ repo

    CI/CD pipeline for Android AI agents. Use this skill whenever setting up GitHub Actions for Android, automated testing in CI, APK/AAB build automation, Play Store deployment automation, Fastlane for Android, code quality checks in CI, lint in pipeline, unit test automation, instrumented test automation, Firebase Test Lab integration, code signing in CI, artifact upload, pull request checks, or any continuous integration/deployment for Android.

  • Read only gh pr review

    jawwadfirdousi/agent-skills/read-only-gh-pr-review/skills/read-only-gh-pr-review Skill

    no license15★ repo

    Review backend pull requests for correctness, security, performance, maintainability, and test coverage using GitHub CLI plus local repository inspection. Use when asked to review service-layer/API/database changes, audit backend branch diffs, summarize backend risk, or produce actionable must-fix/should-fix feedback.

  • Go testing mistakes

    v0lka/skills/development/idiomatic-go/go-testing-mistakes Skill

    15★ repo

    Guides the agent to avoid common Go testing mistakes when writing or reviewing test code. Covers test categorization (build tags, env vars, short mode), race detection, test execution modes (parallel, shuffle), table-driven tests, avoiding sleeps in tests, handling the time API deterministically, using httptest/iotest utility packages, writing accurate benchmarks, and leveraging Go testing features (coverage, external test packages, utility functions, setup/teardown). Use when writing, reviewing, or refactoring Go tests, benchmarks, or test helpers, or when setting up CI test pipelines for Go projects.

  • Tdd

    spences10/skills/tdd Skill

    no license15★ repo

    Test-driven development with a red-green-refactor loop. Use when explicitly asked for TDD, red-green-refactor, test-first development, or integration-test-led feature work.

  • Dataops cicd pipeline review

    ivanshamaev/de-agent-skills/group_skills/infra_dataops_group_skills/dataops_cicd_pipeline_review Skill

    no license15★ repo

    DataOps CI/CD pipeline review — pipeline stages for data projects (lint/test/build/scan/deploy), trunk-based vs GitFlow branching, environment promotion (dev→staging→prod), artifact versioning (Docker image tags/dbt manifest), deployment gating (DQ checks/smoke tests/manual approval), rollback strategy, pipeline observability (DORA metrics), reusable workflow patterns, monorepo vs polyrepo CI strategy

  • Dbt starrocks testing

    ivanshamaev/de-agent-skills/group_skills/starrocks_group_skills/dbt_starrocks_testing Skill

    no license15★ repo

    dbt + StarRocks testing — generic tests (not_null/unique/accepted_values/relationships), singular tests (custom SQL assertions), source freshness tests (loaded_at_field), StarRocks-specific volume and freshness tests, dbt-expectations integration, test severity (warn vs error), store_failures for debugging failed tests, ANALYZE before test runs, partition-scoped test SQL

  • Testing

    byronxlg/skillfold/library/skills/testing Skill

    15★ repo

    Write and reason about tests, covering behavior, edge cases, and errors.

  • Testing

    alexander-danilenko/cortex-ai-skills/skills/testing Skill

    14★ repo

    Apply these opinionated testing conventions whenever writing, reviewing, or planning tests: what earns a test and what is coverage theatre, asserting outputs rather than mock calls, the three modes (functional, performance, security), naming and isolation rules, where to mock, and reporting findings for coverage rather than self-filtering. Includes house Jest standards for NestJS unit and contract tests, TDD discipline, and test-report structure.