Pick Project Type First, Not Skills
Many people start by browsing ClawHub’s 5,700+ skills and picking what looks powerful. A steadier order is:
- Choose project type
- Decide which capabilities you need
- Then select skills, models, and channels
Suitable vs Not Suitable
Suitable for first projects
- Clear input source—links, docs, messages, or tables
- Visible output—Feishu docs, messages, structured tables
- Defined success—saves time, stable format, less repetition
- MVP within a week, not full automation from day one
Not suitable for first batch
- Multiple high-permission channels, third-party skills, and model routing at once
- No clear deliverable beyond “make it smarter”
- No human reviewer, but AI should post, write, or decide autonomously
- Input fields undefined, yet automation expected first
Five Project Types
| Type | Examples | Best for |
|---|---|---|
| Personal side hustle | Daily digests, content collection, research aggregation | One person, clear I/O, low dependency |
| Team efficiency | Feishu assistant, message summaries, docs and tasks | Stable chat entry, internal output |
| Client delivery | Fixed scope, defined success, template-driven | Clear boundaries and acceptance criteria |
| Content automation | Daily News Run, content ops, SEO queue | Existing content pipeline, willing to chain skills |
| Research / analysis | Data cleaning, report generation, due diligence | Fixed research input and output format |
Selection Priority
- Can I describe input and output clearly?
- What is the minimum viable delivery?
- Does it require many permissions and tools at once?
- Can I define success criteria?
Minimum Viable Delivery Template
Fill this before building. If you cannot, the project is not ready.
Project name:
Target users:
Input:
- Where it comes from
- Who provides it
- Update frequency
Output:
- Feishu doc / message / table / file
- Who reviews it
First version only:
1.
2.
3.
First version explicitly not:
1.
2.
Success criteria:
- Time saved
- Output stability
- Reusability
Related Pages
-
Models — decide model and routing
-
Skills — baseline capabilities
-
First config — stabilize initial setup
-
Content & media — content automation
-
E-commerce — product research and listing
-
HR — resume screening and knowledge base
-
Legal — document review and clause comparison
-
Official docs → docs.openclaw.ai
-
Issues → GitHub Issues