CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md，其中包含认证、权限处理
Works with
CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md，其中包含认证、权限处理
lark-cli schema wiki.<resource>.<method> # 调用 API 前必须先查看参数结构
lark-cli wiki <resource> <method> [flags] # 调用 API
重要：使用原生 API 时，必须先运行
schema查看--data/--params参数结构，不要猜测字段格式。
get — 获取知识空间信息get_node — 获取知识空间节点信息list — 获取知识空间列表copy — 创建知识空间节点副本create — 创建知识空间节点list — 获取知识空间子节点列表| 方法 | 所需 scope |
|---|---|
spaces.get |
wiki:space:read |
spaces.get_node |
wiki:node:read |
spaces.list |
wiki:space:retrieve |
nodes.copy |
wiki:node:copy |
nodes.create |
wiki:node:create |
nodes.list |
wiki:node:retrieve |
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionlark-wikiExecute the skills CLI command in your project's root directory to begin installation:
Fetches lark-wiki from larksuite/cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate lark-wiki. Access via /lark-wiki in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
2
total installs
2
this week
6.8K
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
6.8K
stars
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
We added lark-wiki from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: lark-wiki is the kind of skill you can hand to a new teammate without a long onboarding doc.
lark-wiki fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend lark-wiki for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
lark-wiki reduced setup friction for our internal harness; good balance of opinion and flexibility.
lark-wiki has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for lark-wiki matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: lark-wiki is focused, and the summary matches what you get after install.
lark-wiki reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for lark-wiki matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 50