missing-description
From the author
Static analysis for AI agent configs, tool descriptions, and system prompts — catches vague tool descriptions, missing stop conditions, and schema gaps before they reach runtime. Zero-LLM, deterministic checks, built for CI.
Install
npx skills add hermes-labs-ai/lintlang --skill missing-description -a claude-code
Installs to .claude/skills/missing-description/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 84
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- lintlanghermes-labs-ai/lintlangUse when writing or reviewing AI agent configs, system prompts, or tool definitions (JSON/YAML/Python) and you need to catch ambiguous tool descriptions, missing stop conditions, schema/description mismatches, or embedded prompts before they reach runtime. Deterministic static analysis, no LLM or network calls.Writing★ 143
- lintlang-audithermes-labs-ai/lintlangAudit a named AI agent config, system prompt, tool-definition or instruction file (YAML, JSON, Markdown, text, or Python) with the released LintLang CLI, on request. Use when the user asks to audit, lint, scan or review such a file for ambiguous tool descriptions, missing stop conditions, schema/description mismatches, or prompts embedded in Python, and names the file. Deterministic offline static analysis, no model call and no network call. Do not use for general code review, for prose documentation, or when no file has been named.Writing★ 143
- static-bug-detectorArabelaTso/Skills-4-SEAnalyze source code statically to detect potential functional bugs including null dereferences, incorrect condition checks, unreachable code, inconsistent state updates, logic errors, resource leaks, and type mismatches. Report suspicious code locations with detailed explanations, severity levels, and confidence assessments. Use when reviewing code for bugs, performing code audits, or when the user asks to find bugs, detect issues, analyze code for problems, or perform static analysis.Engineering★ 258
- debuggingnotque/vexjoy-agentDebugging: guided diagnosis of application bugs, and post-mortem of failed agent sessions.Engineering★ 443
- agent-runtime-validationzero-lab-ai/skillsPlans and evaluates bounded runtime tests of AI agents, tools, memory, hooks, approvals, and scope enforcement. Use when static review is complete and an authorized assessment must determine how the deployed agent actually behaves.Testing★ 281
- healthtw93/WazaAudits agent config, instruction drift, hooks or MCP, and AI maintainability. Use when Claude, Codex, or Pi setup looks wrong. Not for application bugs or PR review.Engineering★ 7.4K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in