defold-proto-file-editing

To validate Defold protobuf files, this Skill checks each root for a SKILL.md with mandatory YAML frontmatter, then extracts tagline, description, keywords, dependencies, and components to enable consistent repository discovery.

Automating protobuf file editing involves identifying valid Skill Units, assembling structured metadata, and evaluating scripts and frontmatter for security risks to return a toxic_reason if malicious patterns or prompt-injection risks are found.

Yes, you can use this tool with Defold projects with no dependencies, as it independently identifies valid Skill Units by validating required YAML frontmatter fields and optional resources like scripts and references.

You identify valid Skill Units in a Defold repository by ensuring each root contains a SKILL.md file with mandatory YAML frontmatter defining both name and description, which enables structured metadata generation.

A toxic_reason warning during Defold protobuf metadata extraction indicates the Skill evaluated your scripts and frontmatter and detected malicious patterns or prompt-injection risks within the validated content.

Yes, you need a SKILL.md file to automate Defold protobuf metadata discovery because the Skill requires mandatory YAML frontmatter defining name and description at the root to identify and validate each unit.