preen-skill-tooling

Validate skill actions against agentTool.ts and scriptTool.ts definitions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/a2f0/tearleads --skill preen-skill-tooling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preen-skill-tooling
Source: https://github.com/a2f0/tearleads/tree/main/.codex/skills/preen-skill-tooling
Command: npx skills add https://github.com/a2f0/tearleads --skill preen-skill-tooling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that the actions defined in your tool wrappers (agentTool.ts, scriptTool.ts) are correctly referenced by your skills, preventing runtime errors and identifying unused code.

Core Features & Use Cases

  • Action Validation: Verifies that all tool actions invoked by skills actually exist in the tool definitions.
  • Dead Code Detection: Identifies actions defined in tools but never used by any skill.
  • Documentation Sync: Helps maintain up-to-date documentation for tool actions.
  • Use Case: After adding a new function to agentTool.ts, run this skill to confirm all existing skills that should use it are correctly calling it, and that no old, unused functions remain.

Quick Start

Run the preen skill tooling to validate the ecosystem for consistency.

Frequently Asked Questions about preen-skill-tooling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check for undefined actions invoked by skills in TypeScript tooling?

You can check for undefined actions by validating consistency between skill definitions and tool implementations in agentTool.ts and scriptTool.ts, which identifies actions invoked by skills that lack actual definitions in the tool wrappers.

What is the best way to detect dead code in agentTool.ts and scriptTool.ts?

The best way to detect dead code in agentTool.ts and scriptTool.ts is to scan for actions defined in the tool wrappers that are never referenced or invoked by any skill, ensuring no unused functions remain after updates.

How do I keep skill documentation synced with tool action changes?

To keep skill documentation synced with tool action changes, run a consistency validation that checks for semantic parity between Claude and Codex skill documentation and verifies README freshness against the actual tool implementations.

Can I use this skill validation to prevent runtime errors from missing tool actions?

Yes, you can use skill validation to prevent runtime errors by verifying that all tool actions invoked by your skills actually exist in the definitions within agentTool.ts and scriptTool.ts before deployment.

Does skill consistency validation work with both Claude and Codex documentation?

Skill consistency validation works with both Claude and Codex documentation by checking for semantic parity between their respective skill docs and ensuring both accurately reflect the underlying tool action implementations.