Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- Identify BugsProactively discover latent bugs in an existing codebase (correctness, error handling, null and boundary handling, async, concurrency, state, resource management), keep only high-confidence ones, verify each where a seam exists, and use ghx to discard anything already tracked by a GitHub issue, searching for another candidate until nothing useful remains. Use when the user says /identify-bugs, "find bugs", "hunt for bugs", "look for latent bugs", "bug sweep", "what is broken", or wants a peri...Votes: 0GitHub stars: 10
- Git Commit StagedGenerate a Conventional Commits-formatted commit message from only the staged changes, leaving unstaged changes untouched. Use when the user says "commit staged", "commit staged changes", or wants to commit only what is already staged.Votes: 0GitHub stars: 10
- Fix IssueOrchestrate a bug fix from issue to PR by delegating to reproduce-issue, create-implementation, validate-implementation, and create-pr.Votes: 0GitHub stars: 10
- Find Coverage GapsIdentify files and modules with missing or insufficient test coverage, ranked by churn and complexity, and suggest what to test first.Votes: 0GitHub stars: 10
- Create TestsCreate a test plan and test cases covering acceptance criteria, edge cases, and failure scenarios.Votes: 0GitHub stars: 10
- Create PrCreate a GitHub pull request with a structured description linked to its issue, with acceptance criteria coverage, the design decisions the PR implements, and reviewer assignment. Embeds visual proof that was captured beforehand by /validate-implementation (single asset, or a before/after pair for bug fixes) by reading the proof manifest; create-pr is a consumer and does not capture recordings itself. If no proof was captured, it omits the Visual proof section and suggests running /validate-i...Votes: 0GitHub stars: 10
- Create PlanCreate an implementation plan with phases, milestones, dependencies, and risks from a specification or requirements document.Votes: 0GitHub stars: 10
- Create LearningsCapture learnings after completing a feature, sprint, or project in a structured retrospective format.Votes: 0GitHub stars: 10
- Create IssueCreate a GitHub issue with background, prioritized acceptance criteria (Must/Should), and a justified time budget.Votes: 0GitHub stars: 10
- Create ImplementationImplement a feature or task following the specification and plan, producing working, tested code.Votes: 0GitHub stars: 10
- Skill TestValidation test runner for MOOLLM skills. **Status: DESIGN** — harness and per-skill config to be implemented. - **Runner:** Discovers skills with `test.yml` or `.skill-test.yml`; runs entrypoint (pytest or script); passes env; reports pass/fail and drift. - **Per-skill:** Each skill declares entrypoint, runner type, env, marks. Tests can live inside the skill (e.g. `cursor-mirror/tests/`). - **Relation:** skill-snitch = audit/security; skill-test = validation/regression. Both use cursor-mirr...Votes: 0GitHub stars: 56
- Triaging Test FailuresTriage the failures in a Qase test run: cluster them by error signature, separate real product bugs from automation, environment, and flaky noise, and file defects. Use when the user asks to triage a run; why a run, a build, or the tests in it failed; why last night's or the latest run failed or is red; what broke; to investigate, group, cluster, or classify failures; which failures are real bugs versus noise; or to file defects for a failed run.Votes: 0GitHub stars: 7
- Reporting Quality PulseBuild a visual "Quality Pulse" report card for a Qase project over any period the user chooses — daily, weekly, biweekly, monthly, sprint, or a custom date range. A styled HTML card summarizing test execution, pass rate, defect backlog, case activity, and active users for that window. Use this whenever the user asks for a quality pulse, QA pulse, quality/test report card, test health summary, sprint QA snapshot, release health check, or any "how is testing going" overview for a Qase project o...Votes: 0GitHub stars: 7
- Assessing Release ReadinessProduce an evidence-backed go / no-go assessment for a Qase release scope — a milestone, a test plan, or a set of runs. Use when the user asks whether they are ready to ship, release, or cut a version; for a go/no-go, a release sign-off, or a quality gate; what is blocking the release or holding it up; whether a milestone or sprint is done; how a release is tracking; or whether it is safe to deploy.Votes: 0GitHub stars: 7
- Analyzing Test FlakinessFind genuinely flaky tests in a Qase project — cases that both pass and fail — and separate them from tests that are simply broken. Use when the user asks which tests are flaky, unreliable, unstable, intermittent, or non-deterministic; about test stability, flakiness, or the flake rate; which tests pass sometimes and fail other times, or fail randomly; which tests to quarantine, mute, or flag as flaky; or whether a specific test is flaky or a real regression.Votes: 0GitHub stars: 7
- Analyzing Test CoverageFind where a Qase project's test coverage is thin. Use when the user asks about test coverage or coverage gaps; what isn't tested, untested areas, or what is missing tests; which cases are still manual, not automated, or yet to be automated; which cases have never been run or executed; which suites are empty, thin, or hold no cases; how much of the project is automated; which cases are stale or outdated; or wants test cases drafted to close a gap.Votes: 0GitHub stars: 7
- Analyzing Change ImpactAnalyze what a feature branch changes and produce a QA-facing impact analysis plus a regression/new checklist, grounded in the project's existing Qase cases. Use when the user asks for an impact analysis, change impact, risk analysis, or blast radius of a branch or PR; what QA should test for these changes; a QA checklist or test plan for a branch; what could break; or which existing tests to re-run before merging. Reads the repository diff and Qase; renders an HTML report.Votes: 0GitHub stars: 7
- GradersNo description providedVotes: 0GitHub stars: 7
- GradersNo description providedVotes: 0GitHub stars: 7
- GradersNo description providedVotes: 0GitHub stars: 7