AC st-ent-mcp-install
Install, wire, and verify the 699pic enterprise MCP server from the GitHub repository https://github.com/st699pic/st-ent-mcp . Use when the user asks to 安装 st-ent-mcp、接入 699pic MCP、配置 OpenClaw/Claude/Codex 的 MCP、克隆并注册这个仓库,或 when a local MCP install workflow is needed for the 699pic enterprise OpenAPI server.
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (st-ent-mcp-install) differs from the folder (st-ent-skills-install)
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 4 branches
- 100Steps. 29 steps
- 100Execution cost. Instruction body is 809 tokens
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
- +1No license
- +2Single-language instructions
- +3Description length 309: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.