How do I install the Ecc Pairing Auditor skill?

Run npx skillmds@latest add yue-zhou1/ecc-pairing-auditor-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ecc Pairing Auditor safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ecc Pairing Auditor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ecc Pairing Auditor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ecc Pairing Auditor?

Yue-Zhou1 (@yue-zhou1) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ecc Pairing Auditor by yue-zhou1 — Agent Skill

Name: Ecc Pairing Auditor
Author: Yue-Zhou1

Ecc Pairing Auditor

Audit elliptic-curve, pairing, and BLS signature code for point-validation, subgroup, serialization, DST, and pairing-equation failures. Use when reviewing deserialization, `hash_to_curve`, aggregate verification, or batch pairing logic.

Yue-Zhou1 Updated Sep 17, 2026

File contents

ecc-pairing-auditor

Domain auditor for elliptic-curve arithmetic, point parsing, and pairing-based verification.

When to Use

Auditing BLS signatures, aggregate signatures, pairings, or curve arithmetic code
Reviewing deserialization and external-point handling
Checking hash_to_curve, DST separation, or G1/G2 role consistency
Reviewing batched pairing verification or optimized multi-pairing paths

When NOT to Use

Building initial protocol context for a new codebase
Reviewing ZK circuit constraints or transcript construction
Declaring a suspected curve bug confirmed without verification

Core Review Areas

Point validity, subgroup membership, and encoding
Scalar/cofactor/coordinate correctness
Pairing equation and group-role consistency
Hash-to-curve, DST, and batch verification behavior

Workflow

Phase 1: Point and scalar intake

Read references/ecc-checklist.md
Execute workflows/deserialization-review.md
Treat every external point, scalar, and compressed encoding as hostile until validated

Phase 2: Pairing and aggregation review

Read references/pairing-checklist.md
Execute workflows/pairing-review.md
Check rogue-key resistance, pairing direction, final exponentiation, and batching semantics

Phase 3: Pattern hunt

Read references/finding-patterns.md
Prioritize subgroup bugs, non-canonical encodings, batch masking, and optimized-backend divergence

Phase 4: Handoff

Send surviving findings to crypto-fp-check
Use zkbugs-index only after the finding survives verification

Output Contract

Produce a curve/pairing handoff that includes:

The points, groups, encodings, and pairing equations involved
The exact validation or batching gap under review
Whether the issue is parser-level, arithmetic, DST, or aggregation related
The next verification or reporting route

Reference Index

references/ecc-checklist.md
references/pairing-checklist.md
references/finding-patterns.md
workflows/deserialization-review.md
workflows/pairing-review.md

---name: ecc-pairing-auditor-2description: Audit elliptic-curve, pairing, and BLS signature code for point-validation, subgroup, serialization, DST, and pairing-equation failures. Use when reviewing deserialization, `hash_to_curve`, aggregate verification, or batch pairing logic.---# ecc-pairing-auditorDomain auditor for elliptic-curve arithmetic, point parsing, and pairing-basedverification.## When to Use- Auditing BLS signatures, aggregate signatures, pairings, or curve arithmetic code- Reviewing deserialization and external-point handling- Checking `hash_to_curve`, DST separation, or G1/G2 role consistency- Reviewing batched pairing verification or optimized multi-pairing paths## When NOT to Use- Building initial protocol context for a new codebase- Reviewing ZK circuit constraints or transcript construction- Declaring a suspected curve bug confirmed without verification## Core Review Areas1. Point validity, subgroup membership, and encoding2. Scalar/cofactor/coordinate correctness3. Pairing equation and group-role consistency4. Hash-to-curve, DST, and batch verification behavior## Workflow### Phase 1: Point and scalar intake- Read `references/ecc-checklist.md`- Execute `workflows/deserialization-review.md`- Treat every external point, scalar, and compressed encoding as hostile until validated### Phase 2: Pairing and aggregation review- Read `references/pairing-checklist.md`- Execute `workflows/pairing-review.md`- Check rogue-key resistance, pairing direction, final exponentiation, and batching semantics### Phase 3: Pattern hunt- Read `references/finding-patterns.md`- Prioritize subgroup bugs, non-canonical encodings, batch masking, and optimized-backend divergence### Phase 4: Handoff- Send surviving findings to `crypto-fp-check`- Use `zkbugs-index` only after the finding survives verification## Output ContractProduce a curve/pairing handoff that includes:- The points, groups, encodings, and pairing equations involved- The exact validation or batching gap under review- Whether the issue is parser-level, arithmetic, DST, or aggregation related- The next verification or reporting route## Reference Index- [references/ecc-checklist.md](references/ecc-checklist.md)- [references/pairing-checklist.md](references/pairing-checklist.md)- [references/finding-patterns.md](references/finding-patterns.md)- [workflows/deserialization-review.md](workflows/deserialization-review.md)- [workflows/pairing-review.md](workflows/pairing-review.md)

Frequently asked questions