🐋 Orca

SKILL manager for agentic workflows

Orca is an open-source framework for building, orchestrating, and deploying skills for AI agents. Orca provides a modular, extensible platform that empowers developers, researchers, and organizations to design autonomous systems with ease.

📁 Project Structure

orca/
├── scripts/         # Skill manage utilities
├── skills/          # Built-in skills library
├── docs/            # Documentation

🧰 Contributing guidelines

We welcome contributions from the community! To contribute:

• Fork the repository
• Create a feature branch (git checkout -b feature/my-feature)
• Commit changes (git commit -m "Add new feature")
• Push to branch (git push origin feature/my-feature)
• Open a Pull Request

🚀 Conventional Commit Types

| Type | Description | |------|-------------| | feat | A new feature implementation that directly provides value to end-users. | | fix | A bug resolution or patch in the application codebase. | | docs | Direct updates confined entirely to markdown files or documentation. | | style | Surface-level changes that do not affect the meaning of the code (formatting, whitespace, missing semicolons, etc.). | | refactor | Restructuring code without fixing a bug, updating performance, or adding a feature. | | perf | Targeted code optimizations meant explicitly to boost system performance metrics. | | test | Creating missing tests, adding test suites, or updating broken unit tests. | | build | Modifications altering external dependencies or the localized build system (e.g., npm, Webpack, Gradle). | | ci | Scripting adjustments made to continuous integration configuration layers (e.g., GitHub Actions, Jenkins). | | chore | Low-level maintenance work that doesn't modify source code or tests (e.g., updating .gitignore or project metadata). | | revert | Restoring the code state by backing out a previously merged commit. |

Format

<type>(<scope>)!: <summary>

Please read our Contribution Guidelines before submitting.