All authors
Claude Skills by yeaight7
github.com/yeaight7200 skills5 installs224 views
- Dependency CleanupUse when package manifests carry unused or redundant third-party dependencies that slow builds, widen the security surface, or complicate updates.Votes: 0GitHub stars: 6
- Deploy Pipeline RunbookUse when a release spans multiple systems or vendors, order of operations matters with rollback planned up front, or a failed step in one system could corrupt state in a downstream system.Votes: 0GitHub stars: 6
- Dispatching Parallel AgentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesVotes: 0GitHub stars: 6
- Doc Consistency CheckUse when documentation may have rotted against the code -- files were renamed or moved, scripts or env vars changed, or readers report commands and paths from the docs that no longer work.Votes: 0GitHub stars: 6
- Experiment Tracking ReviewUse when reviewing ML training code to confirm a run could be reconstructed later -- hyperparameters, metrics, data references, and artifacts logged, not just printed to stdout.Votes: 0GitHub stars: 6
- Failure TriageUse when confronted with an unknown failure in CI or production, before committing to a deep debugging approach.Votes: 0GitHub stars: 6
- Flaky Test InvestigationUse when tests pass and fail intermittently without code changes, or a test passes alone but fails in the full suite.Votes: 0GitHub stars: 6
- Github Ci Failure TriageUse when a GitHub PR shows failing checks and a clean failure readout is needed before changing any code.Votes: 0GitHub stars: 6
- Graphifyany input (code, docs, papers, images) → knowledge graph → clustered communities → HTML + JSON + audit report. Use when the user wants to build, inspect, or query a cross-file knowledge graph from code, docs, papers, images, or videos with upstream graphify.Votes: 0GitHub stars: 6
- Hard Won Skill ExtractorUse when a tricky bug, non-obvious workaround, hidden gotcha, or undocumented behavior took real debugging effort to discover and should be captured as a reusable learned skill.Votes: 0GitHub stars: 6
- Incident ReadoutUse when a bug fix or complex debugging session concludes and a blameless post-mortem summary is needed for human review.Votes: 0GitHub stars: 6
- Incremental MigrationUse when migrating APIs, libraries, or patterns across a large codebase and a single mega-commit would be too risky to review or merge.Votes: 0GitHub stars: 6
- Log Driven DiagnosisUse when debugging complex runtime failures, distributed systems, or issues where a local debugger cannot be attached.Votes: 0GitHub stars: 6
- Mcp Server BuilderDesign high-quality MCP servers around workflows, narrow schemas, context-aware outputs, and actionable errors. Use when building or reviewing MCP tools for real agent tasks.Votes: 0GitHub stars: 6
- Memory Build WorkflowUse when a user needs to build or refresh persistent graph memory from a mixed corpus and the right path may include graphify, incremental update, or helper conversion before ingestion.Votes: 0GitHub stars: 6
- Memory Optimization WorkflowUse when deciding the lowest-cost context path for a mixed corpus, especially when choosing among direct reading, helper conversion, graph build, graph update, or graph query.Votes: 0GitHub stars: 6
- Memory Query WorkflowUse when a graph already exists and the user needs retrieval, tracing, explanation, or gap detection from graph memory before reopening the full corpus.Votes: 0GitHub stars: 6
- Metric Impact AnalyzerUse when a change may affect metrics, semantic models, dashboards, reporting, or stakeholder-facing KPIs and you need to know whether business meaning or downstream BI assets change.Votes: 0GitHub stars: 6
- Minimal ReproductionUse when a bug must be isolated from a large application into a standalone, runnable script or single test case.Votes: 0GitHub stars: 6
- Ml Leakage CheckUse when reviewing ML preprocessing or feature pipelines for target leakage -- validation metrics look suspiciously good, transformers are fitted before splitting, or features may not exist at prediction time.Votes: 0GitHub stars: 6
- Model Evaluation ReportingUse when writing or reviewing a model evaluation report -- accuracy is being quoted alone, or stakeholders need failure modes, segment performance, and business trade-offs made explicit.Votes: 0GitHub stars: 6
- Model RoutingUse when selecting a model for a new task or subagent, deciding whether to escalate after a failed attempt, or designing a multi-agent pipeline with mixed task complexity.Votes: 0GitHub stars: 6
- Naming And Structure CleanupUse when naming conventions or file structure drift across a project and need to be made consistent without changing business logic.Votes: 0GitHub stars: 6
- No FluffUltra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "no fluff", "be concise", "use less tokens", or similar.Votes: 0GitHub stars: 6
- Parallel Execution EngineUse when latency matters and several independent tasks can run at once -- a bounded implementation or investigation that needs waves of concurrent workers, not a persistent completion loop or stage-based orchestration.Votes: 0GitHub stars: 6
- Persistent Completion LoopUse when a task must run to verified completion rather than best effort -- the user says "don't stop", "must complete", "finish this", or "keep going until done", or the work spans multiple iterations and needs reviewer sign-off before being called done.Votes: 0GitHub stars: 6
- Pr Review Ci LoopUse when a pull request needs one bounded review and CI triage cycle with explicit approval before edits or remote writes.Votes: 0GitHub stars: 6
- Pre Release VerificationUse when a release candidate needs final checks before tagging, publishing, or production deployment.Votes: 0GitHub stars: 6
- Readme HardeningUse when a README cannot be followed verbatim -- setup or test commands fail or are vague, environment requirements are unstated, or a new engineer or agent cannot bootstrap the project quickly.Votes: 0GitHub stars: 6
- Receiving Code ReviewUse when receiving code review feedback, before implementing suggestions — requires technical verification and reasoned pushback, not performative agreement or blind implementation.Votes: 0GitHub stars: 6
- Regression BisectingUse when a bug was recently introduced but you don't know which commit caused it.Votes: 0GitHub stars: 6
- Reproducible Training RunsUse when reviewing or modifying ML training scripts that must produce identical results across runs or machines -- runs with the "same" config differ, or a past result must be reconstructed exactly.Votes: 0GitHub stars: 6
- Requesting Code ReviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements.Votes: 0GitHub stars: 6
- Requirements ClarifierUse when an implementation request is vague or underspecified and needs structured clarification before coding -- the user says "interview me", "ask me everything", "don't assume", or wants to avoid "that's not what I meant" outcomes from autonomous execution.Votes: 0GitHub stars: 6
- Review Comment Style MiningUse when mining PR review comments and text diffs for reusable writing, documentation, tone, and editorial improvement patterns.Votes: 0GitHub stars: 6
- Risk Based ReviewUse when reviewing a PR or your own change plan and you need to decide how much scrutiny it deserves -- the diff touches auth, payments, crypto, migrations, or core shared code, or you are unsure where to focus limited review attention.Votes: 0GitHub stars: 6
- Safe RefactorUse when code needs restructuring without changing observable behavior.Votes: 0GitHub stars: 6
- Semantic Layer Change ReviewUse when a change touches dbt semantic models, metrics, saved queries, or other semantic-layer YAML -- especially when an existing metric's expression, aggregation, filters, or dimensions are modified.Votes: 0GitHub stars: 6
- Skill Authoring GuideCreate or refactor high-quality skills with lean frontmatter, progressive disclosure, and optional bundled helpers. Use when authoring reusable agent workflows.Votes: 0GitHub stars: 6
- Sql Business Logic ReviewUse when reviewing SQL that affects reporting, metrics, transformations, financial logic, product logic, or stakeholder-facing outputs -- especially when a query still runs fine but its business meaning may have drifted.Votes: 0GitHub stars: 6
- Strategic Context CompactionUse when deciding whether to compact agent context -- the window is filling up, you are about to switch from one phase to another (research, planning, implementation, debugging), a failed approach left dead-end reasoning, or a previous mid-task compaction lost critical state.Votes: 0GitHub stars: 6
- Subagent Team OrchestrationUse when a task is too large or too mixed for one agent -- it splits into research, planning, implementation, review, and verification stages, needs different specialties, or has parallelizable branches that still share dependencies.Votes: 0GitHub stars: 6
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes.Votes: 0GitHub stars: 6
- Task IntakeUse at the start of a new task -- before writing or editing code -- when the request is vague, the scope boundaries are unclear, or the acceptance criteria for "done" have not been stated.Votes: 0GitHub stars: 6
- Test Driven DevelopmentUse when implementing any feature or bugfix, before writing implementation codeVotes: 0GitHub stars: 6
- Test Preserving RefactorUse when code needs restructuring and observable behavior must stay unchanged, with existing tests kept green at every step.Votes: 0GitHub stars: 6
- Training Pipeline DebuggingUse when an ML training run fails or misbehaves -- NaN losses, out-of-memory errors, shape mismatches, or a model that cannot fit even a single batch.Votes: 0GitHub stars: 6
- Tri Model ReviewUse when a request needs parallel external perspectives — combined backend and UI work, code review from multiple angles, or cross-validation where different models may disagree.Votes: 0GitHub stars: 6
- Writing PlansUse when you have a spec or requirements for a multi-step task, before touching code.Votes: 0GitHub stars: 6
- Plan Ledger Tasks YyloCreate a concise Product Development Requirement and one or more implementation-sized YYLO Ledger tasks when the user explicitly asks to plan or register work. Planning-only requests stay as external drafts; Ledger records and tasks are created only when the user explicitly asks to register the work or confirms when asked.Votes: 0GitHub stars: 6