789 件 ・ 関連度順
概要と使いどころ
Draft, revise, and audit scientific manuscripts or reports with explicit evidence provenance, reporting-guideline coverage, authorship accountability, confidentiality controls, and local consistency checks. Use for manuscript sections, references, declarations, tables, figures, or submission preparation when scientific accuracy and traceability matter.
日本語の概要は準備中です。原文の説明を表示しています。
Provide qualitative-first, evidence-traceable developmental review of scholarly works and audit low-stakes research-assessment rubrics with optional local quality controls. Never use for ranking people or consequential decisions.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end methodology for reproducing AND patching publicly disclosed, already-fixed vulnerabilities: sourcing the advisory and the fix commit, reading the patch diff, rebuilding a pinned offline lab, building a vulnerable-vs-patched contrast harness with proper controls, minimizing the trigger, designing and validating the fix, and writing it up as a blog post or whitepaper. Use this skill whenever the user wants to reproduce, demonstrate, understand, teach, or write about a known vulnerability or security incident: "reproduce this CVE", "build a repro for", "how did EchoLeak / Log4Shell / the postmark-mcp package actually work", "show me how this exploit worked", "write a blog post about this vulnerability", "set up a lab for CVE-XXXX", "pull the NVD/CVE/OSV details", or "make a PoC I can publish". Use it just as eagerly for the patching half: "how should this be fixed", "is this patch correct", "what would have caught this", "review this security fix", "write a regression test for this CVE", "how do I backport this", or "what's the right fix for this bug class" - even when the user never says the word "reproduce". Reach for it on vague asks like "help me understand this security advisory", "I want to write about this incident", or "can we test whether we were vulnerable" when a disclosed vulnerability is in play. This skill only handles ALREADY-PATCHED, publicly disclosed issues and refuses zero-day discovery, live targets, and weaponization.
日本語の概要は準備中です。原文の説明を表示しています。
Identifies what could go wrong in a system before it is built or changed — the assets worth attacking, the entry points, the trust boundaries, and the controls that actually address the realistic threats. Use this when designing a feature or system, when a change touches authentication, data handling, payments, or external input, before a security review, or when deciding which security work is worth doing at all.
日本語の概要は準備中です。原文の説明を表示しています。
Identifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to regulators. Use this to work out what applies to your business, stand up a compliance program, prepare for a regulatory exam or certification, respond to a finding, or assess exposure before entering a new market.
日本語の概要は準備中です。原文の説明を表示しています。
Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process.
日本語の概要は準備中です。原文の説明を表示しています。
Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal hold. Use this to configure a tenant, tighten sharing, investigate a mail delivery or phishing problem, or work out who can see a file and why.
日本語の概要は準備中です。原文の説明を表示しています。
Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Use this to reduce a defect or error rate, design quality controls into a process, run a root cause analysis, respond to a customer quality complaint, or set up quality metrics that drive behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls, or when a plan's numbers do not reconcile. Also use to decide whether the business can afford something.
日本語の概要は準備中です。原文の説明を表示しています。
Designs cell-based and animal-based validation plans that translate computational, omics, biomarker, genetic, or clinical findings into experimentally testable validation routes. Always use this skill whenever a user wants to move from an in silico, statistical, or clinical association finding toward wet-lab validation using cell systems, organoid-like systems, xenograft or genetically relevant animal models. It should define the exact claim to test, separate mechanism-testing from association-support and translational-support goals, choose the best-fit model family, specify perturbation strategy, readouts, controls, sequencing of experiments, and four workload configurations (Lite / Standard / Advanced / Publication+) with one recommended primary plan. Never fabricate model availability, reagent availability, species relevance, assay feasibility, phenotype penetrance, expected effect sizes, validation success, or literature references.
日本語の概要は準備中です。原文の説明を表示しています。
Session-scoped hook lifecycle management with enable/disable/status controls, execution profiling, and color-coded performance alerts.
日本語の概要は準備中です。原文の説明を表示しています。
Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate multi-layer security scanning and hardening across application, infrastructure, and compliance controls.
日本語の概要は準備中です。原文の説明を表示しています。
Implement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, or conducting GDPR compliance reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Select QA-approved canonical intent cells into a versioned AI-visibility tracking panel with partitions, variants, lanes, surfaces, locales, repetitions, separate exposure and priority weights, randomization, uncertainty, refresh rules, and campaign controls. Use after prompt QA or when revising an existing panel.
日本語の概要は準備中です。原文の説明を表示しています。
Microsoft Cloud Security Benchmark (MCSB v2) control-domain taxonomy and NIST 800-53 / CIS Controls crosswalk for planning and reviewing Azure cloud resources.
日本語の概要は準備中です。原文の説明を表示しています。
Security planning and plan-drift analysis for STRIDE, standards, controls, backlog handoff, current findings, and TM7 generation.
日本語の概要は準備中です。原文の説明を表示しています。
Create, update or review presentation-first HTML slide decks about HVE Core under slides/. Use for slide content research, deck styling, VS Code-style walkthroughs, presenter controls, or single-file HTML sharing in this repository.
日本語の概要は準備中です。原文の説明を表示しています。
Infrastructure-as-code specialist for multi-cloud provisioning using Terraform across any provider (AWS, GCP, Azure, Oracle Cloud). Use for terraform plan/apply, state management, compute, databases, storage, networking, IAM, OIDC, cost optimization, policy-as-code, ISO/IEC 42001 AI controls, ISO 22301 continuity, and ISO/IEC/IEEE 42010 architecture documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Create and edit React Native Storybook stories using Component Story Format (CSF). Use when writing .stories.tsx files, adding stories to React Native components, configuring Storybook addons (controls, actions, backgrounds, notes), setting up argTypes, decorators, parameters, or working with portable stories for testing. Applies to any task involving @storybook/react-native story authoring.
日本語の概要は準備中です。原文の説明を表示しています。
Patterns for continuous autonomous agent loops with quality gates, evals, and recovery controls.
日本語の概要は準備中です。原文の説明を表示しています。
Use when targeting Environmental Pollution or deciding whether a contamination/pollutant-impact manuscript fits this venue. Encodes the journal's fit, the source-fate-impact evidence bar, measurement-and-controls expectations, house style, official-submission re-check, and desk-reject heuristics.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building the robustness section for a 《会计研究》 (Accounting Research) manuscript — replacing accounting measures with alternatives, adding governance / institutional controls, placebo tests, and endogeneity follow-ups — so the main result survives an accounting referee's scrutiny. Use after mechanism is settled.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or auditing experiments for an ACL paper, covering tuned LLM baselines, multi-dataset and multilingual evaluation, statistical significance and variance, human evaluation with agreement reporting, contamination and prompt-sensitivity controls, ablations, and error-analysis expectations in NLP reviewing.
日本語の概要は準備中です。原文の説明を表示しています。