BD bangunai-blog-manager
Use when managing BangunAI Blog content, automating blog workflows, and writing MDX articles with BangunAI conventions. Supports Obsidian-like features (callouts, mermaid, LaTeX, wikilinks, backlinks, graph view).
As a process D 47/100 · Unfinished process — weak spots: when it triggers, inputs and preconditions, failures and branches
ProcedureObsidianLaTeXWriting and documentsInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5647 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 47/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 7 mutating operations with no state check
- 40Consistency. Frontmatter name (bangunai-blog-manager) differs from the folder (tulisai)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 5647 tokens
- 100Steps. 113 steps
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (6 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)
- -4Absolute local paths (C:\Users, /home/…): not portable
- -2localhost URLs: will not work for another user
- -220 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 213: enough signal without eating the budget
- +4Structure: 58 headings
- +3Step-by-step instructions: 113 items
- +3Output format is stated explicitly
- +4Has examples (52 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.
External checks
ClawHub: clean
This is a documentation-only skill for managing a specific blog workspace; its file writes and git examples are disclosed and purpose-aligned, but users should confirm overwrites, deletes, and pushes.
LLM: benign (high) · VirusTotal: suspicious · 28 May 2026