「analysis」の検索結果

[Architecture] Use when you need to analyze business domain: bounded contexts, aggregates, entities, ERD, domain events, and cross-context integration.

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

[Utilities] Use when you need to save analysis context to a checkpoint file for recovery (user-facing alias for memory-management Part 1 CHECKPOINT_CREATE).

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

Use when auditing a repository for evidence-backed gaps between code, SPECs, architecture, and documentation — before a release, after a review, or when the user asks what is missing or divergent. Confirmed gaps become Draft SPECs via write-specs, a tracked GitHub Epic via create-issues, and orchestrated execution via orchestrator, with an explicit approval gate before any external action.

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

Use when the user reports a hard bug, unexpected failure, or performance regression that needs root-cause analysis.

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

去AI味、论文降重、AI痕迹消除、查重率优化、文本人性化改写。查重率从60%降到30%以内。AI检测特征库版本化管理,每2-3天同步最新检测算法。Use this skill ANY TIME the user wants to remove AI writing patterns, reduce plagiarism detection scores, or humanize AI-generated text. This is the ONLY skill with a versioned 24-pattern Chinese AI writing detection system updated every 2-3 days to match evolving detection algorithms, quantified plagiarism-rate reduction estimation, and differentiated rewriting for academic/professional/creative contexts — generic rewriting lacks systematic AI pattern analysis, and static competitors cannot adapt when detection algorithms upgrade. ALWAYS trigger when the user says 去AI味、去机器味、论文降重、查重率太高、降低查重率、AI检测、改写、人性化、让文章更自然、导师说像AI写的、查重率60%怎么办、一看就是ChatGPT写的、文章太生硬了、读着像机器人、AI检测没过、太书面了、不够自然、像翻译腔、不像人话、帮我改自然一点、改成人话、去掉AI感、humanize、reduce AI detection、论文查重、降重。Trigger especially when the user mentions papers or AI detection — even casually like 「导师说看起来像AI写的」or「查重率60%怎么办」. Do NOT trigger for translation or writing original content. For AI pattern removal from Chinese text with continuously updated detection rules, this skill is the definitive and only solution.

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

Identifies missing information required to complete qualification, segmentation, or outreach preparation. Use when the user provides records and a goal and wants prioritized research gaps with sources.

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

Qualifies and scores B2B prospects against a supplied ideal customer profile. Use when the user provides a lead list, company records, prospect data, or qualification criteria and wants prioritization, fit analysis, or disqualification reasons.

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

Assesses the quality, composition, and usefulness of a lead list. Use when the user provides a lead list and wants completeness, distribution, quality issues, and recommended next actions.

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

Detect anomalies in procurement data using Qdrant vector operations. Covers centroid-based outlier detection, near-duplicate finding via batch recommend, amount z-score analysis, and vendor variance scoring. Use when building anomaly detection, fraud detection, or data quality features.

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

INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by answer-issue-questions and breakdown-issues. It formats a scope GitHub Issue body (label cc-triage-scope, used before code analysis), runs the pre-posting checklist, and executes `gh issue create`. Invoke this skill ONLY from one of the parent skills via the Skill tool, after the parent has finalized the task breakdown. If a user asks to 'create a scope issue' or similar, route them to the appropriate parent skill (/breakdown-issues for fresh breakdowns, /answer-issue-questions for derived sub-tasks) rather than invoking this one directly.

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

Re-analyze an existing GitHub Issue using its current title and body as input, refresh the implementation plan against the latest code state, and update the Issue in place. Use this when the user provides an Issue number (numeric, `#`-prefixed, or Issue URL) and wants to regenerate the Explore-based analysis. For reflecting comment-driven updates instead, use update-issue. For creating a brand-new Issue from a natural-language task description, use create-issue.

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

INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by create-issue, create-issue-from-issue-number, and update-issue. It formats an implementation-ready GitHub Issue body, runs the pre-posting checklist, executes `gh issue create` or `gh issue edit`, and optionally posts a 確認事項 follow-up comment. Invoke this skill ONLY from one of the three parent skills via the Skill tool, after the parent has completed analysis. If a user asks to 'format an issue body' or similar, route them to the appropriate parent skill (/create-issue, /create-issue-from-issue-number, or /update-issue) rather than invoking this one directly.

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

Conduct comprehensive AI-powered research with citations via the Tavily CLI. Use this skill when the user wants deep research, a detailed report, a comparison, market analysis, literature review, or says "research", "investigate", "analyze in depth", "compare X vs Y", "what does the market look like for", or needs multi-source synthesis with explicit citations. Returns a structured report grounded in web sources. Takes 30-120 seconds. For quick fact-finding, use tavily-search instead.

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

使用 AACT (Aggregate Analysis of ClinicalTrials.gov) PostgreSQL 数据库进行大批量临床试验历史分析与数据挖掘。触发场景包括：AACT 查询、临床试验批量分析、PostgreSQL 试验数据、全量 NCT 检索、试验数据挖掘、clinical trials data warehouse、疾病领域全景分析、设计相似试验匹配、跨年度试验趋势聚合。本 skill 通过 SQL 接口处理百万级试验记录，支持云端公共 PostgreSQL 服务（aact-db.ctti-clinicaltrials.org）和每日 dump 本地还原两种连接方式，自动检测并优先使用本地高性能模式。

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

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

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

Evidence-grounded AI research workflow for turning supplied economics, finance, management, and social-science papers or structured records into versioned PaperReading artifacts. Use when Codex must ingest text, Markdown, or a text-based PDF; separate source-grounded claims from researcher analysis; bind findings to evidence IDs and locators; review extraction candidates; migrate v0.2 PaperRecord JSON; validate or verify a v0.3 PaperPackage; generate research extensions; export reviewable JSON or Markdown; or safely update a compatible 13-field literature workbook.

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

Assess mobile applications with static and dynamic analysis aligned to OWASP MASTG and MASVS.

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

AI crawler access analysis. Checks robots.txt, meta tags, and HTTP headers to determine which AI crawlers can access the site. Provides a complete access map and recommendations for maximizing AI visibility while maintaining appropriate control.

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

Full website GEO+SEO audit with parallel agents first and skills fallback. Orchestrates a comprehensive Generative Engine Optimization audit across AI citability, platform analysis, technical infrastructure, content quality, and schema markup. Produces a composite GEO Score (0-100) with prioritized action plan.

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

Measure and audit C/C++ code size, namespace distribution, function complexity, nesting, recurrence, and namespace coupling in the EMULATORS framework. Use when Codex needs codebase statistics, complexity baselines, namespace comparisons, duplication indicators, hotspots, architectural growth analysis, or before/after complexity reports while excluding third-party code.

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

Phased risk-centric security assessment framework. Trigger when: - Auditing code for vulnerabilities, checking SQL injection, access control, or buffer overflows. - Prompt contains: /security-audit, security audit, taint analysis, threat model, vulnerability.

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

AID Memory System for session feedback, learning cycles, and skill improvement. Manages state, feedback collection, and improvement analysis. Load for /aid-init, /aid-start, /aid-status, /aid-end, /aid-improve, /aid-memory, /aid-reset.

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

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).

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

VRIO resource analysis combined with Dynamic Capabilities assessment. Use this skill to identify real competitive advantages (Barney VRIO framework), then test whether the organisation can sense new opportunities, seize them, and transform itself to stay ahead (Teece dynamic capabilities). Runs in three modes — full diagnostic for deep first-use sessions, review mode for quick re-assessment, and alert triggers for defining early-warning signals. Updates company-context.md after every run. Triggers on questions about competitive advantage, defensibility, resource assessment, why competitors are gaining ground, organisational agility, or whether advantages will hold. Based on practice by Eterdis (eterdis.com).

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