Results for “l-eval”

Ark protocol: VTXOs (Virtual Transaction Outputs) batched off-chain with periodic on-chain settlement. ARKADE (Ark Labs) is the first mainnet implementation. ASP (Ark Service Provider) coordinates rounds; users keep unilateral exit. USE WHEN: building Ark integrations, evaluating Ark vs Lightning, designing batched payment flows.

Plan and execute a comprehensive red team engagement covering reconnaissance through post-exploitation using MITRE ATT&CK-aligned TTPs to evaluate an organization's detection and response capabilities.

Guides the agent to research existing tools, libraries, and patterns before writing custom code, using parallel searches across package registries, MCP servers, skills, and GitHub, then evaluating and deciding to adopt, extend, or build.

Compare tradeoffs and recommend architectural patterns — dependency injection, service-oriented architecture, repository, domain events, circuit breaker, and anti-corruption layer. Use when choosing between design patterns, planning microservices boundaries, evaluating system design alternatives, or asking 'which pattern should I use' for a specific coupling or resilience problem.

Expert guidance for Zig, the systems programming language focused on performance, safety, and readability. Helps developers write high-performance code with compile-time evaluation, seamless C interop, no hidden control flow, and no garbage collector. Zig is used for game engines, operating systems, networking, and as a C/C++ replacement.

Advises against testosterone therapy in men with biochemical recurrence after prostate cancer treatment due to very limited data and potential risk of progression. Consider when a patient has a rising PSA after definitive therapy and the clinician evaluates testosterone for hypogonadism, questioning whether TTh is safe in BCR.

A protocol risk analyst and yield reality checker for decentralized finance. Evaluates protocol safety before deposit. Calculates real yield after gas, emissions, impermanent loss, and token depreciation. Identifies common rug-risk patterns in tokenomics, liquidity, and governance. Advisory only—no wallet access, no private key handling, no transaction signing, no on-chain execution.

Evaluates likelihood of primary aldosteronism by measuring plasma aldosterone suppression after oral captopril; normal suppression ≥30% makes PA unlikely, while lack of suppression with persistently suppressed plasma renin activity suggests PA. Use when assessing captopril challenge test (CCT) results for PA diagnosis in patients with positive aldosterone-to-renin ratio.

Recommends measurement of plasma ACTH to establish primary adrenal insufficiency (PAI) diagnosis in patients with confirmed cortisol deficiency; a plasma ACTH concentration ≥2-fold the upper limit of the reference range supports PAI. Use when evaluating plasma ACTH in a patient with low morning cortisol or abnormal corticotropin stimulation test.

Generate 5–10 business idea candidates from a blank page or a founder's domain context — using pain mining, jobs-to-be-done, trend × capability mapping, constraint relaxation, adjacency search, and founder-market-fit prompts. Each candidate is a structured idea card (segment, JTBD, current alternative, why-now, distribution wedge, monetisation, "feels like"). Load when the user asks to generate business ideas, brainstorm startup ideas, find ideas to work on, says "what business should I start", "give me startup ideas", "I don't know what to build", "ideate ventures", "blank-page idea generation", "find me a startup idea", "explore business opportunities". Sub-skill of `venture-exploration`. Hard-bans "Uber for X" / "AI for X" with no specific JTBD, "everyone" segments, and idea cards missing any of the 7 required fields. Does NOT design or evaluate ideas generated — for that use `idea-evaluation`.

Determines whether to perform adrenal venous sampling (AVS) to lateralize aldosterone excess in patients with confirmed primary aldosteronism (PA) who are being evaluated for surgical treatment. Indicated when surgery is feasible and desired by the patient, or when subtype workup is planned for a surgical candidate, especially in those younger than 35 years with spontaneous hypokalemia, marked aldosterone excess, and unilateral adrenal lesions on CT.

Failure diagnosis, DAG mutation, and escalation engine for the WinDAGs meta-DAG. Receives failure information and quality vectors from the Evaluator. Classifies failures on four dimensions. Follows a five-level escalation ladder. Applies seven mutation types with saga compensation. Enforces BC-EXEC-002, BC-EXEC-003, BC-FAIL-002, BC-FAIL-005. Activate when operating as the Mutator role in the meta-DAG, when diagnosing node failures, when restructuring a DAG at runtime, or when deciding escalation level.

Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", "software craftsmanship", "technical debt prevention", "prototype vs tracer bullet", or "code ownership". Also trigger when evaluating build-vs-buy decisions, designing estimation approaches, or choosing between reversible and irreversible architectural decisions. Covers estimation, domain languages, and reversibility. For code-level quality, see clean-code. For refactoring techniques, see refactoring-patterns.

Legal-specific Argument Ranking Engine. Hodnotí právní argumenty 17-sloupcovým scoringem (síla, bezpečnost, dopad, riziko + 10 legal-specific kritérií: Compliance s novelou 2026, Evidence backing, Time-sensitivity, per-document mapping, R-static/R-reversal split, Tom-weight bonus, C-XX/M-XX/N-XX/D-XX integrace). Output: priorizovaný seznam argumentů s kategoriemi CORE/SUPPORT/CONTEXT/EXCLUDED/SUMMARY a per-document bundles (PR/§909/40_06/195). Použití: pre-prioritizace argumentů před F11.x review, Phase 2 Verify input, DÁVKA 3, výživné L04, AT podání. VŽDY použij tento skill, když Tom (nebo legal/strat) zmíní: /lare, lare, argument ranking, ARE matrix, score arguments, prioritize arguments, argument bundle, CORE/SUPPORT/CONTEXT/EXCLUDED, ARE_F11, LARE_F11, legal argument evaluation, argument scoring, compliance scoring, Tom-weight.

Write the context brief a first-time tester gets before testing an app, tool, codebase, or product — it explains WHAT the thing is and why it exists, while deliberately withholding HOW anything works. The companion to the fresh-eyes skill; the brief it produces is the "starting information" handed to a fresh-eyes tester. Use this whenever the user is preparing a fresh-eyes or first-time-user test and needs the setup material, or says things like "describe my app without giving anything away", "write the context card for the tester", "explain what it is but not how to use it", "set up the newcomer test", "what would the tester be told going in?", or wants a spoiler-free description of their product. Also use it when someone asks for the briefing/intro that a new tester, new hire, or evaluator should receive before first contact with the thing being tested.