Frontend Tech Doc Guide
v1.0.0规范 AI 生成飞书技术文档结构，确保 Markdown 层级正确、章节顺序稳定、可读性高。
⭐ 0· 74·1 current·1 all-time
bylaner@kelaner
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description claim a doc-generation/style guide for Feishu frontend tech docs; the SKILL.md contains only rules and templates for that task. There are no unrelated required binaries, env vars, or install actions.
Instruction Scope
Instructions are narrowly focused on generating Markdown with specific structure, layout, and Mermaid usage and do not instruct the agent to read files, access credentials, or transmit data externally. Minor oddities: very strict formatting rules (e.g., 'Mermaid only once', 'use <br/> instead of \n', 'no explanatory text, only Markdown') could cause generation failures or hide contextual output, but they are within the documented purpose.
Install Mechanism
No install spec and no code files — lowest-risk instruction-only skill. Nothing will be written to disk or fetched during install.
Credentials
The skill requires no environment variables, credentials, or config paths; requested access is proportional (none) to the stated purpose.
Persistence & Privilege
Skill metadata contains an 'auto':true field (in SKILL.md metadata), and the platform defaults permit autonomous invocation. The registry flags show always:false, so it is not force-included in every agent run. Consider whether you want a skill that can be auto-invoked by agents.
Assessment
This skill appears internally consistent and low-risk: it only contains formatting rules for producing frontend tech docs and does not request credentials or install code. Before installing: (1) Confirm you want an instruction-only skill that enforces 'only output Markdown' and suppresses explanatory text — this can make debugging harder. (2) If you do not want automatic runs, check how your agent platform handles the SKILL.md metadata ('auto':true) and disable autonomous invocation if needed. (3) Test the skill with non-sensitive sample prompts to ensure its strict rules don't produce broken output (especially the Mermaid/<br/> requirement). Request the publisher/source if you need provenance or updates. If any code files, network endpoints, or credential requests appear later, re-evaluate immediately.Like a lobster shell, security has layers — review code before you run it.
latestvk97a1aeenwcrreqrmt3v3xs8n983qdwf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📚 Clawdis