BD webchat-extension
部署「网页划线对话」浏览器扩展(Chrome MV3 / 兼容 Chrome·Edge·千问·夸克 等 Chromium 内核浏览器)。在任意网页选中文字,点工具栏图标唤起可拖动对话浮层,带着网页上下文用 CodeBuddy AI 流式问答。包含本地 Express + SSE 后端(CodeBuddy Agent SDK)与前端扩展。当用户要「做一个网页划词对话插件 / 给浏览器装个网页对话工具 / 选中文字问 AI / 部署小虾网页对话扩展 / web highlight chat extension / 把网页内容丢给 AI 聊」时使用本技能。
部署「网页划线对话」浏览器扩展(Chrome MV3 / 兼容 Chrome·Edge·千问·夸克 等 Chromium 内核浏览器)。在任意网页选中文字,点工具栏图标唤起可拖动对话浮层,带着网页上下文用 CodeBuddy AI 流式问答。包含本地 Express + SSE 后端(CodeBuddy Agent…
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 7
✓ No critical or high findings
Medium and low: 7
-
low Secrets in code
secret-high-entropy-tokenassets/backend/package-lock.json:81High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLi+2W/6ao+6Y7gu/RCwR…Kng==",
detector -
low Secrets in code
secret-high-entropy-tokenassets/backend/package-lock.json:153High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLw+xYSd…cqA==",
detector -
low Secrets in code
secret-high-entropy-tokenassets/backend/package-lock.json:170High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…F4j+6INO…yXw==",
detector -
low Secrets in code
secret-high-entropy-tokenassets/backend/package-lock.json:243High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…W6v+zr+RRp+hqUL…4uQ==",
detector -
low Secrets in code
secret-high-entropy-tokenassets/backend/package-lock.json:289High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Jqj+nOOr…S5A==",
detector -
low Exfiltration
read-dotenvassets/root/README.md:52Reads a .env filecp .env.example .env # 然后按需填写 CODEBUDDY_API_KEY
-
low Exfiltration
read-dotenvreferences/deploy-guide.md:20Reads a .env file (documentation table row)| 复制配置 | `cp .env.example .env` | 按需填 `CODEBUDDY_API_KEY` |
table
Files scanned: 19. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 100Steps. 36 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1841 tokens
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (8 tags): a typed call is more reliable
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 278: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.