安全扫描
OpenClaw
安全
high confidenceThe skill is an instruction-only helper for writing migration guides and its requested actions (reading optional project-context files and producing page content) align with its stated purpose.
评估建议
This is an instruction-only, self-contained skill to generate migration guides. It's coherent with its purpose and doesn't request credentials or installs. The only notable behavior is that, if present, it will read repository-local project-context files (.claude/project-context.md or .cursor/project-context.md) to tailor output — if those files contain sensitive information you don't want the agent to read, remove or sanitize them before invoking the skill.详细分析 ▾
✓ 用途与能力
The name and description match the instructions: the skill generates migration pages, suggests structure/SEO, and references related page types. It does not request unrelated credentials, binaries, or system access.
ℹ 指令范围
Runtime instructions are scoped to producing migration content and recommend reading project context files (.claude/project-context.md or .cursor/project-context.md) if present. Reading those specific repository files is reasonable for contextual output, but users should be aware the agent may access repo-local project-context files when available.
✓ 安装机制
No install steps or code are present (instruction-only). This minimizes on-disk changes and external code execution risk.
✓ 凭证需求
The skill declares no environment variables, credentials, or config paths beyond the optional project-context files. Requested access is proportional to the stated task.
✓ 持久化与权限
always is false and there are no requests to modify other skills or system settings. The skill can be invoked by the agent (default), which is normal for skills of this type.
安全有层次,运行前请审查代码。
运行时依赖
无特殊依赖
版本
latestv1.0.12026/3/23
Batch: integrations through solutions
● 无害
安装命令
点击复制官方npx clawhub@latest install migration-page-generator
镜像加速npx clawhub@latest install migration-page-generator --registry https://cn.longxiaskill.com镜像同步中
技能文档
Guides migration pages that help users switch from a competitor to your product. Reduces friction for switchers; often linked from alternatives pages. Common for SaaS, tools, and productivity apps.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, migration capabilities, and source platforms.
Identify:
- Source: Which competitor(s) to cover (Notion, Trello, etc.)
- Format: Single hub vs. per-competitor pages (/migrate-from-notion)
- Migration type: Manual import, automated tool, API
- Primary goal: Sign up, start migration, reduce churn risk
Page Structure
| Section | Purpose |
|---|---|
| Headline | "Migrate from [Competitor] to [Product] in Minutes" |
| Why switch | Brief; link to alternatives for full comparison |
| What transfers | Data, structure, attachments; what's supported |
| Steps | Numbered guide; screenshots or video |
| Troubleshooting | Common issues, support link |
| CTA | Start migration, try free, contact support |
Best Practices
Clarity
- Explicit steps: "1. Export from X. 2. Upload to [Product]. 3. Map fields."
- Time estimate: "Takes ~10 minutes for most workspaces"
- Data scope: What transfers; any limitations
Trust
- No competitor bashing: Focus on your product's ease
- Support: Offer help; link to docs, chat, email
- Success stories: "10,000+ teams migrated from X"
SEO
- Intent: Transactional; "migrate from X to Y"
- Title: "Migrate from [Competitor] to [Product] | Step-by-Step Guide"
- Internal links: Alternatives, features, pricing, docs
Output Format
- Headline and intro
- Step-by-step migration guide
- Data transfer scope
- Troubleshooting section
- Internal links
- SEO metadata
Related Skills
- alternatives-page-generator: Link to migration from alternatives
- docs-page-generator: Detailed migration docs
- landing-page-generator: Migration as conversion page
- faq-page-generator: Migration FAQ section