Repository-Explorer

Zavelinski · Repositories und repräsentative Skills - Seite 2

Repository-Ansicht von 37 gesammelten Skills in 34 GitHub-Repositories.

#13Zavelinski/cite-guard1 Skills

cite-guardFor factual or external claims, attach a source before asserting; mark anything you cannot verify as unverified; refuse to state ungrounded facts as if certain. Use when answering with facts, versions, APIs, prices, dates, or quotes - anywhere a…30. Juni 2026

#14Zavelinski/retrieval-router1 Skills

retrieval-routerDecide per task whether to RETRIEVE targeted slices (grep/embeddings, read only what's relevant) or LOAD broad context (whole files/dirs), instead of always dumping the codebase. Use on large repos or long docs when deciding what to put in context. Trigger…30. Juni 2026

#15Zavelinski/reflexion1 Skills

reflexionAfter a failed attempt (test fails, command errors, wrong output), write a short reflection on WHY it failed and what to change, then retry with that lesson in context, instead of blindly trying again. Use on the 2nd attempt at any failing task. Trigger with…30. Juni 2026

#16Zavelinski/tool-guard1 Skills

tool-guardBefore calling a tool, validate the arguments; after it returns, verify the output actually did what you intended before acting on it. Use on destructive or stateful tool calls (writes, deletes, deploys, API mutations, shell) and when chaining tool outputs.…30. Juni 2026

#17Zavelinski/dep-guard1 Skills

dep-guardBefore adding an import or install command, verify the package/module/API actually exists, instead of trusting a hallucinated name. Use whenever code adds a dependency, an import, or a `pip/npm/cargo install`. Catches hallucinated packages and typosquats…30. Juni 2026

#18Zavelinski/self-consistency1 Skills

self-consistencyFor a hard reasoning step or a high-stakes decision, sample several independent solutions and take the consistent answer instead of trusting one shot. Use on tricky bugs, ambiguous design calls, math/logic, or any answer where being wrong is expensive.…30. Juni 2026

#19Zavelinski/headless-mcp-bridge1 Skills

headless-mcp-bridgeMake scheduled, cron, and headless Claude Code runs reach your MCP servers, which they otherwise silently drop. Use when setting up a scheduled agent / routine that needs a custom MCP (recall, a DB connector, etc.), or when an unattended run "can't see" tools…30. Juni 2026

#20Zavelinski/multi-repo-context1 Skills

multi-repo-contextWork across several repos at once without losing track of which is which. Use when a task spans a frontend + backend + infra repo, a service and its client, or a repo and a sibling dependency. Builds a scope manifest (repos, roles, boundaries, relationships)…30. Juni 2026

#21Zavelinski/run-cost1 Skills

run-costEstimate the token/cost of a whole TASK or WORKFLOW before running it, and propose a cheaper shape. Use before a big multi-step task, before launching a Workflow that fans out agents, or when the user is cost-sensitive. Works at task altitude (agent count x…30. Juni 2026

#22Zavelinski/orchestrate1 Skills

orchestrateRun a feature or fix through an opinionated plan -> spec -> build -> verify cycle with a hard approval gate, instead of hand-rolling subagent orchestration. Use for multi-step work where you want a plan and spec approved before any edit, and every step…29. Juni 2026

#23Zavelinski/mcp-warden1 Skills

mcp-wardenVet an MCP server BEFORE enabling it in Claude Code. Use before adding a third-party MCP, before pasting an mcp config, or to audit MCPs you already enabled. Produces a security & compatibility sheet, statically scans the server code/config as hostile data,…29. Juni 2026

#24Zavelinski/testsmith1 Skills

testsmithAdversarial, high-value test generation. Use when fixing a bug, hardening a function, or when an agent produced many shallow tests. Reproduces the bug with a failing test first, then runs a test-vs-mutant loop to produce FEW tests that actually catch defects,…29. Juni 2026