Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- 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
- GradersNo description providedVotes: 0GitHub stars: 7
- GradersNo description providedVotes: 0GitHub stars: 7
- GradersNo description providedVotes: 0GitHub stars: 7
- Nix For DevUse this when setting up Nix for a development project (devShell + package build) and you care about `nix develop` being fast. Covers the zero-inputs flake.nix + npins + default.nix/shell.nix layout, sub-flakes for non-user-facing Nix, and language-specific recommendations.Votes: 0GitHub stars: 11
- Nix CiUse this when setting up CI for a GitHub repository — offers GitHub Actions or Vira depending on the projectVotes: 0GitHub stars: 11
- Plans> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking. **Goal:** Add a `qa-report` skill that turns any finished run (`/qa-test`, `/qa-test-fast`, `/qa-verify-fix`, `/qa-regression`, `/qa-smoke`) into **one** brief, char-budgeted tracker comment and **one** human-readable HTML page. Every template lives in one folder, and the f...Votes: 0GitHub stars: 2
- Translate Arabic FinanceTranslate supplied finance analysis to Saudi institutional Arabic (ar-SA), keeping RTL text intact. For Parallax reports, use the analysis skill's lang=. NOT for new analysis or non-finance text.Votes: 0GitHub stars: 5
- Index On Search EngineRegister a (new) website or subdomain on Google + Bing so it gets crawled and indexed, using the claude-in-chrome browser against Ivan's already-logged-in Google Search Console and Bing Webmaster Tools. Use when the user asks to "index this on Google/Bing/Brave", "register on search console", "submit the sitemap", "get this site indexed", "why isn't my site on Google", "set up search engine indexing", or after launching a new site/subdomain under websites/. Covers the live-and-crawlable prere...Votes: 0GitHub stars: 2
- QaUse after code changes, before releases, or when testing features - runs the right level of QA based on what changedVotes: 0GitHub stars: 13
- Frontend Testing Frontend Experience ValidationGather evidence for critical frontend journeys across behavior, accessibility, visual regressions, network resilience, and performance without requiring a fixed test tool.Votes: 0GitHub stars: 4
- Angular Versioning Angular V22 Roadmap AlignmentAlign Angular 22 recommendations with official roadmap status and avoid premature adoption of unfinished work. For Angular 22 projects and 21-to-22 upgrade planning.Votes: 0GitHub stars: 4