GitHub
styx
Styx configuration language syntax and schema reference. Use when writing or editing .styx files, creating schemas, or debugging syntax errors. Covers syntax (scalars, objects, sequences, tags, heredocs), schem...
☆ 37View skill
bearcove AI Skills
GitHub ↗Browse published AI skills maintained by bearcove. Compare skill descriptions and follow each source repository for setup instructions.
Author statistics
Indexed skills
9Repository stars across indexed skills
236Repository forks
14Average repository stars per indexed skill
26Repository stars may repeat across skills from the same repository.
Popular categories
Recent indexing activity
Browse skills
GitHub
styx
Styx configuration language syntax and schema reference. Use when writing or editing .styx files, creating schemas, or debugging syntax errors. Covers syntax (scalars, objects, sequences, tags, heredocs), schem...
☆ 31View skill
GitHub
debugging
Debugging conventions for pikru. Use when adding debug traces or investigating issues. Important rule - leave debug traces in place.
☆ 24View skill
GitHub
git-commands
Git command conventions for pikru. Use when running any git commands to avoid blocking on interactive pager.
☆ 24View skill
GitHub
testing
Testing conventions for pikru. Use when running tests to avoid timeouts. DO NOT run the full test suite.
☆ 24View skill
GitHub
codebase-layout
Codebase organization for pikru. Use when you need to find where specific functionality lives.
☆ 24View skill
GitHub
idiomatic-rust
Idiomatic Rust patterns for pikru C port. Use when writing or reviewing Rust code ported from C. Don't write C in Rust - the goal is correct behavior, not line-by-line translation.
☆ 24View skill
GitHub
code-annotations
Code annotation requirements for pikru. Use when writing or porting Rust functions from C code. All ported functions must have cref comments.
☆ 24View skill
GitHub
subtest-isolation
Create minimal subtests to isolate and fix complex bugs. Use when a test fails and the issue is buried in complexity.
☆ 24View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.