「espec」の検索結果

Create reproducible, cross-platform development environments with Flox — a declarative environment manager built on Nix. ALWAYS use this skill when the user needs to: set up a project with system-level dependencies (compilers, databases, native libraries like openssl, libvips, BLAS, LAPACK); configure reproducible toolchains for Python, Node.js, Rust, Go, C/C++, Java, Ruby, Elixir, PHP, or any language; manage environments that must work identically across macOS and Linux; pin exact package versions for a team; run local services (PostgreSQL, Redis, Kafka) alongside development tools; onboard new developers with a single command; or solve 'works on my machine' problems. Especially valuable for AI-assisted and vibe coding — Flox lets agents install tools into a project-scoped environment without sudo, system pollution, or sandbox restrictions, and the resulting environment is committed to the repo so anyone can reproduce it instantly. Use this skill even if the user doesn't mention Flox — if they describe needing reproducible, declarative, cross-platform dev environments with system packages, this is the right tool. Also use when the user mentions .flox/, manifest.toml, flox activate, or FloxHub.

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

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

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

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

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

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

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

Use this skill whenever you are working on a project that uses Firebase products or services, especially for mobile or web apps.

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

Score a repository's agentic legibility from repo-visible evidence only. Use when Codex needs to audit how easy a codebase is for coding agents to discover, bootstrap, validate, and navigate, especially for harness-engineering reviews, developer-experience audits, repo cleanup, or before/after comparisons after improving docs, tooling, or architectural constraints.

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

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

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

Internal utility for the skills library itself — opt-in, local-first, privacy-respecting usage telemetry and update checks. Provides version checking, usage logging, and usage reporting for the skills in this repo. Use only when asked to view skill usage stats, configure telemetry opt-in/out, wire a skill to log its own runs, or check for skill updates.

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

Scan projects for credential leaks, secrets in code, insecure patterns, LLM API key exposure, PII leakage to external AI services, and .env/.gitignore misconfigurations. Especially useful for data and API integrations, regardless of implementation language.

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

Deep behavioral security audit for AI agent skills and MCP tools. Performs deterministic static analysis (AST + Semgrep + 15 specialized scanners), cryptographic lockfile generation, and optional LLM-powered intent analysis. Use when installing, reviewing, or approving any skill, tool, plugin, or MCP server — especially before first use. Replaces basic safety summaries with full CWE-mapped, OWASP-tagged, line-referenced security reports.

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

Prompt-injection and data-exfiltration screening for untrusted text. Use before summarizing web/email/social content, before replying, and especially before writing anything to memory. Provides a safe memory append workflow (scan → lint → accept or quarantine).

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

This is the MistEye security gate skill. It is triggered by pre-installation risk checks (including Skill/MCP dependency manifests), pre-access security checks for domains or URLs, IoC malicious detection, and supply-chain risk blocking, especially for common requests such as "take a look at this address/website." It must use `https://app-api.misteye.io/functions/v1/detect`; in dependency and external-link scenarios it has the highest priority. If the API returns `status="malicious"` or any `matches`, the action must be blocked and explicitly reported as "blocked". Only after the first installation is complete should the user be reminded that daily patrols can be enabled with OpenClaw or Hermes (default once per day).

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

Code auditor that grades software projects and the agents/developers who built them. Produces structured JSON + Markdown reports with a standardized rubric. Evaluates architecture, correctness, testing, authorship cohesiveness, ghost code, and more. Optionally ingests tmux session logs for process evidence and interrogates agents about specific problems found. Use when asked to "audit", "grade", "evaluate", "review code quality", "rate this project", "score the agents", or "assess the codebase". Especially useful after Marcus multi-agent experiments to grade agent output and track quality over time.

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

GEODE prompt-writing standards. Use when creating or editing runtime prompts, system prompts, tool/developer instructions, model-facing identity text, prompt templates, or scaffold rules that affect model behavior; especially when avoiding identity assertions such as "You are ...".

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

VitePress documentation workflow for Software Metrics Machine docs under docs/vitepress. Use when creating, updating, reviewing, or restyling SMM documentation pages, especially feature docs that must keep CLI terminal examples and dashboard views/screenshots in sync. Covers Markdown style, VitePress tabs, command examples, dashboard screenshots, sidebar links, and docs validation. USE FOR: docs/vitepress, VitePress docs, documentation style, CLI docs, dashboard docs, screenshots, feature pages. DO NOT USE FOR: application code changes unless needed to verify documented behavior.

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

Safely localize unknown Unity games, especially Japanese-to-Chinese projects. Use to discover Unity version/layout/backend, migrate translations across game versions, extract occurrence-mapped text from serialized assets, embedded CSV, bytecode, UI, Localization StringTables, Utage, or middleware, bridge rows through AiNiee-style translation, validate and transactionally write approved candidates, audit residual and runtime-only text or AutoTranslator diffs, diagnose TMP fonts and Addressables/IL2CPP failures, locate saves, or acceptance-test SHA-verified patches.

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

Up-to-date Zig programming language patterns for version 0.17.0-dev (0.16.0 stable APIs plus the 0.17 deltas). Use when writing, reviewing, or debugging Zig code, working with build.zig and build.zig.zon files, or using comptime metaprogramming. Critical for avoiding outdated patterns from training data - especially std.net→std.Io.net (requires Io instance), std.time timestamps removed (use clock_gettime), std.Thread.Mutex/Condition/sleep removed (use pthreads), std.crypto.random removed, build system APIs (root_module, Compile methods→Module methods), I/O APIs (buffered writer pattern), container initialization (.empty/.init), allocator selection (DebugAllocator), ArrayList now unmanaged by default, @typeInfo lowercase fields (.@"struct" not .Struct), and removed language features (async/await, usingnamespace). Also covers 0.17.0-dev deltas: b.args→run_cmd.addPassthruArgs(), std.gpu→std.spirv, @bitCast logical-bit (endian-agnostic) semantics, build configurer/maker split, and the zig-pkg/ package directory. Also covers quality tooling Zig does not ship: coverage with kcov (and why in-file tests wreck the denominator), detecting unused private functions (neither the compiler nor zlint's unused-decls finds them), duplicate detection with jscpd, zlint (NOT the same-named X.509 linter in Homebrew), and the built-in fuzzer whose testOne now takes *std.testing.Smith rather than []const u8.

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

Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.

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

Design roadside signs and large-format ads for businesses, especially automotive dealers. Use for pylon signs, monument signs, lot banners, highway billboards, digital roadside boards, service-lane signage, used-car event signs, lease or finance campaign concepts, and other driver-at-speed messaging where legibility, offer hierarchy, and dealer ad compliance matter. Activate on "road sign", "billboard", "dealership sign", "car dealer ad", "pylon sign", "monument sign", "service lane signage", "automotive billboard", "roadside ad", "dealer lease offer", or "drive-by signage". NOT for fabrication drawings, permitting or local sign-code review, web or social ad campaigns, or full brand identity systems.

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

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

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

This skill guides evaluation of venous thromboembolism (VTE) risk factors in Cushing's syndrome patients to prevent thrombotic complications. Use when assessing a CS patient for thrombotic risk, especially perioperatively; triggers include preoperative assessment, postoperative period (within 4-6 weeks), or presence of CS with additional risk factors such as prior VTE, immobilization, malignancy, or estrogen use.

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

Guidance for clinicians managing pregnant individuals with preexisting diabetes mellitus (PDM) who are evaluating daily carbohydrate intake; consider a carbohydrate-restricted diet (<175 g/day) or usual diet (>175 g/day) based on patient factors. Trigger when assessing nutrition in pregnancy for PDM, especially when discussing glycemic targets, weight gain, or fetal growth concerns.

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

Recommends mineralocorticoid receptor antagonists for all primary aldosteronism patients to prevent target organ damage, irrespective of blood pressure control or serum potassium levels. Triggered when a clinician encounters a PA patient with well‑controlled BP and normal K and wonders, 'Do I still need to treat with MRA?' or considers stopping therapy.

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

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.

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