Explore skills
Showing 46531–46560 of 77104 skills
Human review protocol for whether AI output is grounded in its sources: claim-by-claim attribution, hallucination classes, citation verification, sampling that is defensible, and a recorded attestation because groundedness cannot be fully automated. Also covers the responsible-AI pass - harmful output, bias, disclosure and privacy. Use when reviewing a RAG or summarisation feature, when factuality matters more than fluency, or when an eval suite needs the human check it cannot replace.
jaktestowac/awesome-copilot-for-testers
Stars: 122Claude CodeCodexAnalyzes technical debt in codebases, test suites, architecture, dependencies, and delivery workflows using observable signals. Use when auditing repository health, explaining slow delivery or flaky tests, prioritizing refactoring, or building an evidence-based remediation roadmap with risk, effort, and ROI. Use when user asks for technical debt analysis, repository audit, or refactor planning.
jaktestowac/awesome-copilot-for-testers
Stars: 122Claude CodeCodexDrives implementation test-first through red-green-refactor cycles: one failing test, the minimal code to pass it, then cleanup under green. Use before writing production code for a new behavior, and whenever the request mentions TDD, test-driven, test-first, red-green-refactor, "write the test first", "start with a failing test", or reproducing a bug with a test before fixing it. Also use when implementation keeps landing before anyone knows how it will be verified.
jaktestowac/awesome-copilot-for-testers
Stars: 122Claude CodeCodexRuns the red-green-refactor loop with a compact set of rules: one failing test, the minimal code to pass it, cleanup under green. Use for routine test-first work on a single behavior or a small bug fix, and when the request mentions TDD, test-first, red-green-refactor, or writing the test before the code. For multi-unit features, outside-in double loops, legacy code without tests, or a session that needs a written cycle log, use the test-driven-development skill instead.
jaktestowac/awesome-copilot-for-testers
Stars: 122Claude CodeCodexTests the customization assets themselves - skills, prompts, custom agents, instructions - the way a product is tested: activation cases that check an asset fires when it should and stays quiet when it should not, output-contract cases, safety cases, collision cases between assets competing for the same trigger, a weighted rubric scored blind, and a baseline-versus-candidate gate before an edit ships. Use when a skill is edited and nobody knows whether behaviour changed, when two skills fight over the same request, when a description is being tuned for discoverability, when a collection has grown past manual spot-checking, or when the request mentions skill evals, prompt regression, or "does this skill actually work".
jaktestowac/awesome-copilot-for-testers
Stars: 122Claude CodeCodexValidates API responses against OpenAPI or JSON Schema, detects breaking changes between spec versions, and builds consumer-driven contract checks. Use when an API has a published spec, when a backend change might break a client, when API tests assert only status codes, or when mocked fixtures need a guard against drifting from the real service.
jaktestowac/awesome-copilot-for-testers
Stars: 122Claude CodeCodexBuilds an offline eval suite for LLM-powered features: golden reference cases per prompt template, deterministic scoring where possible, a regression gate on prompt, model and retrieval changes, and CI wiring with promptfoo, Vitest or deepeval. Use when a product ships prompts, agents or RAG, when a model or prompt upgrade needs a regression check, when LLM output is currently verified by someone eyeballing it, or when asked how to test a feature whose output is non-deterministic.
jaktestowac/awesome-copilot-for-testers
Stars: 122Claude CodeCodexCuts AI tells from what the agent says about its own work: completion claimed without a run, invented file paths and API names, terminal output that was never produced, findings with no location, percentages with no denominator, absence claimed from one grep, effort narration instead of results, hedge stacking, buried blockers, puffery in a bug title. Use whenever reporting a result, a fix, a review finding, a test outcome, a coverage or flake number, a root cause, or a release recommendation, and when the request mentions "prove it", "did you actually run it", "be specific", "no fluff", "stop hedging", or "is this real". Must always apply to answers about your own work.
jaktestowac/awesome-copilot-for-testers
Stars: 122Claude CodeCodexCuts AI tells from test code: tests that pass without proving anything, tautological assertions, mock-only tests, hardcoded waits, coverage theater, vague names, swallowed errors, retries used as fixes. Use whenever test code is written, changed, or reviewed, including tests produced as a side effect of a feature task, and when the request mentions "review these tests", "are these tests any good", "this test always passes", "this suite is flaky", or "clean up these tests". Must always apply to test code.
jaktestowac/awesome-copilot-for-testers
Stars: 122Claude CodeCodexCompares implementation evidence against acceptance criteria and shows what is met, partial, missing, or untestable. Use when checking feature readiness, preparing QA sign-off, or turning criteria into a concrete verification matrix without inventing missing behavior.
jaktestowac/awesome-copilot-for-testers
Stars: 122Claude CodeCodexWrites and reviews focused, deterministic unit tests that verify behavior through public interfaces instead of implementation details. Use whenever tests are added to code that already exists, and when the request mentions unit tests, test coverage, edge cases, mocks or test doubles, "add tests for this function", "cover this module", "these tests are flaky", or "this test breaks every refactor". Also use when reviewing an existing suite for brittleness, weak assertions, or missing boundary cases.
jaktestowac/awesome-copilot-for-testers
Stars: 122Claude CodeCodexWrites a few solid unit tests, using a compact set of rules for structure, assertions, determinism, and edge cases. Use for routine everyday testing of a single function, class, or small module, or for a quick sanity check on tests someone just wrote. For legacy backfills, flaky-suite investigations, deep test-double design, or a full suite review, use the writing-unit-tests skill instead.
jaktestowac/awesome-copilot-for-testers
Stars: 122Claude CodeCodexScrape leads from multiple platforms using Apify Actors.
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexEnd-to-end Android APK red-team pipeline
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexAutomated cleanup of unused AWS resources to reduce costs
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexStore and rotate secrets in AWS Secrets Manager.
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexText and document translation with REST-style clients.
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexAzure Event Hubs SDK for .NET.
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexAzure Resource Manager SDK for API Management in .NET.
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexAzure Resource Manager SDK for Fabric in .NET.
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexAzure Resource Manager SDK for Cosmos DB in .NET.
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexAzure Resource Manager SDK for Redis in .NET.
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexAzure Resource Manager SDK for Azure SQL in .NET.
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexBlockRun works with Claude Code and Google Antigravity.
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexMaintenance orchestrator for the brooks-lint plugin itself.
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexExpert C4 Container-level documentation specialist.
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexProject Guidelines Skill (Example)
Ronak1167/aura-vega-tv
Stars: 0Claude CodeCodexUse when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
jtrackingai/analytics-tracking-automation
Stars: 145Claude CodeCodexUse when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group approval.
jtrackingai/analytics-tracking-automation
Stars: 145Claude CodeCodexUse when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
jtrackingai/analytics-tracking-automation
Stars: 145Claude CodeCodex