mrchantey/skills/release
skills/release/SKILL.md
Prepare the speficied crates for release, one by one. For each crate follow the below procedure. **Do not actually release the crate.** ## 1. Documentation Gain an understanding of the intended usage of the crate. Do not comb through every single source file, just check the high level types and ensure they are well documented. Ensure the `README.md` is up to date and of high quality. The `lib.rs` should include the readme as crate level docs. ## 2. Testing Run checks and tests for the crate
$ install --global
skillsauthnpx skillsauth add mrchantey/beet skills/releaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 2, 2026, 6:42 AM105.3s1 file scanned
SKILL.md
Prepare the speficied crates for release, one by one. For each crate follow the below procedure.
Do not actually release the crate.
1. Documentation
Gain an understanding of the intended usage of the crate. Do not comb through every single source file, just check the high level types and ensure they are well documented. Ensure the README.md is up to date and of high quality. The lib.rs should include the readme as crate level docs.
2. Testing
Run checks and tests for the crate with all features, both native and wasm:
cargo check -p CRATE_NAME --all-features
cargo check -p CRATE_NAME --all-features --target=wasm32-unknown-unknown
timeout 1m cargo test -p CRATE_NAME --all-features | tail 30
timeout 1m cargo test -p CRATE_NAME --all-features --target=wasm32-unknown-unknown --lib | tail 30
3. Examples
All examples are located in examples/CRATE_NAME, not crates/CRATE_NAME/examples. Ensure an example exists for each intended usage of the crate. If one is missing create it.
For each example:
- check the implementation is up to date.
- ensure the example is well and consistenly documented, include the command to run the example, specifying features.
- run the example to verify it works, ie:
timeout 1m cargo run --example server --features=http_server | tail 30(then simultaneously run acurl, waiting for it to be live)
Related Skills
mrchantey/skills/documentation
development
VerifiedTrustedCommunity
## Task We will now do a comprehensive code quality pass for the core crates of this project. This task has the primary goal of improving public apis: 1. Reduce usage of `pub`: prefer `pub(super)`, `pub(crate)` etc wherever it makes sense, this includes at the module level and for struct fields. 2. Public Docs: ensure all public apis are well documented according to RFC 1574, except where it would be overly verbose. While we are passing through source files we should also consider two seconda
123SKILL.mdUpdated May 2, 2026
steipete/skill-creator
testing
VerifiedTrustedCommunity
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".
356,423SKILL.mdUpdated Apr 13, 2026
steipete/healthcheck
testing
VerifiedTrustedCommunity
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).
356,423SKILL.mdUpdated Apr 13, 2026
openclaw/skill-creator
testing
VerifiedTrustedCommunity
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".
353,662SKILL.mdUpdated Apr 10, 2026