error: YAML frontmatter could not be parsed: Nested mappings are not allowed in compact mappings at line 2, column 14:
description: Plans a piece as a sequence of Phantra scenes before any is writte…
^
SKILL.md
error: YAML frontmatter could not be parsed: Nested mappings are not allowed in compact mappings at line 2, column 14:
description: Plans a piece as a sequence of Phantra scenes before any is writte…
^
SKILL.md
error: YAML frontmatter could not be parsed: Nested mappings are not allowed in compact mappings at line 2, column 14:
description: Plans a piece as a sequence of Phantra scenes before any is writte…
^
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
2 / 2 inspected as text
Checked
11/2/2026, 9:47:36 PM
Scanner
0.1.3
Policy
1.0.3
1 automated finding
mediumSKILL.md YAML frontmatter is invalidSKILL.md:1 · confidence 100%Nested mappings are not allowed in compact mappings at line 2, column 14: description: Plans a piece as a sequence of Phantra scenes before any is writte… ^
1 inferred permission indicators
network access — 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
11/2/2026, 7:26:52 PM
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.
Version 1.0.0 introduces a workflow for planning and producing multi-scene Phantra storyboards. - Plan and approve a beat list before writing scenes. - Keep scenes in one project, with a consistent look and shared reference photos. - Write and save each scene separately; create alternates as fresh scenes. - Quote and render scenes one at a time, only after the person approves the shown price. - Assemble finished scene clips into a new library item.
Your privacy, your choice
Optional analytics and advertising services stay off unless you accept. Your choice is saved only on this device. Privacy Policy · Cookie Policy。
Global Privacy Control is enabled, so optional services will remain off.