Results for “e-e-a-t”

Runs a Tinder-style swipe interview to pull requirements out of someone's head. Claude generates a deep pool of question cards, the user swipes right/left/up/down (yes / no / absolutely / not sure), the deck reshapes itself around every swipe, and it ends in a written brief once a saturation meter fills. Use this whenever a request is vague, broad, or taste-dependent and you would otherwise fire off a list of clarifying questions — kicking off a project, scoping a build, planning a trip or event, choosing a direction, naming something, deciding what to eat, or any "help me figure out what I want". Trigger on "swipe", "swipe deck", "tinder style", "interview me", "ask me questions", "quiz me", "20 questions me", "figure out what I want", "get it out of my head". Also reach for it proactively any time you catch yourself about to ask more than three clarifying questions in a row, or when someone says a batch of questions felt like a chore or a form.

Dense, machine-readable API reference for PyFixest — high-dimensional fixed-effects OLS/WLS/IV and Poisson (feols, fepois, feglm), clustered/robust standard errors, R-style formula syntax, and post-estimation. Use when writing or debugging Python fixed-effects regressions with the pyfixest package.

Use to extract competitor mentions, switching language and feature-gap evidence from support conversations as an input to win/loss and product strategy. Trigger for "what competitors do customers mention", "why do customers switch away", "find feature gaps customers ask about", competitive intelligence from support, or win/loss analysis that only samples deals sales remembers.

Perform authorized penetration testing against AWS, Azure, and GCP cloud environments using cloud-specific tools and methodologies, with findings mapped to the MITRE ATT&CK Cloud matrix.

Reads BA and TechLead artifacts to produce a sprint plan, task breakdown, and story point estimates, creating one tracked todo per sprint task for live pipeline tracking.

Generate, audit, or update GitHub READMEs with project-type-aware structure, voice calibration, and SEO/AEO discoverability guidance. Three modes: generate (new), audit (check existing), update (patch). Detects repo type and adapts sections, tone, and badges accordingly.

Turn a theory-first research idea into a proof-oriented research plan. Use after idea-creator-analysis, or when the user asks for theorem targets, assumptions, proof obligations, impossibility routes, analysis validation, or a non-experimental plan.

Orquestrador do pipeline de evolução do Reversa. Detecta o estágio físico da feature ativa em `_reversa_forward/` e sugere o próximo agente do ciclo forward (requirements, clarify, plan, to-do, audit, quality, coding). Use quando o usuário digitar "/reversa-forward", "reversa-forward", "iniciar evolução", "iniciar pipeline forward" ou pedir para conduzir o ciclo de uma feature do zero ao código. Não escreve artefatos de feature por conta própria, apenas roteia.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Plans features interactively, creates dependency-ordered tasks, and prepares Ralph for autonomous execution.

Coordinate multiple subagents/worktrees for parallel workstreams. Decomposes larger tasks into independent sub-tasks, dispatches each to a dedicated agent.

Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https://llmstxt.org/

Research-before-coding workflow. Search for existing tools, libraries, and patterns before writing custom code. Invokes the researcher agent.

Scan skills to extract cross-cutting principles and distill them into rules — append, revise, or create new rule files

Generate knowledge schemas and ontologies from any input format. Extract semantic structures, relationships, and hierarchies. Output as Obsidian markdown with YAML frontmatter, wikilinks, tags, and mermaid diagrams, or export to semantic formats (JSON-LD, RDF, Neo4j Cypher, GraphQL). Supports fractal mode (strict hierarchical constraints) and free mode (flexible generation). Auto-activates for queries containing "schema", "ontology", "knowledge graph", "extract structure", or "generate outline".

Executes Atomic Red Team tests mapped to MITRE ATT&CK techniques, performs coverage gap analysis, and runs detection validation loops to measure blue team visibility.

Simulator.Company digital-twin & actor-agent specialist — talk to an agent AS an agent and delegate work to it. An agent is ANY actor whose `description` holds an "# Agent" competency profile (what it does, what it knows, whether it fits a task). The common case is a person: every workspace user has a 1:1 twin actor (`systemObjType="user"`) carrying that profile. But any actor can be an agent — a service/bot twin, a team or department, an organization, a process. This skill discovers the agent (`findAgent`), loads its profile (`getAgent`), adopts it as the persona, then either does the task, finds a better-suited agent, or hands the decision to the user (for a person: a task or a p2p message; for a non-person: propose another executor or run/trigger it as an actor). It is the actor-analog of `simulator-skills` (the `Skills`-form registry), but the registry is the workspace's agent actors. Use when the user wants to "delegate", "assign this to <someone/something>", "can <X> do this", "who/what should do this",

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.

Write user-facing copy following Sentry's brand guidelines, covering Plain Speech and Sentry Voice tones for UI text, documentation, and marketing content.

Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

This skill guides perioperative levothyroxine management for adults with preoperative central hypothyroidism undergoing non-emergency surgery. Trigger phrases include "preoperative central hypothyroidism patient requiring non-emergency surgery" and "use when managing preoperative CH patient".

Wilkinson, branchline, ratrace, directional couplers, corporate dividers, Rotman lenses for power splitting and beam-forming. TRIGGER: user asks to design, create, or analyze any coupler, splitter, power divider, combiner, or Rotman lens. Invoke BEFORE writing code — class names and design() availability vary per coupler type. SKIP: EM simulation/S-parameter extraction of an existing component (use matlab-analyze-em), building custom non-catalog geometry (use matlab-assemble-pcb-layout), material/stackup setup only (use matlab-manage-pcb-material), cascading multiple components (use matlab-integrate-pcb-circuit).

Analisa os efeitos da revelia (CPC 344-346) e suas excecoes (345), tanto quando o cliente e o revel quanto quando a parte contraria e revel. Cobre a presuncao de veracidade dos fatos (344), as quatro hipoteses em que ela NAO opera (345 — litisconsorte contestante, direito indisponivel, falta de instrumento que a lei repute indispensavel, fatos inverossimeis/contraditorios com a prova), a fluencia de prazos sem intimacao (346) e a possibilidade de o revel ingressar e produzir prova. Use quando o operador disser revelia, reu revel, parte nao contestou, efeitos da revelia, presuncao de veracidade, ou meu cliente perdeu o prazo de defesa.

Trace every user-facing button/touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any major refactor touching shared state stores.

Write effective unit tests with TUnit, covering standard tests, data-driven tests, and migration from xUnit.

Use when ASTA Powerproject integration, API development, or data synchronization is needed. This agent specializes in ASTA Powerproject connectivity within the IntegrateForge AI ecosystem.

Safety guardrails for autonomous agents. Intercepts destructive actions and vets skills, requires structured approval before irreversible operations, with CLI-backed cryptographic audit trails and policy enforcement.

Building interactive experiences that engage, challenge, and delight playersUse when "game, gamedev, game development, phaser, unity, unreal, godot, gameplay, game loop, sprites, collision, physics, player, level, tilemap, games, gamedev, interactive, gameplay, physics, engines, performance, player-experience" mentioned.

Implements telehealth privacy compliance covering HIPAA requirements for virtual care, state licensing and recording consent laws, platform security with BAA requirements for telehealth vendors, cross-state prescribing rules, and OCR enforcement discretion during public health emergencies. Keywords: telehealth privacy, virtual care, HIPAA, recording consent, platform BAA, cross-state licensing, OCR enforcement.

Researches an open-ended question — options, possible solutions, prior art, trade-offs, or how something works — and produces a durable, evidence-backed, adversarially-validated report that recommends an option without committing the team to any artifact. Use when you want to research approaches, weigh options, survey prior art or the state of the art, or understand how something works before committing to a direction. Does not diagnose a bug, failure, or root cause — use investigate. Does not specify a feature — use plan-a-feature. Does not create or update a coding standard — use coding-standard. Does not compare two concrete artifacts for gaps — use gap-analysis. Does not assess an existing module's architecture — use architectural-analysis. Does not capture feedback on Han's own skills — use han-feedback.

Walks a running app across routes, states, and interactions to find real bugs, then root-causes, fixes, adds regression tests, and verifies each fix before committing.

This skill should be used when the user asks to "/do-agent", asks for "Execute complex tasks using multi-agent architecture with context protection", or needs the workflow previously provided by the /do-agent slash command.

Write effective unit tests with XUnit, covering standard and data-driven testing approaches.

Deliberative consultation with another Claude model via Task tool. Opus consults Sonnet, Sonnet consults Opus. Ask, evaluate, critique, iterate until workable agreement.

Three.js asset loading - GLTF, textures, images, models, async patterns. Use when loading 3D models, textures, HDR environments, or managing loading progress.

Compiled CLI covering all 52 endpoints of the Anytype local API — objects, properties, tags, search, chat, files — one binary, no MCP server needed.