BC Feishu Post (RichText) Skill
Send Rich Text (Post) messages to Feishu. This format is distinct from Cards. It supports native rich text elements but is less flexible in layout than cards. It is better for long-form text mixed ...
Send Rich Text (Post) messages to Feishu.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
Proceduretype 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 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:19High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…bR6+k7Fi…rEB/8rLw…bbj/Mp8TWH/v1O+p487m6xskxw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:34High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-j+gKEx…ahh+s1F2HZ+wAce…RkU++ZWQr…uoQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:80High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…rvP+yUUf…4tH/iSSo…tEA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:98High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…vPe+zGay…l5w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:107High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9dM/mwVgvbZJaSNaRk+bshk…Kbz+IoId…W0Q==",
detector
Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 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. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (Feishu Post (RichText) Skill) differs from the folder (feishu-post)
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 10 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 305 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 200: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.