> performing-security-testing
This skill automates security vulnerability testing. It is triggered when the user requests security assessments, penetration tests, or vulnerability scans. The skill covers OWASP Top 10 vulnerabilities, SQL injection, XSS, CSRF, authentication issues, and authorization flaws. Use this skill when the user mentions "security test", "vulnerability scan", "OWASP", "SQL injection", "XSS", "CSRF", "authentication", or "authorization" in the context of application or API testing.
curl "https://skillshub.wtf/jeremylongshore/claude-code-plugins-plus-skills/security-test-scanner?format=md"Overview
This skill enables Claude to automatically perform security vulnerability testing on applications and APIs. It leverages the security-test-scanner plugin to identify potential weaknesses and generate comprehensive reports.
How It Works
- Initiate Scan: The plugin is activated when security testing is requested.
- Execute Tests: The plugin automatically runs a suite of security tests covering OWASP Top 10, injection flaws, XSS, CSRF, and authentication/authorization issues.
- Generate Report: The plugin compiles the test results into a detailed report, highlighting vulnerabilities, severity ratings, and remediation steps.
When to Use This Skill
This skill activates when you need to:
- Perform a security vulnerability scan of an application.
- Test for OWASP Top 10 vulnerabilities.
- Identify SQL injection or XSS vulnerabilities.
- Assess authentication and authorization security.
Examples
Example 1: OWASP Top 10 Vulnerability Scan
User request: "Perform a security test focusing on OWASP Top 10 vulnerabilities for the /api/ endpoint."
The skill will:
- Activate the security-test-scanner plugin.
- Execute OWASP Top 10 tests against the specified endpoint.
- Generate a report detailing any identified vulnerabilities and their severity.
Example 2: SQL Injection Testing
User request: "Test the API for SQL injection vulnerabilities."
The skill will:
- Activate the security-test-scanner plugin.
- Run SQL injection tests against the API.
- Report any successful injection attempts.
Best Practices
- Scope Definition: Clearly define the scope of the security test (e.g., specific endpoints, modules).
- Authentication: Provide necessary authentication credentials for testing protected resources.
- Regular Testing: Schedule regular security tests to identify newly introduced vulnerabilities.
Integration
This skill can be integrated with other plugins to automatically trigger security tests as part of a CI/CD pipeline or after code changes. It also integrates with reporting tools for centralized vulnerability management.
> related_skills --same-repo
> fathom-cost-tuning
Optimize Fathom API usage and plan selection. Trigger with phrases like "fathom cost", "fathom pricing", "fathom plan".
> fathom-core-workflow-b
Sync Fathom meeting data to CRM and build automated follow-up workflows. Use when integrating Fathom with Salesforce, HubSpot, or custom CRMs, or creating automated post-meeting email summaries. Trigger with phrases like "fathom crm sync", "fathom salesforce", "fathom follow-up", "fathom post-meeting workflow".
> fathom-core-workflow-a
Build a meeting analytics pipeline with Fathom transcripts and summaries. Use when extracting insights from meetings, building CRM sync, or creating automated meeting follow-up workflows. Trigger with phrases like "fathom analytics", "fathom meeting pipeline", "fathom transcript analysis", "fathom action items sync".
> fathom-common-errors
Diagnose and fix Fathom API errors including auth failures and missing data. Use when API calls fail, transcripts are empty, or webhooks are not firing. Trigger with phrases like "fathom error", "fathom not working", "fathom api failure", "fix fathom".