testing-assistant
Skill206 starsChanged 8 months agoMITView on GitHub
Manages testing lifecycle including unit tests, integration tests, validation, and quality assurance.
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- rudrathegreat/Astronomy-AI-Toolkittheir own version, first seen Aug 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- rudrathegreat/Astronomy-AI-Toolkit★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- bigquery-patent-searchSkill
- development-assistantSkill
- epc-searchSkill
- epo-patent-analyzerSkill
- epo-patent-searchSkill
- index-managerSkill
- mpep-searchSkill
- patent-application-creatorSkill
- patent-claims-analyzerSkill
- patent-diagram-generatorSkill
- patent-reviewerSkill
- patent-searchSkill
- pct-applicationSkill
- prior-art-searchSkill
- setup-assistantSkill
- troubleshooting-assistantSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
FOR CLAUDE: Test scripts in scripts/ directory.
- Distinctive: line 12
Run from project root
- Distinctive: line 14
Only run diagnostics if tests fail
- Distinctive: line 54
Test MCP tools through Claude Code interface.
- Distinctive: line 146
Test after every change
- Distinctive: line 148
Test pyramid (more unit, fewer E2E)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Testing Assistant Skill
Expert system for testing and validating the Claude Patent Creator.
FOR CLAUDE: Test scripts in scripts/ directory.
- Go directly to running appropriate test
- Run from project root
- Tests require active venv
- Only run diagnostics if tests fail
When to Use
Running test suites, validating new features, testing after changes, debugging failures, creating tests, setting up CI/CD, performance testing, E2E validation, regression testing.
Testing Pyramid
/\
/ \ E2E (Manual + Automated)
/----\
/ API \ Integration Tests
/--------\
/ Unit \ Unit Tests
/----------\Strategy: More unit tests (fast, isolated), fewer integration (moderate), minimal E2E (slow).
Test Suite Overview
scripts/
+-- test_install.py # Complete installation validation
+-- test_gpu.py # GPU detection and CUDA
+-- test_bigquery.py # BigQuery connection
+-- test_analyzers.py # Claims, spec, formalities
+-- test_embedding_speed.py # Performance benchmarks
+-- test_checkpoint.py # Index checkpoint systemQuick Test:
python scripts/test_install.pyManual Testing via Claude
Test MCP tools through Claude Code interface.
Quick Test Examples
1. MPEP Search: "Search MPEP for claim definiteness requirements"
2. Patent Search: "Search for patents about neural networks filed in 2024"
3. Claims Review: "Review these claims: [paste test claims]"
4. Full Review: "/full-review" (with test application)
5. Diagrams: "Create a flowchart for this process: [describe]"Validation Checklist
[OK] MPEP search returns relevant results
[OK] BigQuery search finds patents
[OK] Claims analyzer identifies issues
[OK] Specification analyzer checks support
[OK] Formalities checker validates format
[OK] Diagrams generate successfully
[OK] Full review workflow completes
[OK] All MCP tools accessible
[OK] Error messages clear and helpful
[OK] Performance acceptable (<2s most ops)Creating New Tests
Quick Start
# Unit test template
def test_basic_functionality():
from mcp_server.your_module import YourClass
instance = YourClass()
result = instance.method("test input")
assert result is not None
print("[OK] test_basic_functionality passed")Test Categories:
- Basic functionality
- Edge cases
- Performance
- Error handling
Performance Testing
Quick Benchmark
from mcp_server.mpep_search import MPEPIndex
import time
index = MPEPIndex()
index.build_index()
index.search("test", top_k=5) # Warm up
start = time.time()
result = index.search("claim definiteness", top_k=5)
duration = time.time() - start
print(f"Search took: {duration:.3f}s")Performance Thresholds
| Operation | Threshold | Notes |
| MPEP search (first) | <3s | Model loading |
| MPEP search (subsequent) | <500ms | Cached models |
| BigQuery search | <2s | Network dependent |
| Claims analysis | <3s | 20 claims |
| Spec analysis | <10s | 10 pages |
| Diagram generation | <1s | SVG output |
Troubleshooting Test Failures
| Problem | Solution |
| Import errors | Activate venv, pip install -r requirements.txt |
| GPU tests fail | Check nvidia-smi, reinstall PyTorch, or skip |
| BigQuery fails | Re-auth: gcloud auth application-default login |
| Index not found | Rebuild: patent-creator rebuild-index |
| Too slow | Check GPU usage, first run slower, check system load |
Best Practices
- Test after every change
- Automated testing
- Test pyramid (more unit, fewer E2E)
- Fast tests (<5 min suite)
- Isolated tests (no dependencies)
- Clear assertions
- Document tests
- Version control tests
- Regular execution (weekly)
- Monitor performance
Quick Reference
Run All Tests
python scripts/test_install.py
python scripts/test_gpu.py
python scripts/test_bigquery.py
python scripts/test_analyzers.py
python scripts/test_embedding_speed.pyRegression Test
python scripts/test_install.py || exit 1
python scripts/test_bigquery.py || exit 1
python scripts/test_analyzers.py || exit 1
echo "[OK] All regression tests passed!"Manual Checklist
□ Ask Claude to search MPEP
□ Ask Claude to search patents
□ Ask Claude to review claims
□ Run /full-review command
□ Generate a diagram
□ Verify all tools work
□ Check performance (<2s)Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

