yaml@1.0.2
CAUTION· static onlyPublisher claims: "Writes, debugs, and validates YAML that parses the same in every language and tool. Use when a file will not parse, when a value silently turns into a boolean, number, date or null (`no`, `on`, `1.0`, `0644`, `22:22`), when tabs, indentation, or a colon inside a string breaks a document, when a block scalar mangles a script or a PEM key, when anchors, aliases or `<<` merge keys do not survive a tool, when duplicate keys pick the wrong winner, when the same file loads in one parser and fails in another, when YAML has to be edited or generated in code without losing comments or key order, when untrusted YAML could execute code, or when writing Kubernetes, Helm, GitHub Actions, GitLab CI, Ansible, Compose, CloudFormation, OpenAPI or Home Assistant files. Covers yamllint, schema validation, yq, and semantic diffs. Not for JSON (`json`), TOML (`toml`), XML (`xml`), or Ansible playbook semantics (`ansible`)." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-10 and scored it 65/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; References a credential file in the home directory. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
…-tls`, `1password:Work/Cluster/kubeconfig`, `sops:secrets/prod.enc.yaml`, `file:~/.kube/config`. A pasted PEM key inside a `|` block is the single most common way a se…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.… with a message about types. **After diagnosing a non-obvious parse failure**, write one row to `## Gotchas Hit` in `~/Clawic/data/yaml/memory.md`: the message, the real cause, the file, and the fix (`memory-template.md`). Er…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.… quirk is diagnosed or a tool-specific file becomes part of the user's setup**, add or update its row in `## Config Files` of `~/Clawic/data/yaml/memory.md` (path, tool, spec version, validator, whether it is templated or rewritten by …Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…on, and add its `## Boxes` line in the same turn (`memory-template.md`). If the edit revealed a house style, that goes to `## Repo Style` in `memory.md`; if the user declared the style, it goes to `config.yaml`. Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…-tls`, `1password:Work/Cluster/kubeconfig`, `sops:secrets/prod.enc.yaml`, `file:~/.kube/config`. A pasted PEM key inside a `|` block is the single most common way a secret la…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…e>.md` (or its location, if it lives in the repo), add its `## Boxes` line, and update the affected rows of `## Config Files` in `~/Clawic/data/yaml/memory.md` with which validator now guards them (`memory-template.md`). If a re-validatio…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.The general defense is Rule 10: run the file through the consumer's own validator, and once through a load-and-dump diff.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…** — or after any behavior above turns out to differ on the installed version — write or update its row in `## Toolchain` of `~/Clawic/data/yaml/memory.md`: project, library, version, spec version, and the quirk that was observed (`me…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…e fails in CI instead of at runtime. **After a coercion trap actually bites**, write it to `## Gotchas Hit` in `~/Clawic/data/yaml/memory.md` — the value, the file, the parser, and the fix — and if the parser or spec ver…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…yaml/artifacts/<kebab-name>.md`, with every secret replaced by its pointer, and add its `## Boxes` line to `memory.md` in the same turn (`memory-template.md`). Deriving the right header takes two o…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…at runs **When a pipeline trap is diagnosed or a workflow layout is settled**, write it down: the trap goes as one row in `## Gotchas Hit` of `~/Clawic/data/yaml/memory.md` with the verbatim error, the workflow file gets or updates its row…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…to `~/Clawic/data/yaml/artifacts/<kebab-name>.md` with its `## Boxes` line, and update the file's row in `## Config Files` of `~/Clawic/data/yaml/memory.md` (`memory-template.md`). Never copy Secret payloads or kubeconfig material into…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
15 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim ivangdavila: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- References a credential file in the home directory≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.