pqc-evaluator
Post-quantum cryptography evaluation skill for quantum-safe migration
npx skills add a5c-ai/babysitter --skill pqc-evaluator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PQC Evaluator ## Purpose Provides expert guidance on evaluating post-quantum cryptographic algorithms and planning quantum-safe migration strategies. ## Capabilities - NIST PQC standard implementation checks - Lattice-based algorithm analysis - Code-based cryptography evaluation - Hash-based signature verification - Hybrid classical-PQC schemes - Migration impact assessment - Performance benchmarking - Key size analysis ## Usage Guidelines 1. **Inventory Assessment**: Catalog current cryptographic usage 2. **Algorithm Selection**: Choose appropriate PQC algorithms for use cases 3. **Implementation Review**: Verify correct implementation of PQC schemes 4. **Performance Testing**: Benchmark PQC against classical algorithms 5. **Migration Planning**: Develop phased migration strategy ## Tools/Libraries - liboqs - PQClean - OpenSSL (with PQC support) - Bouncy Castle - SUPERCOP
- Purpose
- Capabilities
- Usage Guidelines
- Tools/Libraries
What does the pqc-evaluator skill do?
Post-quantum cryptography evaluation skill for quantum-safe migration
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill pqc-evaluator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
