“scope”的搜索结果

Find Amazon same-niche competitors by ASIN, with multi-dimensional filtering by click conversion rate, composite conversion rate, click volume, sales volume, reviews, ratings, price, and gross margin to identify potential competitors. Triggered when users mention same-niche competitors, ASIN competitor mining, niche competitor analysis, similar product benchmarking, ASIN benchmarking, niche market competitor list, high-conversion competitor screening, Nexscope product mining, niche competitor by ASIN, ASIN competitor analysis, same niche products, similar products discovery, conversion rate comparison, potential competitor screening, Nexscope ASIN mining. Even if users do not explicitly mention "niche" or "same niche", this skill should be triggered whenever the task involves discovering competitor lists or screening potential competitors based on a specific ASIN within the same market segment.

中文简介正在准备中。当前显示原文说明。

Break down all competitor ASIN traffic sources under a given keyword -- organic search, SP ads, SB brand ads, SBV video ads, SP recommendations, AC/ER/TR recommendation slots, with support for ASIN filtering, custom date ranges, and new traffic keyword filters. Trigger when the user mentions keyword traffic sources, which competitors are grabbing traffic under this keyword, organic traffic vs paid traffic share, SP ad exposure, brand ad share, SP recommendation slots, recommendation ad/non-ad split, search display analysis, Amazon's Choice or editorial recommendation exposure, keyword competitive landscape, ASIN traffic composition, keyword traffic, traffic structure analysis, search share, ad share, traffic source distribution, Nexscope, traffic analysis, SP recommendation, recommend position breakdown. Even if the user does not explicitly mention "Nexscope", if their need involves analyzing competitor ASIN traffic source distribution under a keyword, this skill should also be triggered.

中文简介正在准备中。当前显示原文说明。

Query Amazon product historical time-series data, including price trends, BSR (Best Sellers Rank) trends, rating changes, seller counts, and monthly sales, supporting any ASIN across multiple Amazon marketplaces. Triggered when users mention price history, price tracking, BSR history, BSR trends, historical pricing, price fluctuations, Nexscope data, rank history, price drop alerts, lightning deal historical prices, Buy Box price trends, coupon prices, FBA/FBM price comparison, seller count changes, rating trends, sales history. Even if users do not explicitly mention "Nexscope" or "time-series data", this skill should be triggered whenever the task involves analyzing Amazon product-level historical data (such as price, rank, or sales trends over time).

中文简介正在准备中。当前显示原文说明。

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).

中文简介正在准备中。当前显示原文说明。

Parse HackerOne / Bugcrowd / Intigriti scope into a structured asset list with in-scope, out-of-scope, and excluded-vuln-class breakdowns. Use when the user has chosen a program and needs to understand exactly what's allowed before recon.

中文简介正在准备中。当前显示原文说明。

Draft a project charter that defines scope, stakeholders, success criteria, and initial risk register. Covers problem statement, RACI matrix, milestone planning, and scope boundaries for both agile and classic methodologies. Use when kicking off a new project or initiative, formalizing scope after an informal start, aligning stakeholders before detailed planning begins, or transitioning from discovery to active project work.

中文简介正在准备中。当前显示原文说明。

对 msMemScope 显存数据做全链路处理：根据用户的显存问题诉求（OOM、显存泄漏、显存占比拆解、Step 间对比等），指导并帮助用户以最合适的 msMemScope 采集配置完成显存数据采集（支持命令行、Python 接口、mstx 打点三种采集方式，覆盖训练、推理 vLLM-Ascend、FSDP、强化学习 verl 等场景）；对已采集的 memscope_dump_*.csv/db 数据做系统性解读与问题诊断（整体显存曲线趋势分析、显存使用大头按模块/组件拆解分析、显存峰值点各模块与流程占比分析，以及对显存泄漏、OOM 等典型问题的根因定位与原因分析）。

中文简介正在准备中。当前显示原文说明。

Use when developing in packages/agent-core-v2 (the DI × Scope agent engine) — adding or modifying a domain Service, choosing a LifecycleScope, wiring DI dependencies, splitting a domain across scopes, owning or migrating a config section, gating behavior behind an experimental flag, raising coded errors, working on the permission system, writing DI/Scope tests, porting business logic from agent-core (v1) to v2, triaging a main-branch commit against v2, or exposing a v2 domain over server-v2 while keeping the /api/v1 wire contract compatible with released clients. Self-contained guide organized by development stage (orient → design → implement → test → verify) plus align workflows for v1→v2 migration, main-branch commit triage, and server-v2 wire exposure; each file carries the rules, examples, and red lines for its step.

中文简介正在准备中。当前显示原文说明。

scope.md をもとに Next.js アプリを projects/<name>/apps/ に実装する対話スキル。MVP を一括生成したあと「完了」で終わらず、想定ユーザー1人になりきって触る → 1サイクル1改善のチューニングを回し続けて体験を磨く。/scope-design の後、/verify-project の前に実行する。/build-app で明示起動。

中文简介正在准备中。当前显示原文说明。

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).

中文简介正在准备中。当前显示原文说明。

Session-scoped directory edit restriction. Blocks Edit and Write outside the allowed path for the current session only. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits". NOT for blocking destructive shell commands (see mk:careful).

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

Responsive scope: production-level createScope lifecycle, media query gating, cleanup. Use when implementing, reviewing or testing responsive scope for React, Vite, Next.js or Perfect_AI projects.

中文简介正在准备中。当前显示原文说明。

Use when working with Descope — descope authentication and identity management platform covering users, tenants, access keys, flows, and audit logs. Use when analyzing user authentication patterns, monitoring tenant health, reviewing access key usage, managing Descope flows and roles, or auditing login activity.

中文简介正在准备中。当前显示原文说明。

直近N日（デフォルト1日）に更新された `cc-triage-scope` / `cc-pr-created` ラベル付きGitHub Issueのdescriptionとコメントを横断し、繰り返し現れる仕様判断・要件決定のロジックを再利用可能なルールとして抽出して `.claude/requirements/` 配下のタイプ別マークダウンへ集約・統合・圧縮したうえで、commit-push + create-prでPRを作成する（`cc-triage-scope`ラベル + 自分自身をAssignee）。作成したルールは create-issue / create-issue-from-issue-number / answer-issue-questions が仕様作成・判断の材料として読み込む。

中文简介正在准备中。当前显示原文说明。

INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by 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 parent skill (/breakdown-issues) rather than invoking this one directly.

中文简介正在准备中。当前显示原文说明。

读取Git差异和近期提交历史，按Conventional Commits格式及仓库惯例拟写或修改提交消息，调整类型、范围和长度，并建议拆分无关改动。

• 提交前拟写提交消息
• 检查并修改已有提交消息
• 编写拉取请求的简短摘要

根据当前使用的智能体环境，引导完成ECC的安装、更新和重新配置。从检查安装状态、预览变更、确认与应用，到验证结果，均以对话方式推进。

• 安装或更新ECC
• 迁移Claude Code中的安装范围
• 调整Claude Code中的钩子

将 Git 差异与修改目的对照，找出可能无关的文件、新增依赖等范围扩张信号，给出保留、拆分或说明必要性的判断，并整理拆分方案。

• 创建拉取请求前检查修改范围
• 发现混入缺陷修复的额外修改
• 检查暂存修改是否范围过大

在实施前审视开发计划的目标和前提，比较不同方案与工作范围，并检查设计、安全、测试和运维方面的问题，帮助决定后续实施方向。

• 重新审视计划的目标和前提
• 比较最小可行方案与理想架构
• 决定扩大或缩小工作范围

利用现有代码结构，在必要范围内实现新功能或外部集成。先明确可验证的完成条件和不包含的内容，再贯通相关层级，完成整套运行流程。

• 在明确范围内实现新功能
• 利用现有结构接入外部服务
• 明确完成条件与不包含的内容

将规格说明或需求拆分为带有完成标准和验证方法的小型实现任务，梳理依赖关系、执行顺序及检查节点，并保存为计划文档和任务清单。

• 把大型功能拆分为实现任务
• 按依赖关系安排执行顺序
• 明确完成标准和验证方法

通过OmniRoute命令行查看MCP服务器状态和工具权限范围，启用、停用或重启服务器，并使用JSON参数或参数文件调用工具以检查运行情况。

• 检查MCP服务器运行状态
• 启用、停用或重启服务器
• 查询工具的权限范围

Integrate GSAP animations into React and Next.js components using useGSAP, element references, and scoped selectors. The skill guides dependency updates, event callbacks, and cleanup when components unmount, while keeping animation code out of server rendering.

中文简介正在准备中。当前显示英语简介。

• Adding GSAP animations to React components
• Restricting animations to elements within one component
• Cleaning up animations when components unmount