error: YAML frontmatter could not be parsed: Unexpected flow-seq-start at node end at line 2, column 51:
description: "Gunakan skill ini saat: step task?" [shape=diamond];; plans" [sha…
^
SKILL.md
error: YAML frontmatter could not be parsed: Unexpected flow-seq-start at node end at line 2, column 51:
description: "Gunakan skill ini saat: step task?" [shape=diamond];; plans" [sha…
^
SKILL.md
error: YAML frontmatter could not be parsed: Unexpected flow-seq-start at node end at line 2, column 51:
description: "Gunakan skill ini saat: step task?" [shape=diamond];; plans" [sha…
^
SKILL.md
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
Status
completed
Coverage
full text content
Files
5 / 6 inspected as text
Checked
8/24/2026, 1:20:36 PM
Scanner
0.1.3
Policy
1.0.3
1 automated finding
mediumSKILL.md YAML frontmatter is invalidSKILL.md:1 · confidence 100%Unexpected flow-seq-start at node end at line 2, column 51: description: "Gunakan skill ini saat: step task?" [shape=diamond];; plans" [sha… ^
2 inferred permission indicators
network access — automatically inferred
filesystem write — automatically inferred
1 dependency and API indicators
api: clawhub.ai
External clawhub result: clean
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
Evidence checked
8/24/2026, 7:34:03 AM
Release binding
Matches this record
vt: clean
skillspector: suspicious
llm: clean
Recorded files
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
writing-plans 1.0.2 — Minor update - Clarified trigger description in SKILL.md for when the skill should activate. - Expanded and refined documentation on plan structure, usage context, scope, and task decomposition. - Reorganized instructions for writing and structuring implementation plans, including plan document headers and task granularity. - Added detailed file structure guidelines and updated best practices on file and task segregation. - Usage decision flowchart (dot graph) included for clearer activation criteria.
Release security diff
mediumCompared fixed releases 1.0.1 and 1.0.2; 1 finding and 0 permission indicators were added.
Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.
Change reasons and limitations
finding surface changed
content hash changed
Observed release history
These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.