skillize-any-lib — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited skillize-any-lib (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Generate a comprehensive SKILL.md for any library to teach LLMs how to use it properly. The skill analyzes the library source and its dependents to extract real usage patterns.
Use this skill when:
Follow these steps to generate a SKILL.md for any library:
Extract library name from user prompt. Patterns:
skillize the lib {name}skillize {lang} lib {name}skillize crate {name}create skill for {name}Optional: User can specify language with --lang rust|python|js|go|cpp
Query package registries to detect language and get library info:
| Language | Registry API |
|---|---|
| Rust | https://crates.io/api/v1/crates/{lib} |
| Python | https://pypi.org/pypi/{lib}/json |
| JavaScript | https://registry.npmjs.org/{lib} |
| Go | https://pkg.go.dev/{lib} |
| C/C++ | GitHub search only |
Fetch from registry:
Search GitHub for projects using this library:
| Language | Search Query |
|---|---|
| Rust | depends:{lib} in Cargo.toml |
| Python | import {lib} or from {lib} |
| JavaScript | require("{lib}") or from "{lib}" |
| Go | "{lib}" in go.mod |
| C/C++ | #include <{lib}> |
Sort results by stars (descending), take top 5-10.
Present to user:
"I found {N} popular projects on GitHub that use this library. Choose: 1. Use these GitHub projects 2. Add your own reference projects (provide URLs) 3. Use both 4. Skip - use only the library's examples/tests"
If user adds custom repos, collect the URLs.
Clone to temp directory (/tmp/skillize-{lib}/):
Extract and analyze:
| What | How |
|---|---|
| README | Find use cases, features |
| Examples | examples/ directory |
| Tests | tests/ directory |
| API usage | Find use/import/require statements |
| Configuration | Cargo.toml, package.json, etc. |
| Feature flags | [features] in Cargo.toml |
For each reference project:
Write to ~/.claude/skills/{lib}-usage/SKILL.md
Use this structure (adapt as needed):
---
name: {lib}-usage
description: {description from registry}
---
# {lib}
{one-line description}
## Quick Reference
| Need | Solution |
|------|----------|
| {common_need_1} | `{solution_1}` |
| {common_need_2} | `{solution_2}` |
## Installation
{package_manager_install_command}
## Core Types
{important_types}
## Basic Usage
{minimal_example}
## Common Usage Patterns
### Pattern 1: {name}{code}
### Pattern 2: {name}{code}
## Advanced Examples
{complex_example}
## Gotchas / Anti-patterns
- **{gotcha}**: {explanation}
## Limitations
- {limitation}
## Further Reading
- Official docs: {repo_url}
- Package registry: {pkg_url}Remove temporary cloned repositories from /tmp/skillize-{lib}/
Generated SKILL.md: ~/.claude/skills/{lib_name}-usage/SKILL.md
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.