SSO, RBAC & audit · Any model, your keys · No seat tax
Scores per-test flakiness from CI run history and quarantines the worst offenders via a skip-only PR.
kortix marketplace install kortix-starter:flaky-test-quarantine-skillcat memory/flaky-test-ledger.md 2>/dev/null || echo "(no ledger yet)"
gh issue list --repo {{target_repo}} --state open \
--search 'in:title "Flaky test quarantine tracker"' \
--json number,title,url
gh pr list --repo {{target_repo}} --state open \
--search 'in:title "test(quarantine)"' \
--json number,title,headRefName,statusCheckRollup,url
gh run list --repo {{target_repo}} --branch main --limit 50 \
--json databaseId,conclusion,createdAt,headSha,workflowName > /tmp/runs.json
# For each run since the ledger's last processed run_id, pull the per-test
# report artifact the workflow produces (JUnit/XML or equivalent).
gh api repos/{{target_repo}}/actions/runs/<RUN_ID>/artifacts \
--jq '.artifacts[] | select(.name | test("test-results|junit")) | .id'
gh api repos/{{target_repo}}/actions/artifacts/<ARTIFACT_ID>/zip > /tmp/artifact.zip
unzip -o /tmp/artifact.zip -d /tmp/artifact-<RUN_ID>
(test_name, file, outcome, run_id, head_sha, timestamp) tuples. Only process runs newer than the ledger's last processed
run_id — don't re-score history already folded in.head_sha (a rerun) or of near-identical code (no change
touching the test or its subject between runs).{{quarantine_threshold}} that isn't already marked quarantined in the
ledger.// Jest / Vitest
it.skip('does the thing', () => { ... }); // FLAKY: quarantined <date>, see #<issue>
# Pytest
@pytest.mark.skip(reason="FLAKY: quarantined <date>, see #<issue>")
def test_does_the_thing(): ...
// Go
func TestDoesTheThing(t *testing.T) {
t.Skip("FLAKY: quarantined <date>, see #<issue>")
...
}
BRANCH="test/quarantine-$(date +%Y-%m-%d)"
git checkout -b "$BRANCH" origin/main
git add -p # stage only the skip-marker changes
git commit -m "test(quarantine): skip $(date +%Y-%m-%d) flaky tests"
git push origin "$BRANCH"
gh pr create --repo {{target_repo}} --base main --head "$BRANCH" \
--title "test(quarantine): skip flaky tests ($(date +%Y-%m-%d))" \
--label flaky-test \
--body "Quarantines the tests below at or above the flakiness threshold.
Each is skipped, not deleted, with a link to run evidence. See tracking issue
#<issue-number>. A human owns the merge and the eventual de-quarantine."
Flaky test quarantine tracker.
Create it if it doesn't exist; otherwise edit its body to the current state:gh issue create --repo {{target_repo}} \
--title "Flaky test quarantine tracker" \
--label flaky-test \
--body "<table: test, file, flakiness score, quarantined since, PR>"
# or, if it already exists:
gh issue edit <ISSUE_NUMBER> --repo {{target_repo}} --body "<updated table>"
{{alert_channel}}: how many tests newly crossed the threshold this
run, how many remain quarantined from before, and any tests stable enough to
recommend de-quarantining — with links to the PR and the tracking issue.
Never post raw run logs or the full ledger to Slack.memory/flaky-test-ledger.md (see <ledger-format>),
then open and self-merge a scoped change request for the ledger update only.The role-to-grant policy, extra-scrutiny cases, the approval handshake, and how an applied grant gets logged.
Get a complete picture of any company or person before outreach. This skill always works with web search, and gets significantly better with enrichment and CRM data.
Daily runbook for budget pacing, CPA/ROAS drift, underperformer detection, and anomaly flags across Google Ads and Meta Ads, plus how to rank and word optimization recommendations.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Extract-and-match runbook for incoming vendor invoices: line-item extraction, PO/prior-invoice matching, duplicate + overcharge detection, and the ledger + approval hand-off.
Search, dedupe against the seen-mentions ledger, classify sentiment and notability, and post a digest with suggested response drafts — the daily brand-monitor runbook.