397 件 ・ 関連度順
概要と使いどころ
Evaluate and tier suppliers using a weighted scorecard per SCOR DS Supplier Management practices. Score Quality, Delivery, Cost, Responsiveness, and Sustainability. Classify suppliers as Strategic, Preferred, Approved, or Conditional. Use during vendor reviews or procurement decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Write structured Requests for Proposal (RFP) or Requests for Quotation (RFQ) aligned with ISO 20400 sustainable procurement principles. Cover scope, technical requirements, evaluation methodology, and commercial terms. Use when sourcing vendors, services, or equipment.
日本語の概要は準備中です。原文の説明を表示しています。
Write one-page executive briefs and decision memos that turn messy inputs into a concise recommendation, options, risks, decision ask, and next steps. Use when leaders need a fast read before approving budget, policy, vendor, headcount, or strategy changes. Do not use for long-form reports, slide design, or generic summarization without a decision.
日本語の概要は準備中です。原文の説明を表示しています。
Review commercial contracts, NDAs, MSAs, SOWs, and vendor agreements for obligation clarity, risk allocation, termination, data handling, and negotiation red flags. Use when a user needs a structured contract summary, red flag list, fallback positions, or clause-by-clause review. Do not use as jurisdiction-specific legal advice, litigation strategy, or final legal sign-off.
日本語の概要は準備中です。原文の説明を表示しています。
Draft commercial contracts from scratch by contract type — NDAs, service agreements, vendor contracts, employment agreements, and licensing deals. Follow a clause library approach with risk-balanced terms. Use when creating new contracts. Do not replace legal counsel sign-off on finalized agreements. For reviewing existing contracts, use contract-risk-review instead.
日本語の概要は準備中です。原文の説明を表示しています。
Generates CVE request packages from pentest findings. Reads cve-candidates.json (auto-generated at pentest completion) or findings.json directly, then produces for each qualifying vulnerability: MITRE CVE form data, GitHub Security Advisory draft, full disclosure report, and vendor notification email. Invoke manually after a pentest engagement when you have true-positive findings that warrant CVE IDs.
日本語の概要は準備中です。原文の説明を表示しています。
Vite config, path aliases, vendor chunk splitting, environment-specific builds, Rolldown codeSplitting, Sass modern API, build targets, module preload
日本語の概要は準備中です。原文の説明を表示しています。
Run this skill for Phase 3 of the evidence verification pipeline — the adversarial audit step. Use when you need to check the evidence data lake for bad data before ingestion: dead links, wrong URL formats (tree/ vs blob/), subjective wording ("elite", "high-quality"), stale migration notes, benchmark catalog misuse/vendor-claim leakage, or skills whose star evidence conflicts with classified evidence level. Triggers on phrases like: "audit the data lake", "adversarial check", "ev-adversarial-audit", "check for noise in evidence", "flag bad evidence", "run the audit phase", "quality check the by-type files", or any reference to Phase 3 of the pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Generate and maintain browser demos of Pulp audio plugins (both web ABIs — WAM and WCLAP) from one declarative config, so every demo mounts the SAME shared player and the two ABIs stay in lockstep. Invoke it whenever you publish/update a browser demo of a Pulp plugin, add a plugin to a demo gallery, stand up a new gallery, or touch demo pages/hosting. It runs a deterministic generator (config → stamped WAM+WCLAP site + owned-files manifest) and a blocking validator (config schema, cross-origin-isolation coverage, OG metadata, regeneration ownership). Customization is declarative config in <repo>/.pulp-web-demo/config.json (schema bundled) plus at most two typed module seams; the shared player (pinned @danielraffel/web-player) holds all UX behavior and is never vendored. Works in Claude and Codex.
日本語の概要は準備中です。原文の説明を表示しています。
Add a new benchmark to sgl-eval by vendoring its NeMo-Skills dataset module and registering it in `_TABLE`. Use when the user asks to "add <benchmark>" / "support <benchmark>" / "register <benchmark>" inside the sgl-eval repo.
日本語の概要は準備中です。原文の説明を表示しています。
Threat intelligence fusion skill for collecting, normalizing, deduplicating, enriching, and operationalizing IOCs and TTPs from OTX, MISP, abuse.ch, VirusTotal, Shodan, GreyNoise, Censys, CISA KEV, NVD, vendor blogs, and internal telemetry. Use to build STIX/TAXII feeds, ATT&CK-mapped actor profiles, prioritized blocklists, and detection-ready intel packages.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Door-to-Door Sales Worker — planning a canvassing route or street-vending spot, diagnosing a rep's or vendor's underperformance from doors/contacts/sits/close ratios, navigating solicitation-permit or curfew or cooling-off compliance, structuring a doorstep pitch and objection handling, or reconciling a shift's cash and inventory.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a systems engineer/architect working at the whole-program level — decomposing requirements across hardware/software/network subsystems, writing or reviewing an interface control document (ICD), making a build-vs-buy tradeoff for a subsystem, or tracing a verification failure back through the requirements baseline. Distinct from a software engineer (owns one service's code) or DevOps/SRE (owns operational reliability) — this role owns the technical baseline for a whole system-of-systems and is accountable when subsystems built by different teams or vendors don't fit together.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Computer and Information Systems Manager (IT Manager/Director/CIO-adjacent) — planning IT infrastructure and systems strategy, evaluating a technology vendor or platform decision, allocating an IT budget, or managing IT risk (security, uptime, technical debt) at an organizational level. Broader than the devops-sre or software-engineer roles — this one owns IT as a business function, not a specific engineering discipline.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Concierge — securing a reservation at a fully-booked restaurant or sold-out venue, coordinating a multi-vendor guest request (dinner, transportation, and a gift delivery) inside a tight window, deciding when to pivot from a failed Plan A to a same-caliber Plan B, or navigating a paid-referral relationship without letting the commission distort the recommendation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Chef or Head Cook — costing and re-engineering a menu, diagnosing a food-cost or prime-cost overrun, building a kitchen labor schedule against sales volume, vetting or renegotiating a vendor, or resolving a health-code/HACCP compliance gap.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Administrative Services Manager — evaluating a vendor contract on total cost of ownership rather than price, right-sizing a facilities/admin budget against actual utilization, anticipating where an operational process breaks at the org's next size milestone, or diagnosing why internal operational support is failing a growing organization.
日本語の概要は準備中です。原文の説明を表示しています。
Search DigiKey by keyword or part number, check stock and price breaks, retrieve component specifications, and download or synchronize datasheets for an electronics project. Use when the user explicitly wants DigiKey data, a DigiKey prototype-order comparison, or direct datasheet synchronization. For distributor-neutral sourcing, multi-vendor price comparison, or order-file generation, use the bom skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Reusable deployment templates — one-click deploys, blueprints, and environment-as-code — vendor-neutral patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Scheduled jobs on PaaS and in the cloud — cron syntax, reliability, and observability — vendor-neutral patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Understanding and optimizing cloud/PaaS pricing — cost models, common traps, and FinOps habits — vendor-neutral.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to select the right Salesforce integration pattern — from point-to-point to event-driven to hub-and-spoke — by applying the official Salesforce two-axis decision framework (integration type × timing) to a business integration scenario. Trigger keywords: integration pattern decision, choose integration approach, Salesforce integration architecture, when to use platform events vs API, integration type selection. NOT for implementation of any specific integration pattern (use domain-specific integration skills), MuleSoft architecture (use architect/mulesoft-anypoint-architecture), or middleware vendor selection. More triggers: integration decision record, Bulk API vs REST for a nightly load, external Id upsert, Named Credential vs Remote Site Setting, platform event vs CDC, who calls whom.
日本語の概要は準備中です。原文の説明を表示しています。
Firmware development for the <VENDOR> <BOARD NAME> (<MCU PART NUMBER>) — its <peripheral>, <peripheral>, <peripheral>, and the <SDK/HAL> + <build system> setup around them. Use when working on this board or any <compatible siblings>: project setup, <config file>, clock configuration, pin mapping, peripheral bring-up, <the board's headline concern>, flashing, or debugging why something on the board does not work.
日本語の概要は準備中です。原文の説明を表示しています。
Firmware development for the ProMicro nRF52840 (V1940) — the nice!nano v2 compatible clone also sold as SuperMini nRF52840, nRF52840 Pro Micro or nRFMicro (nRF52840 QIAA, Cortex-M4F @ 64 MHz, 1 MB flash / 256 KB RAM, BLE 5 + 802.15.4, native USB, Adafruit UF2 bootloader with SoftDevice S140). Covers the PlatformIO + Adafruit nRF52 Arduino setup for a board that ships in neither, the vendored board definition and Pro Micro pin map, USB CDC via TinyUSB, Bluefruit BLE, the 32.768 kHz crystal that clones omit, SAADC pins, NFC pins as GPIO, and Zephyr's promicro_nrf52840 board target. Use when working on this board or any nice!nano v2 / ZMK keyboard controller: project setup, platformio.ini, pin mapping, LED not blinking, double-tap RESET and UF2/DFU flashing, SoftDevice version mismatches, a board that enumerates but never runs, or debugging why something on the board does not work.
日本語の概要は準備中です。原文の説明を表示しています。