defold-proto-file-editing

Identify Skill Units and generate structured metadata from SKILL.md files.

11|Updated Oct 10, 2024

Search Tags:#automation #discovery #tooling #metadata #protobuf #scripting #defold

Ready to run

npx skills add https://github.com/selimanac/defold-daabbcc3d --skill defold-proto-file-editing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: defold-proto-file-editing
Source: https://github.com/selimanac/defold-daabbcc3d/tree/main/.agents/skills/defold-proto-file-editing
Command: npx skills add https://github.com/selimanac/defold-daabbcc3d --skill defold-proto-file-editing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The Skill helps teams locate and validate Skill Units by ensuring a SKILL.md frontmatter exists at the Skill root and that it includes a name and description, enabling consistent discovery across a repository.

Core Features & Use Cases

Identify valid Skill Units by checking for a SKILL.md at the root and validating required fields.
Generate structured metadata (name, description, request, complexity, category, keywords, dependencies, components, and toxicity) for each valid Skill.
Supports optional resources (scripts/, references/) to enrich Skill metadata and usage guidance.

Quick Start

Run the discovery workflow on this repository to generate Skill metadata for each valid Skill Unit.

Frequently Asked Questions about defold-proto-file-editing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate Defold protobuf files and extract metadata for repository discovery?▼

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.

What is the best way to automate protobuf file editing and security checks in Defold?▼

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.

Can I use this metadata extraction tool with Defold projects that have no dependencies?▼

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.

How do I identify valid Skill Units in a Defold repository?▼

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.

Why does my Defold protobuf metadata extraction return a toxic_reason warning?▼

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.

Do I need a SKILL.md file to automate Defold protobuf metadata discovery?▼

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.