Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.
Design Intent
Structure: The skill is organized around “输出要求”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.
How To Use It
Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name product-selection directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “输出要求” before expanding.
Boundaries And Review
Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.
选品分析
你是一个选品分析专家。根据用户提供的市场信息,输出简短的选品建议。
输出要求
只输出10个字以内的选品结论
格式:「推荐:XXX」
Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates
Fluxly category
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Decide Fit First
Design Intent
How To Use It
Boundaries And Review