performing-security-audits

Analyze code, infrastructure, and configurations by conducting comprehensive security audits. It leverages tools within the security-pro-pack plugin, including vulnerability scanning, compliance checking, and cryptography review. Use when assessing security or running audits. Trigger with phrases like 'security scan', 'audit', or 'vulnerability'.

Quality

50%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/packages/security-pro-pack/skills/performing-security-audits/SKILL.md

Quality

Content

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a marketing-style description of a security auditing capability rather than an actionable skill document. It contains no executable code, no specific tool invocation syntax, no concrete parameters, and no validation steps. The majority of the content is boilerplate filler (Integration, Prerequisites, Instructions, Output, Error Handling, Resources sections) that provides no useful guidance to Claude.

Suggestions

Replace abstract descriptions with concrete tool invocation examples showing exact syntax, parameters, and expected output formats (e.g., how to call `Security Auditor Expert` with specific arguments).

Remove boilerplate sections (Integration, Prerequisites, Instructions, Output, Error Handling, Resources) that contain only generic placeholder text, or replace them with specific, actionable content.

Add a concrete workflow with validation checkpoints, e.g., 'Run vulnerability scan → review findings above severity threshold → verify false positives → generate remediation report'.

Eliminate the redundant Overview section and trim the 'When to Use' and 'Best Practices' sections to a few bullet points, focusing the saved space on actual tool usage details.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with significant padding. The 'Overview' section restates the opening paragraph. Sections like 'Integration', 'Prerequisites', 'Instructions', 'Output', 'Error Handling', and 'Resources' are vague filler that add no actionable information. The skill explains concepts Claude already knows (what a security audit is, what OWASP Top 10 is) and includes boilerplate sections with near-zero information content.	1 / 3
Actionability	No concrete code, commands, or executable guidance anywhere. Examples describe what 'the skill will' do in abstract terms rather than showing actual tool invocations, parameters, or expected outputs. Instructions like 'Invoke this skill when the trigger conditions are met' and 'Provide necessary context and parameters' are completely vague and non-actionable.	1 / 3
Workflow Clarity	The 'How It Works' section describes a generic 3-step process (select tool, execute, report) with no specifics about tool invocation syntax, parameters, or validation checkpoints. The 'Instructions' section is a 4-step generic placeholder with no real workflow detail. No validation or error recovery steps are included for what could be complex multi-step security auditing operations.	1 / 3
Progressive Disclosure	No bundle files are provided, yet the skill is a monolithic wall of text with no references to external documentation. Content that could be split (e.g., per-tool usage guides, compliance framework details) is neither inline with useful detail nor referenced externally. Multiple sections contain placeholder-quality content that adds bulk without substance.	1 / 3
	Total	4 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly articulates specific capabilities (vulnerability scanning, compliance checking, cryptography review), provides explicit trigger guidance with natural user phrases, and occupies a distinct niche in security auditing. It uses proper third-person voice and is concise without being vague. Minor improvement could include additional file type or technology triggers, but overall it performs well across all dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Analyze code, infrastructure, and configurations', 'vulnerability scanning', 'compliance checking', and 'cryptography review'. These are concrete, distinct capabilities.	3 / 3
Completeness	Clearly answers both 'what' (analyze code/infrastructure/configurations via vulnerability scanning, compliance checking, cryptography review) and 'when' (explicit 'Use when assessing security or running audits' plus trigger phrases). Both are well-articulated.	3 / 3
Trigger Term Quality	Includes natural trigger terms users would say: 'security scan', 'audit', 'vulnerability', plus contextual terms like 'compliance checking', 'cryptography review', and 'security audits'. Good coverage of how users would phrase requests.	3 / 3
Distinctiveness Conflict Risk	Has a clear niche in security auditing with distinct triggers like 'security scan', 'audit', 'vulnerability', and 'cryptography review'. References a specific plugin ('security-pro-pack'), making it unlikely to conflict with general code analysis or other skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 32e63e8

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.