Skills-4-SE
Over 180 software engineering skills for bugs, tests, requirements, DevOps, security and formal verification, plus task packs
- 260 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Skills may access system directories, install dependencies and execute code
- Pack scripts copy many skills into ~/.claude/skills in one run
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/skills-4-seDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Skills may access system directories, install dependencies and execute code
- Pack scripts copy many skills into ~/.claude/skills in one run
This is third-party code. Review the repository files before installing.
What it does
Skills-4-SE collects instructions for engineering tasks such as requirements work, testing and code maintenance. Each skill has its own directory with SKILL.md; some include scripts and reference files. Choose one task, such as unit-test generation, or install a thematic pack. Eight packs organize bug fixing, code quality, test automation and other areas. Separate groups cover formal methods and security checks. These are agent instructions, so outcomes depend on available tools and verification in the actual project. Two indexes organize the collection by category and development stage. Skills Manager adds search and filtering. Inspect the chosen skill directory and its proposed commands before installation.
Who it is for. For engineers and researchers who want ready skills for testing, debugging, requirements and verification in Claude Code.
Good fit when
- You need to find and localize a bug, and the Bug Fixing Suite with its 12 skills fits
- You need to generate tests and measure their value: Test Automation Suite holds 18 skills
- You write formal specifications or check invariants and need the Formal Verification Toolkit
- You need to turn requirements into tests and trace links between them, for example with the `req-to-test` and `traceability-matrix-generator` skills
- You need instructions for one development stage and want to select them through Skills Manager categories
Not a fit when
- You need one installation command for all eight collections: security-scanner-suite has no shared install.sh
- You need a collection usable without code review: individual skills run commands and change the environment
- You need a skill for a specific framework such as Rails or Next.js: the library is general and not tied to a stack
- You work in a locked-down environment where a skill must not touch system directories or install packages
Example request
Use the bug-localization skill to find the commit and file where this failure appeared, then propose a reproducing testLimitations
Pack installation requires Git, Bash and Python 3. Matching installed skill folders are deleted before copying, without a prompt or backup. Save local edits and start with one skill. The inspected Security Scanner Suite directory has no install.sh, so the shared installer skips it.
Older scanner reports cover an earlier collection and do not establish the safety of current files. Individual skills may install packages, execute tests and edit code. Check their dependencies and external services separately. The main installation directory is documented for Claude Code; the project uses Apache 2.0.
How to disable. Delete the folders of the skills you installed from ~/.claude/skills. If you installed a pack with a script, delete all skills of that pack.
FAQ
How do I install Skills-4-SE skills in Claude Code?
For the formal verification pack, use the full installation recipe. Alternatively, copy one folder, such as skills/unit-test-generator from the clone, into an existing ~/.claude/skills directory. The security pack lacks its own installation script.
Which packs does Skills-4-SE have?
Eight: Bug Fixing Suite, Code Quality Toolkit, Test Automation Suite, Requirements Engineering Suite, Code Understanding and Manipulation Suite, DevOps Automation Toolkit, Formal Verification Toolkit and Security Scanner Suite. They hold from 10 to 19 skills.
Does the scanner report establish that the collection is safe?
No. Reports cover a particular snapshot. Read the current SKILL.md and scripts before installation; evaluate file and package access in the context of your task.
What is Skills Manager?
The project's web interface with search and category filters, installing all skills at once or selected ones. You can deploy it locally; instructions are in the skill-manager folder.
Can I pick skills by development stage?
Yes, the README has two indexes: by category and by stage. Stages run from requirements and design through implementation, testing, verification, deployment and maintenance.
Discussion
No questions or reviews yet.
Related
SkillsA set of independent skills against drift in large codebases: hard-cut, root-cause tracing, lean testing and CI right-sizing.
Nine JS Mastery skills take a change through phases: from idea and spec to verification, tests, release texts and a docs sync
Over 200 skills by stack and practice: React, Next.js, Rails, Rust, Python, debugging, TDD and UI review
Fifteen skills from Warp: CI repair, pull requests, accessibility and SEO audits, web app testing and issue triage
Over 1,100 ready-made skills for Claude Code, Codex, Gemini CLI and Cursor, plus an MCP server that picks a skill for the task
common-skills by Warp
common-skills
Warp skills for team development: specs, PR descriptions and reviews, failed CI diagnosis and merge conflict resolution
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Skills-4-SE (this card) | no | 260 | |
| Claude Skills (Alireza Rezvani) | no | 29,373 | a fork of a large skill library with added 1C skills |
| RampStack Claude Skills | no | 1,038 | a skill library for the whole website lifecycle: brand, design, content, SEO and development |
README in short
The repository includes sample instructions and reports from earlier checks. They illustrate the author’s approach, but the current directory contents need separate review.
README badge
Original SKILL.md
--- name: function-class-generator description: Generate complete, production-ready functions and classes from formal specifications, design descriptions, type signatures, or natural language requirements. Use this skill when implementing APIs from specifications, creating data structures from schemas, building classes from UML diagrams, generating code from contracts, or translating design documents into code. Supports multiple programming languages and follows language-specific best practices. --- # Function/Class Generator Transform formal specifications, design descriptions, and requirements into complete, well-structured, production-ready code. Generates functions, classes, interfaces, and data structures with proper error handling, documentation, and tests. ## Core Capabilities ### 1. Specification Parsing Understand specifications from multiple sources: - **Type signatures** - Function signatures with input/output types - **Formal specifications** - Pre/postconditions, invariants, contracts - **API documentation** - OpenAPI, Swagger, JSON Schema - **UML diagrams** - Class diagrams, sequence diagrams - **Natural language** - Requirements and design descriptions - **Interface definitions** - Protocol buffers, GraphQL schemas ### 2. Code Generation Create complete implementations: - **Functions** - Standalone functions with logic and validation - **Classes** - Full class definitions with methods and properties - **Interfaces/Protocols** - Abstract definitions and contracts - **Data structures** - Custom types, enums, unions - **Error handling** - Exceptions, error types, validation - **Documentation** - Docstrings, comments, type hints ### 3. Best Practices Integration Apply language-specific patterns: - **Naming conventions** - Follow language standards - **Type safety** - Use static typing where available - **Error handling** - Appropriate exception handling - **Documentation** - Clear docstrings and comments - **Testing** - Generate unit tests alongside code - **SOLID principles** - Single responsibility, open/closed, etc. ### 4. Validation and Testing Ensure correctness: - **Type checking** - Verify type correctness