yeaight7
- 215 skills
- 0 followers
- 8 repo stars
- 6 days ago last updated
- ▌ Plan Ledger Tasks Yylo · yeaight7 bundleCreate 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.
- ▌ Training Pipeline Debugging 2 · yeaight7Use 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.
- ▌ Memory Optimization Workflow 2 · yeaight7Use 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.
- ▌ Subagent Team Orchestration 2 · yeaight7Use 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.
- ▌ Naming And Structure Cleanup 2 · yeaight7Use when naming conventions or file structure drift across a project and need to be made consistent without changing business logic.
- ▌ Review Comment Style Mining 2 · yeaight7 bundleUse when mining PR review comments and text diffs for reusable writing, documentation, tone, and editorial improvement patterns.
- ▌ Autonomous Delivery Pipeline 2 · yeaight7Use when the user wants end-to-end autonomous execution from a brief idea to working, verified code -- multi-phase work spanning requirements, planning, implementation, QA, and validation. Not for brainstorming, single focused changes, or quick fixes.
- ▌ Architecture Decision Records 2 · yeaight7Use when a significant architectural choice is being finalized, revisited, or reversed -- technology selection, structural patterns, or trade-offs that future maintainers or agents might unknowingly undo.
- ▌ No Fluff 2 · yeaight7Ultra-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.
- ▌ Repo Map 2 · yeaight7Use when the task is to understand an unfamiliar codebase, locate key entry points, or summarize architecture before editing.
- ▌ Task Intake 2 · yeaight7Use 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.
- ▌ Brainstorming 2 · yeaight7Use when starting any creative work — creating features, building components, adding functionality, or modifying behavior — before any implementation begins.
- ▌ Writing Plans 2 · yeaight7 bundleUse when you have a spec or requirements for a multi-step task, before touching code.
- ▌ Using Powerups 2 · yeaight7Use when starting work in a repository with Agent Powerups installed, when a task may match a reusable local skill, command, workflow, hook recipe, AGENTS.md template, or MCP feature.
- ▌ Pr Review CI Loop 2 · yeaight7Use when a pull request needs one bounded review and CI triage cycle with explicit approval before edits or remote writes.
- ▌ Defuddle 2 · yeaight7Use when the user provides a URL to a standard web page and clean Markdown extraction with Defuddle would reduce clutter and token cost.
- ▌ Graphify 2 · yeaight7 bundleany 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.
- ▌ Model Routing 2 · yeaight7Use 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.
- ▌ Data Quality 2 · yeaight7Use when adding or reviewing data quality tests for dbt models in warehouse-backed analytics projects. Covers dbt generic tests, singular tests (assert_*.sql), accepted-values macros, dbt_utils patterns, cross-system consistency tests, and warehouse-oriented validation. Use when writing data tests, creating assert_*.sql files, testing business logic, or validating referential integrity.
- ▌ Dbt Strategy 2 · yeaight7Use when creating or modifying dimensional dbt models in warehouse-backed analytics projects. Covers a four-layer warehouse architecture (sources/staging/core/marts), naming conventions, no-alias SQL rule, surrogate-key and missing-record patterns, incremental strategies, deduplication, and common project macros. Use when building fact tables, dimension tables, staging models, writing SQL, or designing tests.
- ▌ Handoff Discipline 2 · yeaight7Use when ending a session, handing a task back to the user, or approaching the context limit with work unfinished -- the next session or engineer must be able to resume the work instantly.
- ▌ Dbt Preflight 2 · yeaight7Use when a dbt change needs preflight before a PR, review, or merge -- changed models, snapshots, seeds, macros, or semantic YAML whose blast radius and test coverage are not yet known.
- ▌ Bug Hunt 2 · yeaight7Use when reproducing, isolating, and fixing a bug with the smallest safe change.
- ▌ Context Compression 2 · yeaight7 bundleUse when conversation context is bloated, constraints are being forgotten, or a compact handoff is needed before continuing work.
- ▌ Gh Address Comments 2 · yeaight7Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, then implement selected fixes.
- ▌ Context Minimization 2 · yeaight7Use when a task runs long and the context window is filling -- large files are being read whole, command output is flooding the transcript, or responses are getting verbose and slow.
- ▌ Risk Based Review 2 · yeaight7Use 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.
- ▌ Tri Model Review 2 · yeaight7Use 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.
- ▌ CI Failure Readout 2 · yeaight7Use when a CI pipeline has failed and the real error must be extracted from thousands of lines of noisy logs.
- ▌ Agent Runtime Patterns 2 · yeaight7 bundleUse when optimizing agent runtime loops, card packs, MCP session lifecycle, tool-call count, or multi-agent orchestration patterns.
- ▌ Change Impact Check 2 · yeaight7Use before submitting a PR or considering a task done to evaluate the blast radius of your changes -- you touched a public signature, a shared utility, a schema, or added config and need to know what else is affected.
- ▌
- ▌ Agent Session Forensics 2 · yeaight7 bundleUse when diagnosing agent session history, interrupted tool loops, missing tool results, timing bottlenecks, or subagent trace correlation.
- ▌ Context Docs 2 · yeaight7Use when a subsystem needs persistent context for future agents or engineers -- its boundaries keep being rediscovered the hard way, invariants keep getting violated, or sessions repeatedly ask the same questions about it.
- ▌ MCP Server Builder 2 · yeaight7 bundleDesign 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.
- ▌ Local RAG MCP 2 · yeaight7 bundleUse when querying, ingesting, or maintaining a local RAG MCP corpus for semantic document retrieval with privacy controls.
- ▌ Github CI Failure Triage 2 · yeaight7 bundleUse when a GitHub PR shows failing checks and a clean failure readout is needed before changing any code.
- ▌ AI Regression Testing 2 · yeaight7Use when an agent has modified logic, API routes, or data-transformation code, a bug was just fixed and must not be reintroduced, or behavior must stay identical across execution paths such as sandbox versus production.
- ▌ Receiving Code Review 2 · yeaight7Use when receiving code review feedback, before implementing suggestions — requires technical verification and reasoned pushback, not performative agreement or blind implementation.
- ▌ MCP Risk Review 2 · yeaight7Use when an MCP server is about to be enabled, added to agent config, or upgraded -- a staged server config is a candidate for activation, a third-party server is proposed from a registry, or an existing entry changes transport, credentials, or tool surface.
- ▌ Agent Harness Design 3 · yeaight7Use when designing tool definitions for a new agent or subagent, an agent shows high retry rates, ambiguous tool invocations, or silent failures, or an existing agent harness needs a quality review.
- ▌ AI Slop Cleaner 2 · yeaight7Use when a working code path feels bloated, noisy, or over-abstracted, when asked to clean up or deslop AI-generated code, or when a reviewer-only anti-slop pass is requested.
- ▌ Bigquery Cost Audit 2 · yeaight7Use when reviewing BigQuery spend, query failure patterns, or scan inefficiencies -- identifying which jobs, users, or projects drive cost, or preparing optimization recommendations for a cost review.
- ▌ Failure Triage 2 · yeaight7Use when confronted with an unknown failure in CI or production, before committing to a deep debugging approach.
- ▌ API Doc Review 2 · yeaight7Use when API documentation may have drifted from the implementation -- endpoints changed without a spec update, integration partners report mismatches, or a PR touches routes, params, or response shapes.
- ▌ Requesting Code Review 2 · yeaight7 bundleUse when completing tasks, implementing major features, or before merging to verify work meets requirements.
- ▌ Ml Leakage Check 2 · yeaight7Use 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.
- ▌ Test Driven Development 2 · yeaight7Use when implementing any feature or bugfix, before writing implementation code
- ▌ Skill Authoring Guide 2 · yeaight7 bundleCreate or refactor high-quality skills with lean frontmatter, progressive disclosure, and optional bundled helpers. Use when authoring reusable agent workflows.
- ▌ Context Retrieval Loop 5 · yeaight7Use when starting work in an unfamiliar area of a codebase, spawning a subagent that needs targeted file context, a first search pass missed the relevant file, or the file scope of a task is unclear.
- ▌ Dead Code Removal 2 · yeaight7Use when unused functions, classes, exports, or files need to be identified and safely deleted.
- ▌ Deploy Pipeline Runbook 2 · yeaight7Use 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.
- ▌ Incident Readout 2 · yeaight7Use when a bug fix or complex debugging session concludes and a blameless post-mortem summary is needed for human review.
- ▌ Dispatching Parallel Agents 2 · yeaight7Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
- ▌ Readme Hardening 2 · yeaight7Use 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.
- ▌ Pre Release Verification 2 · yeaight7Use when a release candidate needs final checks before tagging, publishing, or production deployment.
- ▌ Hook Safety Review 2 · yeaight7Use when a hook is about to be enabled or modified -- a hook recipe proposed for activation, a pre/post-tool or lifecycle hook added to agent settings, a git pre-commit hook added to a repo, or a third-party hook snippet pasted in from outside.
- ▌ Dependency Cleanup 2 · yeaight7Use when package manifests carry unused or redundant third-party dependencies that slow builds, widen the security surface, or complicate updates.
- ▌ Metric Impact Analyzer 2 · yeaight7Use 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.
- ▌ Strategic Context Compaction 2 · yeaight7Use 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.
- ▌ Hard Won Skill Extractor 2 · yeaight7Use 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.
- ▌ Canonical Advisor Routing 2 · yeaight7Use when routing a prompt to a local provider CLI for a second opinion, review, or plan -- you are about to call a provider directly, need the response saved for later, or want a single consistent way to invoke codex/gemini/claude.
- ▌ Verification Before Completion 2 · yeaight7Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
- ▌ Agent Readable Docs 2 · yeaight7Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.
- ▌ Dataset Split Review 2 · yeaight7Use when reviewing how data is split into train/validation/test sets -- especially with time-series data, repeated entities (users, patients, sessions), or imbalanced targets.
- ▌ Memory Build Workflow 2 · yeaight7Use 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.
- ▌ Memory Query Workflow 2 · yeaight7Use when a graph already exists and the user needs retrieval, tracing, explanation, or gap detection from graph memory before reopening the full corpus.
- ▌ Secret Leak Preflight 2 · yeaight7Use when about to commit, push, or publish -- staged changes touch config or environment files, generated artifacts (relay sessions, logs, build output) are being added, or the session handled credentials even indirectly.
- ▌ Incremental Migration 2 · yeaight7Use when migrating APIs, libraries, or patterns across a large codebase and a single mega-commit would be too risky to review or merge.
- ▌ SQL Business Logic Review 2 · yeaight7Use 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.
- ▌ Log Driven Diagnosis 2 · yeaight7Use when debugging complex runtime failures, distributed systems, or issues where a local debugger cannot be attached.
- ▌ Minimal Reproduction 2 · yeaight7Use when a bug must be isolated from a large application into a standalone, runnable script or single test case.
- ▌ Regression Bisecting 2 · yeaight7Use when a bug was recently introduced but you don't know which commit caused it.
- ▌ Systematic Debugging 2 · yeaight7 bundleUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
- ▌ Markitdown File Intake 2 · yeaight7 bundleUse when the user provides a MarkItDown-supported file or URL and converting it to Markdown first will make inspection easier, cheaper, or more reliable.
- ▌ Doc Consistency Check 2 · yeaight7Use 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.
- ▌ Browser Automation Safety 2 · yeaight7 bundleUse when validating rendered web pages, local dev servers, browser automation, screenshots, forms, auth sessions, or UI evidence with strict browser safety boundaries.
- ▌ Red Team Eval Authoring 2 · yeaight7 bundleUse when creating or reviewing red-team eval plugins, attack templates, grader rubrics, safety fixtures, or model-risk test metadata.
- ▌ Search Before Building 2 · yeaight7Use when about to add a new helper, utility, or abstraction, a task sounds like a solved problem, a new external dependency is being considered, or custom code is proposed without checking what already exists.
- ▌ Prompt Evaluation Runner 2 · yeaight7 bundleUse when evaluating prompts, LLM outputs, red-team suites, or model behavior with local eval configs and safe provider/cost controls.
- ▌ Test Preserving Refactor 2 · yeaight7Use when code needs restructuring and observable behavior must stay unchanged, with existing tests kept green at every step.
- ▌ Semantic Layer Change Review 2 · yeaight7Use 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.
- ▌ Filesystem MCP Guardrails 2 · yeaight7 bundleUse when designing or reviewing filesystem MCP access, path boundaries, allowed roots, method allowlists, and safe local file operations.
- ▌ Managed Codebase Context 2 · yeaight7 bundleUse when connecting to a managed codebase-context MCP/session service, checking stale maps, or safely using MCP-provided repository context.
- ▌ Flaky Test Investigation 2 · yeaight7Use when tests pass and fail intermittently without code changes, or a test passes alone but fails in the full suite.
- ▌ Parallel Execution Engine 2 · yeaight7Use 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.
- ▌ Requirements Clarifier 2 · yeaight7Use 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.
- ▌ Skill Evaluation Workbench 2 · yeaight7 bundleUse when designing, running, debugging, or hardening deterministic eval suites for agent skills, prompts, tool workflows, or MCP-backed cases.
- ▌ Dbt Incremental Strategy Audit 2 · yeaight7Use when reviewing a new or changed dbt incremental model -- the strategy looks over-engineered, rebuild or delete behavior is unclear, or the model deviates from how the rest of the repo handles incrementals.
- ▌ Baseline Comparison Review 2 · yeaight7Use when a new or more complex ML model is proposed and its value over simple baselines is not yet demonstrated -- before approving a new architecture or replacing an existing heuristic.
- ▌ Experiment Tracking Review 2 · yeaight7Use 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.
- ▌ Model Evaluation Reporting 2 · yeaight7Use 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.
- ▌ Reproducible Training Runs 2 · yeaight7Use 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.
- ▌ Agent Config Security Audit 2 · yeaight7Use when modifying agent config files, committing configuration changes, onboarding a repository with existing agent configs, or running a periodic config hygiene check.
- ▌ Codebase Migration Batches 2 · yeaight7Use when a wide refactor or migration is too large to ship as one change — API renames across many files, framework or config migrations, or mechanical codemod-backed refactors that need reviewable batches.
- ▌ Persistent Completion Loop 2 · yeaight7Use 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.
- ▌ Structured Code Search MCP 2 · yeaight7 bundleUse when designing or using MCP-backed structured code search with search, AST query, symbol inventory, and bounded extraction workflows.
- ▌ Architecture Simplification 2 · yeaight7Use when a codebase carries over-engineered abstractions, unnecessary layers, or redundant logic that should be collapsed without changing behavior.
- ▌ Agent Harness Design 2 · yeaight7Use when designing tool definitions for a new agent or subagent, an agent shows high retry rates, ambiguous tool invocations, or silent failures, or an existing agent harness needs a quality review.
- ▌ Context Retrieval Loop 2 · yeaight7Use when starting work in an unfamiliar area of a codebase, spawning a subagent that needs targeted file context, a first search pass missed the relevant file, or the file scope of a task is unclear.