skills.rest
cyanheads
cyanheadsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tool-defs-analysis

Audit tool, resource, and prompt definitions for consistency and leaks.

654|102|Updated Jan 23, 2025
Search Tags:#quality assurance#security#validation#audit#llm#definition#tool
One-click install
npx skills add https://github.com/cyanheads/obsidian-mcp-server --skill tool-defs-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tool-defs-analysis
Source: https://github.com/cyanheads/obsidian-mcp-server/tree/main/skills/tool-defs-analysis
Command: npx skills add https://github.com/cyanheads/obsidian-mcp-server --skill tool-defs-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It helps identify inconsistencies, unclear descriptions, and potential security issues within tool, resource, and prompt definitions, ensuring high-quality API interfaces for LLMs.

Core Features & Use Cases

  • Comprehensive audits of definition files to detect voice, internal leaks, and other issues.
  • Detailed report generation with file:line citations to assist maintainers in fixing issues.
  • Use Case: After updating or refactoring tool definitions, run this Skill to verify adherence to best practices and identify potential risks before deployment.

Quick Start

Run the analysis on all definition files in the project directory to generate a safety and quality report.

Frequently Asked Questions about tool-defs-analysis

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

FAQPage Schema
How do I audit LLM tool definitions for security and clarity issues?▼

Pre-release validation for tool definitions detects internal leaks, audience leaks, and sparse data before deployment. It ensures API interface safety and clarity by verifying defaults, recovery information, and cross-references, preventing potential security risks and inconsistencies.

How do I validate tool and resource definitions before deployment?▼

Use this analysis after updating or refactoring tool definitions to verify adherence to best practices. It reviews prompt definitions to identify potential risks, ensuring your tool interfaces remain safe and clear before deployment.

What is the best way to check tool definitions for internal leaks and voice consistency?▼

This audit checks tool and prompt definitions for sparse data and missing examples. It reviews structure and output clarity to ensure your definitions are complete, clear, and safe for LLM consumption.

Does this tool definition analysis provide specific file and line citations for issues found?▼

Limitations include relying on the quality of the definition files present in the project directory. The analysis identifies issues like sparse data and audience leaks but requires maintainers to manually apply the recommended fixes before deployment.

Related Skills

Explore More Software Engineering Skills→
wangke19wangke19
1

session-init

Resume coding sessions from .ai-session/STATE.md checkpoints or start fresh.

Community
Advanced
brandonavantbrandonavant
2

cross-reference-check

Scan Markdown files to detect broken internal links and missing chapter entries.

Community
Advanced
open-haxopen-hax
6

opencode-tool-authoring

Define and validate OpenCode tool schemas with YAML frontmatter.

Official
Intermediate
CENKSSSCENKSSS

pentest-validation

Validate SAST and DAST vulnerability exploitability through a 4-phase pipeline.

Community
Advanced