Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →github/developer-code-organization
Code organization patterns, file structure guidelines, WASM build variants, and string processing conventions for gh-aw Go code.
Passed 23 of 23 test cases with the skill, and 10 of 23 without it.
and 15 more in the full report
13 fixed10 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
When generating user agent strings or internal execution identifiers from user input that might turn out completely empty after cleaning, which function should be used?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends SanitizeIdentifier when generating user agent strings with fallback defaults. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this reference for gh-aw code organization patterns, file structure guidelines, WASM build-variant stubs, and string sanitization/normalization conventions.
The codebase follows clear patterns for organizing code by functionality rather than type. This section provides guidance on maintaining code quality and structure.
Organize code into focused files of 100-500 lines rather than creating large monolithic files.
Example:
create_issue.go (160 lines)
create_pull_request.go (238 lines)
create_discussion.go (118 lines)
Recommended approach:
create_issue.go # Issue creation logic
create_issue_test.go # Issue creation tests
add_comment.go # Comment addition logic
add_comment_test.go # Comment tests
test cases passed, vs 10 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.