RadarTopicsBuildersWeeklyReads
Open Source Radar
shenli/

distributed-system-testing

GitHub

AI-agent skills for distributed-systems testing

225stars
12forks
1issues
MITlicense
2026since
Star historydaily snapshots by VibeCrowd

Collecting history — the radar snapshots this repo daily. The trend line appears after 3 days of data (1 so far).

Alternatives & relatedmatched by topic overlap
DietrichGebert/
ponytail
▲ 4.8k/wk

Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.

96k5.3kJavaScriptnew
nexu-io/
open-design
▲ 1.3k/wk

🎨 The open-source Claude Design alternative. 🖥️ Local-first desktop app. 🖼️ Your coding agent becomes the design engine: prototypes, landing pages, dashboards, slides, images & video — real files, HTML/PDF/PPTX/MP4 export. 🤖 Claude Code / Codex / Cursor / Gemini / OpenCode / Qwen & 20+ CLIs via BYOK.

84k9.7kTypeScript
ComposioHQ/
awesome-claude-skills
▲ 585/wk

A curated list of awesome Claude Skills, resources, and tools for customizing Claude AI workflows

72k8.1kPython
sickn33/
agentic-awesome-skills
▲ 328/wk

AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,000+ agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.

44k6.5kPython
wshobson/
agents
▲ 148/wk

Multi-harness agentic plugin marketplace for Claude Code, Codex CLI, Cursor, OpenCode, GitHub Copilot, and Gemini CLI

38k4.1kPython
topoteretes/
cognee
▲ 254/wk

Cognee is the open-source AI memory platform for agents. Give your AI agents persistent long-term memory across sessions with a self-hosted knowledge graph engine.

30k2.9kPython
Agent skills inside · 2
All skills →
designing-distributed-system-testsUse when designing a test plan for a distributed or stateful system — anything with persistence, replication, consensus, retries, idempotency, async messaging, multi-tenancy, or partial failure. Plans are claim-driven: investigate the product's claimed guarantees first, then design hypotheses and scenarios that try to falsify those claims under fault. Handles change-scoped plans (a commit / PR / feature) and project-wide plans (holistic, with existing-test inventory and gap analysis). Also use when asked to write a stability plan, fault matrix, release-validation plan, durability / partition /Testing & QAexecuting-distributed-system-testsUse when running a previously designed distributed-systems test plan against a real or simulated cluster — driving fault injection, workload, chaos scenarios, linearizability / consistency runs, durability, partition, crash-recovery, upgrade, performance/SLO runs, tenant isolation runs, boundary or authz runs, fairness / noisy-neighbor runs, or release validation. Also use when asked to "execute the plan", "reproduce a distributed bug", "run stability tests", "drive chaos", "validate a release end-to-end", "run the tenant isolation tests", or when a plan file exists at docs/testing-plans/ or aTesting & QA
SharePost on XLinkedIn
All trending reposRevenue-verified startups →