「unit」の検索結果

Calibrate an LLM judge against human labels using data splits, TPR/TNR, and bias correction. Use after writing a judge prompt (write-judge-prompt) when you need to verify alignment before trusting its outputs. Do NOT use for code-based evaluators (those are deterministic; test with unit tests per `write-code-eval`).

日本語の概要は準備中です。原文の説明を表示しています。

Pulls Bigdata.com (RavenPack) financial and news data via the official bigdata-client SDK and /v1/* REST endpoints — structured financials, prices, analyst estimates, entity-sentiment series, annotated chunk search, screener. Use when the Bigdata MCP's tearsheets/search feel thin and you need the machine-readable substrate: mentions of Bigdata.com, RavenPack, a bd_v2_ key, rp_entity_id, or chunk/query_unit cost.

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked 质量追溯体系怎么建, 产品追溯方案, 批次追溯, 一物一码, 客户要求可追溯性, 召回演练, 正向追溯和反向追溯, or plan product and batch traceability in a Chinese factory. Produces a traceability plan in Chinese: the trace unit and coding rule, the data to capture at each process step (material lots, work orders, equipment, people, inspection results), forward and backward trace paths, record retention, a mock recall drill with a target time, gaps against the current system, and a phased rollout, with industry rules (food, medical devices, automotive) marked to confirm.

日本語の概要は準備中です。原文の説明を表示しています。

Review a bill of materials for cost, risk, and supply exposure — cost rollup, top-10 cost drivers, single-source and EOL risk, MOQ vs forecast mismatch, cost-down candidates, and tariff/logistics sensitivity. Use when asked to review a BOM, find cost-down opportunities, check component sourcing risk, or sanity-check BOM cost against target. Produces a structured BOM review with a cost driver Pareto, risk flags per line, and a prioritised cost-down list.

日本語の概要は準備中です。原文の説明を表示しています。

Write a fundraising case for support that makes donors want to give. Use when asked to write a case for support, a fundraising case statement, a major-gift or campaign case, or the core argument for a donation appeal. Produces a persuasive case — the need, your solution and why you, the impact a gift makes, specific funding opportunities with amounts, and a clear ask — donor-centred, not org-centred.

日本語の概要は準備中です。原文の説明を表示しています。

Build a realistic recovery plan for burnout — address the causes, not just the symptoms — with changes you can actually make at work and outside it. Use when asked to help with burnout, I'm burnt out, how to recover from burnout, or I'm exhausted and dread work. Produces a read on what's driving the burnout (load, control, reward, fairness, values, community), immediate relief steps, the boundary and workload changes that address the root, a recovery timeline with realistic expectations, and a flag that severe or persistent burnout/depression warrants a professional. Not medical advice.

日本語の概要は準備中です。原文の説明を表示しています。

Write a sincere, effective apology to a customer, group, or the public. Use when asked to write an apology, say sorry to a customer or community, make amends after a mistake, or respond to a complaint with an apology. Produces a genuine apology — acknowledgement, taking responsibility, empathy for the impact, the concrete fix and prevention, and an offer to make it right — in the right tone, without excuses or non-apologies.

日本語の概要は準備中です。原文の説明を表示しています。

Analyse a construction bid or tender package for scope gaps, risk-shifting exclusions, unit-rate red flags, and front-loading in the schedule of values. Use when asked to review a bid, level bids, check a tender for gaps, compare sub quotes, or vet a schedule of values before award. Produces a structured bid review with a gap register, exclusion risk table, pricing red flags, and an award recommendation with pre-award clarifications.

日本語の概要は準備中です。原文の説明を表示しています。

Build a tiered classroom behavior intervention plan (BIP) for a K-12 student, grounded in the function of the behavior. Use when asked to plan a behavior intervention, address a disruptive or off-task pattern, write a BIP, or set up positive behavior supports. Produces a function hypothesis, prevention/antecedent strategies, teaching of a replacement behavior, a response plan for when it happens, and a simple data-tracking method — positive and skill-building, not punitive.

日本語の概要は準備中です。原文の説明を表示しています。

Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.

日本語の概要は準備中です。原文の説明を表示しています。

Search LCSC Electronics for electronic components — find parts by LCSC number (Cxxxxx) or MPN, check stock/pricing, download datasheets, analyze specifications. Sister company to JLCPCB, same parts library. Sync and maintain a local datasheets directory for a KiCad project, or use batch MPN-list seeding (`--mpn-list`) for bulk workflows without a project. No API key needed — uses the free jlcsearch community API. Use this skill when the user mentions LCSC, JLCPCB parts library, JLCPCB assembly parts, production sourcing, Cxxxxx part numbers, needs to find LCSC equivalents for parts, is preparing a BOM for JLCPCB assembly, or wants to download datasheets and LCSC is available. For package cross-reference tables and BOM workflow, see the `bom` skill.

日本語の概要は準備中です。原文の説明を表示しています。

Help users evaluate new opportunities, manage professional identity shifts, and transition into roles that maximize both impact and personal fulfillment.

日本語の概要は準備中です。原文の説明を表示しています。

Help users plan, coordinate, and execute product launches that cut through market noise. This guide covers everything from internal alignment and GACCS briefs to community engagement and viral mechanics.

日本語の概要は準備中です。原文の説明を表示しています。

Help users navigate complex transitions, from scaling new business units to managing crises and driving AI adoption across large organizations.

日本語の概要は準備中です。原文の説明を表示しています。

Help users distinguish between deceptive tarpit ideas and high-potential opportunities by applying rigorous frameworks for market timing, business math, and user demand.

日本語の概要は準備中です。原文の説明を表示しています。

Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.

日本語の概要は準備中です。原文の説明を表示しています。

Use when touching retiring old logic, collapsing duplicate owners, removing fallbacks, or schema/persistence/source-of-truth boundaries; identify opportunities automatically; destructive execution requires explicit confirmation.

日本語の概要は準備中です。原文の説明を表示しています。

Use AtomLane to compile and execute safe atomic parallel plans on macOS and native Windows Preview for worthwhile independent argv tasks, dependency DAGs, supported platform entrypoints, or Apple-silicon operators. Use at task start or an execution boundary when structured local work may contain two or more worthwhile units; skip plain answers, one quick command, and work whose effects cannot be safely bounded.

日本語の概要は準備中です。原文の説明を表示しています。

Codex-native multi-keyword Amazon opportunity scan using LaunchFast MCP. Use when the user wants to research 1-10 keywords, compare niches, or decide whether a product idea is a GO, INVESTIGATE, or PASS. Requires the LaunchFast MCP tool `research_products`.

日本語の概要は準備中です。原文の説明を表示しています。

Search LCSC Electronics for electronic components — find parts by LCSC number (Cxxxxx) or MPN, check stock/pricing, download datasheets, analyze specifications. Sister company to JLCPCB, same parts library. Sync and maintain a local datasheets directory for a KiCad project, or use batch MPN-list seeding (`--mpn-list`) for bulk workflows without a project. No API key needed — uses the free jlcsearch community API. Use this skill when the user mentions LCSC, JLCPCB parts library, JLCPCB assembly parts, production sourcing, Cxxxxx part numbers, needs to find LCSC equivalents for parts, is preparing a BOM for JLCPCB assembly, or wants to download datasheets and LCSC is available. For package cross-reference tables and BOM workflow, see the `bom` skill.

日本語の概要は準備中です。原文の説明を表示しています。

Discovers and installs community skills from the public registry. Use when the user mentions a technology, framework, or task that could benefit from specialized skills not yet installed, asks 'how do I do X', 'find a skill for X', or starts work in a new technology area. Proactively suggest when the user's task involves tools or frameworks without existing skills.

日本語の概要は準備中です。原文の説明を表示しています。

Dispatches many independent items in parallel: create a table, fan out to subagents, aggregate results. One row = one unit of work.

日本語の概要は準備中です。原文の説明を表示しています。

INVOKE THIS SKILL when setting up a new project or when asked about package versions, installation, or dependency management for LangChain, LangGraph, LangSmith, or Deep Agents. Covers required packages, minimum versions, environment requirements, versioning best practices, and common community tool packages for both Python and TypeScript.

日本語の概要は準備中です。原文の説明を表示しています。

Review generated or changed test code against universal testing rules before it ships. Best used reactively after an agent writes, edits, generates, or refactors tests, before presenting, committing, or merging them. Use for pytest (test_*.py, *_test.py), PHPUnit/Pest (*Test.php), Jest/Vitest (*.test.ts, *.spec.js), Go (*_test.go), files under tests/, __tests__/, or spec/, and review requests like 'write tests for X', 'add tests', 'test this', 'review these tests', or PR diffs containing tests. Can also guide test writing when explicitly invoked before the work. This skill is the quality gate that prevents AI-generated test bloat. DO NOT USE for production or implementation code review (use clean-code-guard), CI or test-runner configuration, running or debugging tests, or general architecture discussion.

日本語の概要は準備中です。原文の説明を表示しています。