Index of every page on this site: llms.txt
All skills
jame581 avatar

/authoring-godot-prompter-skills

@426e8ab
by Jan Mesarčjame581/godotprompter979 stars
63
Run it yourself

Use when writing or editing a SKILL.md, a skill's references/*.md, or an agent definition in this repo — required frontmatter, section ordering, the GDScript-then-C# example convention, and C# parity exemptions.

Use this Skill: https://skilld.dev/gh/jame581/godotprompter/authoring-godot-prompter-skills

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈62 tokens for metadata: the name and description. ≈600 when used: this file.

Description uses 3.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈245 characters, or 3.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Authoring GodotPrompter skills and agents

File format templates for this repo. See the root CLAUDE.md for the conventions and size budget that govern the content itself.

SKILL.md format

Every skill must start with YAML frontmatter:

---
name: skill-name
description: Use when [trigger] — [brief scope]
---

Followed by:

  1. Title and intro
  2. Related skills line: > **Related skills:** **skill-a** for X, **skill-b** for Y.
  3. Numbered sections with patterns and examples
  4. GDScript first, then C# equivalent (use gdscript and csharp language tags)
  5. Implementation checklist at the end

C# parity

The validator also checks C# parity inside references/*.md (csharp-parity-*-reference), so Pattern X moves stay enforced. Files that section by language (## C#, ## Dash (C#), ### … — C#) are checked file-level instead of per-section; a heading that merely mentions C# in prose is not a partition.

When a section genuinely cannot have a C# counterpart, mark that section — never the whole skill:

<!-- csharp-parity: n/a — C# is statically typed; there is no untyped alternative to contrast -->

It works in both SKILL.md and references/*.md. The reason is mandatory; omitting it is an error (checked on every marker, not only on sections missing C#), because an exemption that cannot say why is indistinguishable from an example nobody wrote. A reason may contain < and >, and a marker inside a fenced block is ignored, so a file can document the marker without exempting itself.

Do not reach for the two blunter tools instead: adding the skill to GDSCRIPT_ONLY_BY_DESIGN exempts every section in it, and renaming a heading to "… (GDScript)" trips the language-partition check and silently downgrades the entire file to a file-level check. Both hide real gaps in neighbouring sections.

A fenced ```gdscript block containing only comments is not a code example — it is prose in a fence, and it will be flagged as an unpaired GDScript block. Write it as prose or a bullet list.

Agent format

Agent definitions in agents/<name>.md use YAML frontmatter:

---
name: agent-name
description: |
  When to use, with <example> blocks.
model: inherit
---

Before you finish

Run node scripts/validate-skills.mjs — it enforces frontmatter, cross-references, and the 16 KB size budget.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides authoring guidelines for GodotPrompter skills and agents. It is a documentation-oriented skill with no malicious behaviors detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 426e8ab. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated 2 months ago

README badge

README badge for jame581/godotprompter/authoring-godot-prompter-skills