Results for “doe”

Replace with a specific description of what this skill does and when to use it. Include keywords that help agents identify relevant tasks.

Enumerating failure modes via pre-mortem analysis. Systematically identifies failure scenarios for plans, designs, and features, scoring them with RPN/AP. Does not write code.

Audits fuzzy goals into checkable deliverables using Wittgenstein's philosophy of language, ensuring every word does work.

Brief description of what this skill does and when to trigger it. TRIGGERS - Use this skill when: - Trigger condition 1 - Trigger condition 2 - Trigger condition 3

Brief description of what this skill does and when to trigger it. TRIGGERS - Use this skill when: - Trigger condition 1 - Trigger condition 2 - Trigger condition 3

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"

Use this skill when selecting an MRO for drug testing program oversight. Covers MRO qualifications under Part 40, what the MRO does, and how to evaluate MRO services.

Produce a plain-language manual test plan from the context supplied to it — an executive summary, a high-level list of named tests, and a detail section per test with the steps a person follows by hand and the outcomes they should expect. Use when you want to create, draft, generate, or outline a manual test plan, manual QA steps, hands-on verification steps, or an acceptance walkthrough for a feature, change, branch, plan, or PR. When the plan holds more than five tests and at least two natural categories emerge, both the test list and the detail sections are organized under plain-language categories. When nothing in the supplied context can be manually tested, it says so and asks for more context instead of producing a document. Does not analyze code for automated test coverage gaps — use automated-test-planning. Does not write test code — use tdd. Does not review code quality — use code-review. Does not stress-test an existing plan — use iterative-plan-review.

A complete tour of the intelli-verse-x 5-layer stack — Leantime/GitHub at the top, Beads/Bernstein/Claude-Squad in the middle, Gas Town as the multi-project fabric, and LiteLLM/Infisical/Langfuse/n8n/GH-Actions underneath. Use whenever the user asks "what does X service do", "where does Y data live", "how do I get to Z", or you need to understand which tool to reach for. This is the architecture map.

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"

Alpaca broker limitations: crypto shorts blocked (broker doesn't support), stock shorts allowed. Trigger when: (1) shorting gate blocks wrong assets, (2) SELL signals blocked, (3) order type confusion.

Diagnoses why someone knows what to do but doesn't do it, using Adlerian psychology to identify root causes like procrastination, perfectionism, or avoidance.

Design experiments and studies before data collection — choosing a design, randomizing, blocking, and laying out treatment combinations so results are interpretable.

Guardian of V.A.I.R.E. quality standards (Value/Agency/Identity/Resilience/Echo). Handles pre-release evaluation, scorecard assessment, and pass/fail determination. Use when UX quality gates are needed. Does not write code.

Schema validation for notes. Checks against domain-specific templates. Validates required fields, enum values, description quality, and link health. Non-blocking — warns but doesn't prevent capture. Triggers on "/validate", "/validate [note]", "check schema", "validate note", "validate all".

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

Autonomous design space exploration loop for computer architecture and EDA. Runs a program, analyzes results, tunes parameters, and iterates until objective is met or timeout. Use when user says "DSE", "design space exploration", "sweep parameters", "optimize", "find best config", or wants iterative parameter tuning.

DALL-E: Zero-Shot Text-to-Image Generation

Econometrics skill for Difference-in-Differences (DID) analysis. Activates when the user asks about: "difference in differences", "DID", "DiD", "diff-in-diff", "parallel trends", "treatment group", "control group", "pre-treatment", "post-treatment", "policy evaluation", "natural experiment", "staggered DID", "event study regression", "two-way fixed effects DID", "callaway santanna", "sun and abraham", "双重差分", "倍差法", "平行趋势", "处理组", "对照组", "政策评估", "事件研究", "交错DID", "渐进处理"

将实证研究设计转成 Stata 执行计划或 do 文件骨架，包含数据合并、变量构造、描述统计、回归和稳健性

Rewrites AEM Edge Delivery Services page content for AI search discoverability (Generative Engine Optimization) by analyzing structure, clarity, and factual density.

Provides Playwright patterns for building stable E2E test suites, including Page Object Model, configuration, flaky test strategies, artifact management, and CI/CD integration.

Systematic debugging — reproduce, read the error, isolate, hypothesize, fix, verify, document. Use when tracking down a bug, unexpected behavior, or test failure — including phrases like "this doesn't work", "why is this failing", or "help me debug".

Detect and exploit XML External Entity (XXE) injection vulnerabilities in XML parsers, including file disclosure, SSRF, and blind out-of-band exfiltration.

Donate to charities onchain via Endaoment. Use when the user wants to donate crypto to charity, make a charitable contribution, give to nonprofits, support a cause, or donate to a 501(c)(3). Supports Base, Ethereum, and Optimism. Handles USDC donations directly or swaps ETH/tokens to USDC automatically.

Provides Playwright E2E testing patterns including Page Object Model, configuration, CI/CD integration, artifact management, and strategies for handling flaky tests.

Donate crypto to 501(c)(3) charities onchain via Endaoment smart contracts, supporting USDC on Base with automatic ETH/token swaps.

Read, propose, and vote in the Starchild DAO — a hold-to-govern commons for the $STARCHILD token on Base, with gasless EIP-712 signatures.

Provides Playwright patterns for building stable, fast, and maintainable E2E test suites, including Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.