Project Manager Skill

Assist with objective product research by analyzing strengths, weaknesses, risks, user value, and providing balanced improvement suggestions.

Security Scan

The skill is an instruction-only product-research template whose requirements and runtime instructions are consistent with its stated purpose and request no credentials or installs.

Purpose & Capability

Name and description claim product research and the SKILL.md is a focused framework for strengths, weaknesses, user value, and verdicts. There are no unrelated requested binaries, env vars, or config paths.

Instruction Scope

The instructions are scoped to analyzing products (questions, output format, evaluation criteria). They do not instruct the agent to read files, access environment variables, contact external endpoints, or collect system data.

Install Mechanism

No install spec and no code files — instruction-only. Nothing is written to disk and no external packages or download URLs are required.

Credentials

The skill declares no required environment variables, credentials, or config paths. There is no disproportionate credential access for the stated functionality.

Persistence & Privilege

Flags show always:false and normal autonomous invocation allowed. The skill does not request persistent presence, nor does it instruct modifying other skills or system settings.

Assessment

This skill is a harmless, self-contained template for product analysis. It is safe to install from a permissions standpoint because it asks for no credentials or installs. Consider: (1) provide the agent with concrete product context (links, specs) when requesting analysis so results are grounded; (2) review any external data the agent fetches using other tools or plugins — the skill itself does not instruct network access but the agent could use other capabilities to look up information; (3) verify sensitive or proprietary inputs are not sent to external services. If you need the agent to research live data, confirm which other skills/tools the agent will use and what credentials they require.

Product Research Assistant / 产品研究助手

Core Principle

优点和缺点同等重要，缺点比优点更关键。 Strengths and weaknesses are equally important. Weaknesses are MORE critical.

Research Framework

1. Strengths (优点)

• 产品解决了什么实际问题？
• 相比同类产品的核心优势是什么？
• 技术/功能/体验上有哪些亮点？

2. Weaknesses & Risks (缺点 & 风险) — MORE IMPORTANT

每个缺点必须包含：

维度	内容
问题描述	具体哪里不足、有什么问题
用户痛点	对用户实际造成什么影响
风险级别	Low / Medium / High / Critical
改善方向	可行的解决方案、优化方向

重点关注：

• 产品本身的功能缺陷或设计问题
• 商业可行性风险（盈利模式、市场竞争）
• 用户体验痛点（上手难、用完即走）
• 安全隐私风险
• 可扩展性/技术债务

3. User Value (对用户的实际价值)

• 能解决什么问题？
• 目标用户是谁？
• 替代方案是什么？本产品优势在哪里？
• 投入产出比如何？

4. Verdict (最终结论)

• 用户是否应该接受/认可/满意？
• 核心原因（不超过3点）
• 最大顾虑（1-2点）
• 改善优先级建议

Output Format / 输出格式

# [Product Name] 产品分析报告

## 优点 Strengths
...

## 缺点与风险 Weaknesses & Risks
| 问题 | 痛点 | 风险等级 | 改善方向 |

## 用户价值 User Value
...

## 结论 Verdict
✅ 推荐 / ⚠️ 谨慎 / ❌ 不推荐
原因：...
最大顾虑：...

Key Reminders

• 不只吹捧，不回避问题
• 客观、全面、落地
• 围绕用户需求展开
• 每个分析最终目标：让产品被用户真正接受、认可、满意