athola/math-review
plugins/pensive/skills/math-review/SKILL.md
Verifies math-heavy code for algorithmic correctness and numerical stability. Use when reviewing scientific algorithms, ML models, or numerical code.
$ install --global
skillsauthnpx skillsauth add athola/claude-night-market math-reviewInstall 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: Jun 8, 2026, 3:34 AM135.8s5 files scanned
SKILL.md
- name:
- math-review
- description:
- Verifies math-heavy code for algorithmic correctness and numerical stability. Use when reviewing scientific algorithms, ML models, or numerical code.
- alwaysApply:
- false
- category:
- specialized
- tools:
- []
- complexity:
- advanced
- model_hint:
- deep
- estimated_tokens:
- 200
- progressive_loading:
- true
- - pensive:
- shared
- - imbue:
- structured-output
Table of Contents
- Quick Start
- When to Use
- Required TodoWrite Items
- Core Workflow
- 1. Context Sync
- 2. Requirements Mapping
- 3. Derivation Verification
- 4. Stability Assessment
- 5. Proof of Work
- Progressive Loading
- Essential Checklist
- Output Format
- Summary
- Context
- Requirements Analysis
- Derivation Review
- Stability Analysis
- Issues
- Recommendation
- Exit Criteria
Mathematical Algorithm Review
Intensive analysis ensuring numerical stability and alignment with standards.
Quick Start
/math-review
Verification: Run the command with --help flag to verify availability.
When To Use
- Changes to mathematical models or algorithms
- Statistical routines or probabilistic logic
- Numerical integration or optimization
- Scientific computing code
- ML/AI model implementations
- Safety-critical calculations
When NOT To Use
- General algorithm review - use architecture-review
- Performance optimization - use parseltongue:python-performance
- General algorithm review - use architecture-review
- Performance optimization - use parseltongue:python-performance
Required TodoWrite Items
math-review:context-syncedmath-review:requirements-mappedmath-review:derivations-verifiedmath-review:stability-assessedmath-review:evidence-loggedmath-review:findings-verified
Core Workflow
1. Context Sync
pwd && git status -sb && git diff --stat origin/main..HEAD
Verification: Run git status to confirm working tree state.
Enumerate math-heavy files (source, tests, docs, notebooks). Classify risk: safety-critical, financial, ML fairness.
2. Requirements Mapping
Translate requirements → mathematical invariants. Document pre/post conditions, conservation laws, bounds. Load: modules/requirements-mapping.md
3. Derivation Verification
Re-derive formulas using CAS. Challenge approximations. Cite authoritative standards (NASA-STD-7009, ASME VVUQ). Load: modules/derivation-verification.md
4. Stability Assessment
Evaluate conditioning, precision, scaling, randomness. Compare complexity. Quantify uncertainty. Load: modules/numerical-stability.md
5. Proof of Work
pytest tests/math/ --benchmark
jupyter nbconvert --execute derivation.ipynb
Verification: Run pytest -v tests/math/ to verify.
Log deviations, recommend: Approve / Approve with actions / Block. Load: modules/testing-strategies.md
6. Verify Findings Are Grounded (math-review:findings-verified)
Every issue must cite a real location and a verbatim anchor. Write
findings to .review/findings.json and confirm each citation resolves:
python plugins/imbue/scripts/citation_verifier.py \
--findings .review/findings.json --repo-root .
Drop or label UNVERIFIED any finding the verifier fails (exit 1);
only verified findings enter the report. See Skill(imbue:review-core)
Step 5 for the protocol and Skill(imbue:structured-output) for the
finding schema.
Progressive Loading
Default (200 tokens): Core workflow, checklists +Requirements (+300 tokens): Invariants, pre/post conditions, coverage analysis +Derivation (+350 tokens): CAS verification, standards, citations +Stability (+400 tokens): Numerical properties, precision, complexity +Testing (+350 tokens): Edge cases, benchmarks, reproducibility
Total with all modules: ~1600 tokens
Essential Checklist
Correctness: Formulas match spec | Edge cases handled | Units consistent | Domain enforced Stability: Condition number OK | Precision sufficient | No cancellation | Overflow prevented Verification: Derivations documented | References cited | Tests cover invariants | Benchmarks reproducible Documentation: Assumptions stated | Limitations documented | Error bounds specified | References linked
Output Format
## Summary
[Brief findings]
## Context
Files | Risk classification | Standards
## Requirements Analysis
| Invariant | Verified | Evidence |
## Derivation Review
[Status and conflicts]
## Stability Analysis
Condition number | Precision | Risks
## Issues
[M1] [Title]
- Location: file.py:123
- Anchor: `verbatim source text at line 123`
- Issue: [what is wrong] | Fix: [remediation] | Evidence: [E1]
## Recommendation
Approve / Approve with actions / Block
Every issue's Anchor is the exact source text at Location; it is what
citation_verifier.py re-reads to prove the finding is real.
Verification: Run the command with --help flag to verify availability.
Exit Criteria
- Context synced, requirements mapped, derivations verified, stability assessed, evidence logged with citations
- Every reported issue carries a
Location+ verbatimAnchor, andcitation_verifier.pyconfirmed all citations (exit0) or unverified issues were dropped or labeledUNVERIFIED
Related Skills
athola/ideate
research
VerifiedTrustedCommunity
Generate diverse solution candidates with category-spanning ideation methods and rotation. Use when stuck on a design or fighting repetitive LLM output.
304SKILL.mdUpdated Jun 8, 2026
athola/plugins/sanctum/skills/validate-pr
tools
VerifiedTrustedCommunity
--- name: validate-pr description: Use when you need a diff-derived test plan for a PR: reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions. alwaysApply: false category: validation tags: - pr - validation - test-plan - diff - revert-test - evidence tools: [] usage_patterns: - diff-derived-test-plan - revert-test-quality-check - evidence-capture complexity: intermediate model_hint: standard estimated_tokens: 650
304SKILL.mdUpdated Jun 8, 2026
athola/decision-journal
development
VerifiedTrustedCommunity
Contract for the project decision journal (tradeoffs and lessons-learned logs). Use when recording a decision, tradeoff, or lesson, or building a consumer hook.
304SKILL.mdUpdated Jun 8, 2026
athola/graduated-implementation
development
VerifiedTrustedCommunity
Ramps implementation ambition a notch only after the prior increment is understood. Use when building a feature you must understand, not just ship.
304SKILL.mdUpdated Jun 8, 2026