2,394 件 ・ 関連度順
概要と使いどころ
Compare scoped quantity snapshots and explain matches, missing rows and conflicts. Use to reconcile drawing, report or schedule counts; not to extract source documents or update adopted records.
日本語の概要は準備中です。原文の説明を表示しています。
Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Explain US architecture professional-practice terms, phases, deliverables, roles, delivery methods, AIA contract families, CSI documentation systems, or NCS at a high level. Use for questions such as “what is a CD set?” or “what does 50% CDs mean?”; do not use for code/jurisdiction, outline-spec, agreement-scope, or work-plan work.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain sourced agreement context and scope in PROJECT.md, cite registered contracts/proposals, and record amendments without imposing a commercial workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Draft, diagnose, and improve IEEE rebuttals, revision plans, cover letters, response letters, and point-by-point replies using routed reviewer-comment handling. Use when responding to IEEE reviewer or editor comments about novelty, scope, method, experiments, baselines, figures, tables, citations, writing, LaTeX formatting, limitations, compliance, technical correctness, or reviewer comments that appear generic, contradictory, unsupported, careless, or possibly AI-generated.
日本語の概要は準備中です。原文の説明を表示しています。
Review IEEE conference, journal, Transactions, Letters, or magazine manuscripts from a technical reviewer perspective using routed IEEE review gates. Use when evaluating scope fit, novelty, validity, data, clarity, compliance, advancement, engineering significance, method soundness, experiment sufficiency, baseline fairness, figure/table quality, formatting risks, rejection risk, major revision strategy, pre-submission readiness, or the quality and specificity of reviewer comments that may be generic, careless, contradictory, or possibly AI-generated.
日本語の概要は準備中です。原文の説明を表示しています。
Background legal and regulatory context for the shinkoku tax filing plugin. Contains the standard disclaimer about the scope of tax information provided, the relationship to the Tax Accountant Act (税理士法), and tool limitations. This skill is not user-invocable — Claude loads it automatically when generating tax-related responses that require a disclaimer.
日本語の概要は準備中です。原文の説明を表示しています。
Remove the discourse-level (structural) signs of AI writing that survive surface editing: stated lessons and moral-of-the-story closers, tidy single-track arcs, embodied-emotion performance ("chest tightened"), vague allusions instead of named references, unbroken linear structure, and shape convergence across pieces. Grounded in the StoryScope study (Russell et al. 2026): narrative structure alone detects AI text at 93.2% F1, and professional stylistic rewriting moved detection only 1.6 points. Use as the SECOND pass after the humanizer skill (which handles words and phrasing) whenever writing or revising LinkedIn posts, course lessons, blog posts, essays, newsletters, or emails that must read as human. Triggers: "humanize", "de-slop", "AI tells", "make this sound human", "structural pass", "deep humanize".
日本語の概要は準備中です。原文の説明を表示しています。
Compare and analyze contractor bids. Score proposals, identify scope gaps, and recommend selections.
日本語の概要は準備中です。原文の説明を表示しています。
Builds estimates, quotes, and bids for trades and field-service businesses (HVAC, plumbing, electrical, roofing, landscaping, painting, cleaning, remodeling, general contracting, IT/AV installs). Turns a scope into line items with waste factors, burdened labor, materials, equipment, subs, permits, mobilization, contingency, overhead, profit, and tax, then writes a client-ready xlsx (live formulas) and PDF plus an internal cost sheet, with good/better/best options, add-ons, a payment schedule, exclusions, and assumptions. Use whenever someone asks for a quote, estimate, bid, proposal price, or job price, asks "how much should I charge for this job", wants to check a price or margin on a job, or is confused about markup vs margin. Computes deterministically with a script instead of mental math, because models routinely treat a 30% markup as a 30% margin and drop labor burden, waste, and mobilization.
日本語の概要は準備中です。原文の説明を表示しています。
Generates professional Statements of Work from a project brief. Use when a user needs to create an SOW, scope a project, define deliverables and milestones, or produce a consulting engagement document.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an AI coding agent is writing or refactoring production code and its known failure modes need to be held in check — over-engineering, silent scope creep, invented APIs, claiming work is done without checking, deleting tests to make them pass. Trigger when the user asks for careful, production-grade, or reviewed code, or when a previous agent run produced confident output that turned out wrong.
日本語の概要は準備中です。原文の説明を表示しています。
Generates full consulting proposals from a brief. Input client name, problem description, and rough scope. Outputs proposal.md with executive summary, problem statement, proposed approach, timeline, team, pricing tiers, and terms. Researches client company for personalization. Multiple pricing models. Professional formatting matching consulting standards.
日本語の概要は準備中です。原文の説明を表示しています。
Use before starting a product, feature, MVP, agent, automation, or integration build to identify the main pre-build risk and choose the smallest validation step. Trigger when the user asks whether to build, scope, validate, prioritize, or sanity-check an idea before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Builds session-scoped temporary memory palaces for extended conversations. Use when tracking state across interruptions in a multi-step project.
日本語の概要は準備中です。原文の説明を表示しています。
Ramps implementation ambition a notch only after the prior increment is understood. Use when building a feature you must understand, not just ship.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing a literature review article (narrative, scoping PRISMA-ScR or systematic). Scaffolds a 7-part skeleton with a scope and non-overlap statement, summary-table stubs and reporting-guideline wiring, without inventing citations. Original research is /write-paper.
日本語の概要は準備中です。原文の説明を表示しています。
Use when choosing where to submit a manuscript. Matches the abstract against curated journal profiles and returns ranked picks with scope fit, AI-disclosure policy, an acceptance-readiness pre-flight and a reject-fallback cascade. Impact and APC figures may be stale.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.
日本語の概要は準備中です。原文の説明を表示しています。
External recon and OSINT pipeline - subdomain enum, live host discovery, URL crawl, JS analysis, nuclei scan. Outputs to Attack-surface.md and scope/. Queries wiki before each phase. Use when starting recon on any target.
日本語の概要は準備中です。原文の説明を表示しています。
Cloud attack hunting for AWS / Azure / GCP - credential discovery, metadata SSRF, IAM privesc, service enumeration, persistence. Scope + billing aware. Wiki-first, FIND schema output.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous bug-bounty campaign driver. Runs a full programme end to end with no operator approvals - the deterministic driver (scripts/campaign.py) owns pass state, generates the killchain board from recon, and prints the exact next action (including which Skill and tool to run) every turn. Use when starting or resuming a bug-bounty engagement, "run the bb workflow", "hunt this program", "9-pass campaign", or when handed a *.scope wildcard to test for TIER1 findings. Single agent, refuter-verified, wiki-first, tool-first.
日本語の概要は準備中です。原文の説明を表示しています。
Show per-asset vuln-class coverage gaps for the active engagement so nothing in scope is skipped. Use when asked "coverage", "what haven't we tested", "test gaps", "are we thorough", or before calling an engagement done.
日本語の概要は準備中です。原文の説明を表示しています。
Manage OpenViking collections (OV libraries) from the command line with `ov-cp` — list / create / get / update / usage / get the data-plane API key / delete, plus managing the users and account data spaces of an enterprise-tier library (list / create / register / update / delete), account-scoped users / API keys / usage, and configuring how a library is billed (AgentPlan AFP deduction vs Volcano pay-as-you-go, `--pay-type` / `--seat-id`). Use when the user wants to provision or inspect an OpenViking library, fetch a library's data-plane API key, do the create→get-key cold-start, manage a library's users or accounts / 数据空间, set or switch a library's billing, or otherwise drive the OpenViking control plane (topapi). Authenticates with an Ark AgentPlan ApiKey.
日本語の概要は準備中です。原文の説明を表示しています。