giladresisi/prime-tools
skills/prime-tools/SKILL.md
Use when about to build or modify agent tools and needing to load tool docstring patterns and best practices first
$ install --global
skillsauthnpx skillsauth add giladresisi/ai-dev-env prime-toolsInstall 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: May 3, 2026, 6:27 AM64.9s1 file scanned
SKILL.md
- name:
- prime-tools
- description:
- Use when about to build or modify agent tools and needing to load tool docstring patterns and best practices first
Prime for Tool Development
Load tool development patterns from Module 3 to prepare for building agent tools.
Context
You are about to work on building or modifying agent tools that will be used by Pydantic AI agents. Load the comprehensive patterns and best practices we established in Module 3 for writing agent-optimized tool docstrings.
Read
Read the tool docstring patterns: @.agents/reference/adding_tools_guide.md
Process
Understand and internalize:
- Core Philosophy - How agent tool docstrings differ from standard docstrings
- 7 Required Elements - One-line summary, "Use this when", "Do NOT use", Args with guidance, Returns, Performance Notes, Examples
- Agent Perspective - Writing for LLM comprehension and tool selection
- Token Efficiency - Documenting token costs and optimization strategies
- Anti-patterns - Common mistakes that confuse agents
- Template Structure - The exact format to follow
Pay special attention to:
- "Use this when" (affirmative guidance for tool selection)
- "Do NOT use" (negative guidance to prevent tool confusion)
- Performance Notes (token costs, execution time, limits)
- Realistic examples (not "foo", "bar", "test.md")
Report Back
Provide a concise summary with:
Key Principles (5 bullets max)
- [What are the core principles you understood?]
Critical Distinctions
- [What makes agent tool docstrings different from standard docstrings?]
- [Why does "Do NOT use" matter?]
Template Internalized
- [Confirm you understand the structure you'll follow]
Ready to Apply
- [One sentence confirming you're ready to write agent-optimized tool docstrings]
Keep it scannable - I want to verify understanding in 30 seconds.
Related Skills
giladresisi/new-co-trader-worktree
testing
VerifiedTrustedCommunity
Creates a new git worktree in the auto-co-trader project for any purpose — optimization, regression, backtesting, brainstorming, etc. Use this skill when the user wants to CREATE or SET UP a new worktree — phrases like "prepare a new worktree", "set up a worktree", "create a new worktree for <purpose>", "prep a new worktree", "new worktree for autoresearch", "prepare optimization from [strategy]", or "create a worktree using [strategy]". Do NOT use this skill when the user is already in a worktree and wants to start/run/begin a task — that is handled by the relevant program file in the worktree session.
2SKILL.mdUpdated May 9, 2026
giladresisi/validate
development
VerifiedTrustedCommunity
Use when running comprehensive project validation including tests, type checking, linting, API connectivity checks, and server startup verification
2SKILL.mdUpdated May 3, 2026
giladresisi/system-review
research
VerifiedTrustedCommunity
Use when performing a meta-level analysis of plan adherence after implementation to identify process improvements and suggest CLAUDE.md updates
2SKILL.mdUpdated May 3, 2026
giladresisi/github_bug_fix:rca
documentation
VerifiedTrustedCommunity
Use when investigating a GitHub issue to identify root cause, assess impact, and create a fix strategy document
2SKILL.mdUpdated May 3, 2026