- Home
- Skills
- Agents & Orchestration
- Brain-corp Agent Skills
Works with the AI Agents you already use
Brain-corp Agent Skills
Automate multi-repo analysis, Spec-Driven Development, and ticket lifecycle management for the brain-corp ecosystem.
Free
Brain-corp Agent Skills
Example session with this skill installed
Analyze the ecosystem for integration gaps between the auth-provider and web-client repositories and create a ticket for any missing fields.
- Read your context and instructions
- Compiled the brain-corp agent
I have completed the cross-repository analysis between auth-provider and web-client. I identified a missing field in the login response schema that is required by the client dashboard.
Analysis Results
| Repository | Role | Finding | Ticket Created |
|---|---|---|---|
| auth-provider | provider | Missing last_login_at in AuthResponse DTO | TICK-042 |
| web-client | client | Dashboard requires last_login_at for session audit | TICK-042 |
A new ticket has been generated in .agents/tickets/backlog/TICK-042-add-last-login-timestamp.md with the following frontmatter:
---
id: "TICK-042"
title: "Add last_login_at timestamp to AuthResponse"
author: "Brain-Corp Analyst"
target_domain: "shared"
status: "backlog"
created_at: "2023-10-27"
dependencies: []
---
Next steps
- Run
brain init-work TICK-042 --repo auth-providerto start the implementation. - Execute
brain specify TICK-042to generate the EARS specification. - Run
brain syncif you want to publish this ticket to GitHub Issues.
Connects securely to your tools. The creator never sees your data.
About this skill
Managing multi-repository ecosystems often leads to fragmented requirements, stale tickets, and integration gaps that slow down development. Manual coordination between providers and clients is error-prone and difficult to track across different sidecars.
This skill package provides a specialized interface for the brain-corp ecosystem, enabling automated cross-repo analysis and structured feature implementation. It bridges the gap between high-level requirements and local development by enforcing strict ticket formats, Spec-Driven Development (SDD) workflows, and GitHub synchronization.
What it does
- Ecosystem analysis scans for integration gaps between provider and client repositories and records them as actionable tickets.
- Spec-Driven Development automates the creation of EARS-compliant specifications, technical plans, and atomic task lists from tickets.
- Lifecycle management synchronizes local tickets with GitHub Issues, validates ticket coherence, and manages the completion of work.
- Pull request automation generates standardized PR bodies in English or Spanish using ticket metadata without leaving the terminal.
- Workspace initialization bootstraps new environments by registering sidecars, setting roles, and provisioning agent directives.
How it works
- Bootstrap the environment using the setup command to map repository relationships and preferred languages.
- Identify work by running the analysis workflow to detect gaps or by importing existing issues from GitHub.
- Execute the SDD loop to generate specs, plans, and tasks before implementing changes in a controlled checkpoint mode.
- Deliver changes by running sanity checks on the ticket state and opening the pull request using bundled templates.
Frameworks & tools
This tool integrates with Node.js 18+, git, and the GitHub CLI (gh). It specifically interfaces with the @rgkoko/brain-corp CLI and manages files within .brain/, .agents/, and config/system-map.json.
Why this beats prompting it yourself
Generic prompts often miss cross-repository dependencies and fail to maintain consistent ticket structures across large projects. This skill enforces the exact brain-corp CLI contracts and EARS formatting rules, ensuring that every architectural change is verified and tracked.
Use cases
- Bootstrap new sidecars by initializing the system map and repo roles for a multi-service project.
- Audit API contracts by scanning provider schemas against client view implementations to find missing fields.
- Implement complex features using the SDD flow to ensure requirements are planned before code is written.
- Automate release documentation by generating PR descriptions that map directly back to verified technical requirements.
Known limitations
Requires an authenticated GitHub CLI for PR and sync operations. It does not perform git commit, push, or merge actions, which must be handled by the user.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Requires Node.js 18+ and GitHub CLI (gh) authentication. Does not perform git commit, push, or merge. Interactive setup prompts may require manual terminal execution.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
8 uses
Times used to date
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 8 days ago
- Free with an Agensi account
- Accounts
GitHub
- Software
- @rgkoko/brain-corp
Node.js
Gitandequivalent.fallback
Permissions
Allowed Hosts