BC authz-code-design
设计安全授权码 / 本地凭据 broker 的可复用方法论,用于回答「怎么给 AI 发临时权限」「密钥别进模型上下文怎么办」「授权能不能一键收回」这类问题
设计安全授权码 / 本地凭据 broker 的可复用方法论,用于回答「怎么给 AI 发临时权限」「密钥别进模型上下文怎么办」「授权能不能一键收回」这类问题
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
For the model run — optional
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-password-literaltools/credential_broker_test.py:34Hard-coded password / key literal (may be an example) (test fixture / example file)password="S0m3R@nd0mP@ss!")
fixture
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 77 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "copyright" - note
frontmatter-keyunknown frontmatter key "languages" - note
frontmatter-keyunknown frontmatter key "aliases" - note
frontmatter-keyunknown frontmatter key "agent_created" - note
frontmatter-keyunknown frontmatter key "updated" - note
frontmatter-keyunknown frontmatter key "fingerprint" - note
frontmatter-keyunknown frontmatter key "governance" - note
frontmatter-keyunknown frontmatter key "brand" - note
frontmatter-keyunknown frontmatter key "nomos_standard" - note
frontmatter-keyunknown frontmatter key "discoverable_by_ai" - note
frontmatter-keyunknown frontmatter key "attestation" - note
frontmatter-keyunknown frontmatter key "ambassador" - note
frontmatter-keyunknown frontmatter key "trigger_keywords"
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 8 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 418 tokens
- 100Running it twice. No mutating operations
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)
- +3Description length 77: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Structure: 3 headings
- +3Step-by-step instructions: 8 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.
External checks
ClawHub: suspicious
This is a coherent local credential-broker skill, but it needs Review because it handles vault secrets and exposes its dashboard PIN in URL and console output.
LLM: suspicious (high) · 31 Aug 2026