BB lan-folder-share
Publish any local folder as a web link everyone on your LAN can open in one click — browse and search Markdown docs, Excel/CSV sheets, HTML reports, images and videos online. No database, no pre-configuration; file changes appear on refresh. 一键把本地文件夹/目录打包发布为局域网内人人可打开访问的网页链接，无需数据库与任何预配置，同事可在线浏览 Markdown 文档、Excel/CSV 表格、HTML 报告、图片画廊、视频并全文搜索，文件增删改动刷新页面即生效（服务端实时扫描目录，无需重启）。Use when user wants to share a local folder or files with colleagues over the LAN ("share this folder on the LAN", "give the team an online link to browse docs", "LAN knowledge base / file server", "one-click web sharing of a directory"), or 当用户想把本地目录/文档/文件分享给同事或局域网内其他人访问，如"把 XX 文件夹分享到局域网""给团队一个在线看文件的链接""局域网共享文件夹/文件""一键把目录发布成可访问网页/链接"等诉求。WARNING: the HTTP server has no authentication — anyone reachable on your LAN can open the link and browse everything in the shared folder, so only share folders that contain no sensitive or private files; 警告：HTTP 服务无鉴权，局域网内任意可达设备均可打开链接浏览共享目录的全部内容，请勿分享含敏感/私密文件的目录。
Publish any local folder as a web link everyone on your LAN can open in one click — browse and search Markdown docs, Excel/CSV sheets, HTML reports, images…
As a process B 67/100 · Nearly there — weak spots: result and completion, running it twice
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 19. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Publish any local folder as a web link everyone on your LAN can op… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 975 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "permissions"
Process rating: all ten parameters 67/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 10 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 34 steps, 2 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2524 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 975: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +4Structure: 13 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.