skills/agentsecops/skill-name/SKILL.md
[REQUIRED] Comprehensive description of what this skill does and when to use it. Include: (1) Primary functionality, (2) Specific use cases, (3) Security operations context. Must include specific "Use when:" clause for skill discovery. Example: "SAST vulnerability analysis and remediation guidance using Semgrep and industry security standards. Use when: (1) Analyzing static code for security vulnerabilities, (2) Prioritizing security findings by severity, (3) Providing secure coding remediation, (4) Integrating security checks into CI/CD pipelines." Maximum 1024 characters.
npx skillsauth add aiskillstore/marketplace skill-nameInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Brief overview of what this skill provides and its security operations context.
Provide the minimal example to get started immediately:
# Example command or workflow
tool-name --option value
For straightforward step-by-step operations:
For complex multi-step operations, use a checkable workflow:
Progress: [ ] 1. Initial setup and configuration [ ] 2. Run primary security scan or analysis [ ] 3. Review findings and classify by severity [ ] 4. Apply remediation patterns [ ] 5. Validate fixes with re-scan [ ] 6. Document findings and generate report
Work through each step systematically. Check off completed items.
For more workflow patterns, see references/WORKFLOW_CHECKLIST.md
When validation and iteration are needed:
./scripts/validator_example.py output.yamlNote: Move detailed validation criteria to references/ if complex.
scripts/)Executable scripts for deterministic operations. Use scripts for low-freedom operations requiring consistency.
example_script.py - Python script template with argparse, error handling, and JSON outputexample_script.sh - Bash script template with argument parsing and colored outputvalidator_example.py - Validation script demonstrating feedback loop patternWhen to use scripts:
references/)On-demand documentation loaded when needed. Keep SKILL.md concise by moving detailed content here.
EXAMPLE.md - Template for reference documentation with security standards sectionsWORKFLOW_CHECKLIST.md - Multiple workflow pattern examples (sequential, conditional, iterative, feedback loop)When to use references:
assets/)Templates and configuration files used in output (not loaded into context). These are referenced but not read until needed.
ci-config-template.yml - Security-enhanced CI/CD pipeline with SAST, dependency scanning, secrets detectionrule-template.yaml - Security rule template with OWASP/CWE mappings and remediation guidanceWhen to use assets:
Description and example of common usage pattern.
Additional patterns as needed.
Solution: Steps to resolve.
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.