2,377 件 ・ 関連度順
概要と使いどころ
AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Data Scientist role within the AID methodology. Activate when working on: EDA, feasibility assessment, experiment planning, ML architecture, model development & validation, or production deployment & monitoring. Stack-agnostic — ask the user for their stack at the start of any new project.
日本語の概要は準備中です。原文の説明を表示しています。
Review an author's manuscript, its argument and paragraph structure, analyze reviewer comments, draft rebuttals, and verify revisions. Use for self-review, structural edit plans, simulated reviewer objections, author responses, revision closure, and submission-readiness assessment. Formal assigned peer review is outside this skill; manuscript edits and final figures/tables use their owning skills.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve, validate, and audit manuscript integrity and applicable requirements for academic manuscripts and paper artifacts. Use when Codex needs to determine active paper rules from manuscript state, paper type, venue, submission stage, or workflow mode; lint a LaTeX paper project; assess submission readiness; create or update a paper policy profile; explain why a rule is active; or validate the paper-policy registries. Do not use as the primary skill for prose drafting, peer review, rebuttal writing, citation discovery, or figure/table creation.
日本語の概要は準備中です。原文の説明を表示しています。
Build an evidence-backed working model of an existing codebase. Use when you must orient in a large or unfamiliar repository; explain architecture or a subsystem; trace a request, runtime, control, or data flow for a concrete question or bug; analyze a branch, commit, diff, or pull request for behavioral impact and blast radius; or assess AI-generated or changed code against requirements, contracts, invariants, tests, and runtime evidence. Default to read-only investigation. Do not trigger only because a coding task touches an existing repository; use when understanding or verification is the requested outcome or a substantial prerequisite.
日本語の概要は準備中です。原文の説明を表示しています。
The Eterdis Strategy Diagnostic — an AI-guided conversation that helps leadership teams understand their strategic situation before committing to a direction. This is the entry point skill. It runs an open-ended discovery conversation, detects which strategic frameworks are most relevant, and produces a strategy-ready brief. Use this skill when someone asks for a general strategic assessment, when they don't know which framework they need, when they want to "figure out where we stand," or when they're preparing for a strategy engagement. This skill orchestrates other Eterdis skills — it does not replace them. Triggers on: "help me think through our strategy," "where should we start," "we need to figure out what's going on," "strategic health check," "prepare for a strategy review," or any open-ended request for strategic thinking. Based on 20 years of consulting practice by Eterdis (eterdis.com).
日本語の概要は準備中です。原文の説明を表示しています。
Continuous environmental scanning across six PESTEL categories — Political, Economic, Social, Technological, Environmental, Legal. Not a one-time analysis but an ongoing radar. Three modes. Diagnostic mode runs a full scan and prioritises forces by impact, speed, and reversibility. Review mode checks the watch list monthly for movement and new signals. Alert mode defines concrete monitoring triggers for each top force. Use whenever someone wants to understand external forces acting on their business, assess macro risk, prepare for planning, or check whether the world has moved since last time they looked. Connects to the strategy map (forces act on the chain) and Wardley Map (forces drive component evolution). Based on practice by Eterdis (eterdis.com).
日本語の概要は準備中です。原文の説明を表示しています。
Culture assessment and monitoring with three modes — Diagnostic for a deep session surfacing the gap between declared culture and actual culture, Review for periodic check-ins on whether behavior is shifting, and Alert Triggers for setting tripwires around culture-strategy misalignment, regression, and integration risk. Not a culture change programme — a mirror. Updates company-context.md after every run. Triggers on questions about culture, values, team dynamics, how decisions really get made, why change efforts stall, merger integration, or whether the organisation can actually execute its strategy. Based on practice by Eterdis (eterdis.com).
日本語の概要は準備中です。原文の説明を表示しています。
First-principles strategy — strip away conventional assumptions and find the theoretical maximum for your business. Three modes. Diagnostic mode runs a full session (45+ min) to define your theoretical maximum, map the gap honestly, classify constraints, invert for failure modes, set strategic intent, and work backwards to your first intervention. Review mode (15-20 min) checks whether your theoretical maximum has shifted, whether the gap has changed, and whether you're still climbing the right peak. Alert mode defines constraint-shift, peak-shift, and local-peak triggers that tell you when to reassess. Use when someone is stuck optimising incrementally, when conventional wisdom is driving strategy, when a new technology or regulation changes what's physically possible, or when you suspect the business is climbing a local peak. Integrates with company-context.md. Based on practice by Eterdis (eterdis.com).
日本語の概要は準備中です。原文の説明を表示しています。
Strategy map analysis using the Eterdis two-directional causal chain. Use this skill to diagnose whether strategy is coherent by building two chains — bottom-up from resources to results, top-down from expectations to requirements — and finding where they don't connect. Runs in three modes — full diagnostic for deep sessions, review mode for quick re-assessment, and alert triggers for early-warning signals. Updates company-context.md after every run. Triggers on questions about strategic alignment, why the strategy isn't working, what to invest in, how the business creates value, whether the plan is realistic, or where the biggest gap is. Based on practice by Eterdis (eterdis.com).
日本語の概要は準備中です。原文の説明を表示しています。
Wardley Mapping for strategic positioning — map your value chain from customer need to underlying components, plot where each component sits on the evolution curve (novel to commodity), and spot the strategic plays that movement creates. Use this skill when someone wants to understand where their industry is heading, whether they're building things they should be buying, where competitors are vulnerable, what's about to become commoditised, or why their competitive advantage is eroding. Triggers on questions about build-vs-buy, component evolution, value chain analysis, commoditisation risk, or strategic positioning relative to market movement. Three modes — full diagnostic (build a map from scratch), review (update positions and reassess), and alert triggers (set tripwires for when components move). Based on practice by Eterdis (eterdis.com).
日本語の概要は準備中です。原文の説明を表示しています。
运用《大厂人才》(娄珺) 的祛魅框架与人才盘点方法评估组织的人才管理实践。适用于用户要做团队人才盘点或梯队规划、评估是否引入 OKR/价值观考核/去 KPI 等大厂工具、设计干部选拔与晋升标准、以及诊断考核制度为何流于形式时使用。
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
日本語の概要は準備中です。原文の説明を表示しています。
Assess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work. Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive Azure compliance and security auditing capabilities including best practices assessment, Key Vault expiration monitoring, and resource configuration validation. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expirati...
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "pentest AWS", "test AWS security", "enumerate IAM", "exploit cloud infrastructure", "AWS privilege escalation", "S3 bucket testing", "metadata SSRF", "Lambda exploitation", or needs guidance on Amazon Web Services security assessment.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.
日本語の概要は準備中です。原文の説明を表示しています。
Use when assessing AI/ML systems for prompt injection, jailbreak vulnerabilities, model inversion risk, data poisoning exposure, or agent tool abuse. Covers MITRE ATLAS technique mapping, injection signature detection, and adversarial robustness scoring.
日本語の概要は準備中です。原文の説明を表示しています。
Set up AI Runway on AKS — from bare cluster to running model. Covers cluster verification, controller install, GPU assessment, provider setup, and first deployment. WHEN: "setup AI Runway", "onboard AKS cluster", "install AI Runway", "airunway setup", "deploy model to AKS"...
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "implement LLM-as-judge", "compare model outputs", "create evaluation rubrics", "mitigate evaluation bias", or mentions direct scoring, pairwise comparison, position bias, evaluation pipelines, or automated quality assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Detects and prevents code injection attacks targeting serverless functions (AWS Lambda, Azure Functions, Google Cloud Functions) through event source poisoning, malicious layer injection, runtime command execution, and IAM privilege escalation via function modification. The analyst combines static analysis of function code, CloudTrail event correlation, runtime behavior monitoring, and IAM policy auditing to identify injection vectors across the expanded serverless attack surface including API Gateway, S3, SQS, DynamoDB Streams, and CloudWatch event triggers. Activates for requests involving Lambda security assessment, serverless injection detection, function event poisoning analysis, or serverless privilege escalation investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute authorized vishing (voice phishing) pretext calls to assess employee susceptibility to social engineering and evaluate security awareness controls.
日本語の概要は準備中です。原文の説明を表示しています。
Collects and synthesizes open-source intelligence (OSINT) about threat actors, malicious infrastructure, and attack campaigns using publicly available data sources, passive reconnaissance tools, and dark web monitoring. Use when investigating external threat actor infrastructure, performing pre-engagement reconnaissance for authorized red team assessments, or enriching CTI reports with publicly available adversary context. Activates for requests involving Maltego, Shodan, OSINT framework, SpiderFoot, or infrastructure reconnaissance.
日本語の概要は準備中です。原文の説明を表示しています。