Strictly follow the naming conventions in rules/named.md
/go-naming
@8ec6eacGo naming conventions and best practices. Use this skill when working with Go code and need to name packages, files, directories, structs, interfaces, functions, variables, or constants. Provides comprehensive naming guidelines following Go community standards.
Use this Skill: https://skilld.dev/gh/infiniflow/ragflow/go-naming Nothing lands on disk. Nothing to clean up.
Edit a local copy. It keeps the author and licence.
≈68 tokens for metadata: the name and description. ≈20 when used: this file.
Description uses 3.4% 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 ≈273 characters, or 3.4%.
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.
Source: SKILL.md on GitHub
Skill behaviors
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.
Third-party checks
No alerts1mo3 checks · Risk SAFE
- Gen Agent Trust Hub1mo
This skill provides naming convention guidelines for the Go programming language by referencing a local rules file. It does not contain any executable code, scripts, or network requests.
- Socket1mo
No alerts
- Snyk1mo
Risk: LOW · No issues
Provenance
Signed by skilld at 8ec6eac. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.
Last checked against GitHub yesterday.