feat(skills): add composio-cli optional skill - #36730
Conversation
Add an optional devops skill that drives the local Composio CLI through the terminal tool to discover and run tools for 1000+ apps, connect accounts, inspect schemas, script workflows, listen for triggers, and proxy authenticated API calls. Includes a first-run flow that suggests apps to connect (grounded in composio search) when the user has no linked accounts.
First run is a pitch of known-supported apps, not a tool lookup. Reserve composio search for when the user picks a concrete task.
mxnstrexgl
left a comment
There was a problem hiding this comment.
🤖 Automated PR Review
Security Scan
- ✓ No hardcoded secrets, injection sinks, unsafe deserialization, or dependency red flags found by this automated scan.
Code Quality
- ✓ No blocking code-quality issues found by this automated scan.
Summary
Status: APPROVE — security findings: 0, quality suggestions: 0.
Automated review; raw diff content intentionally omitted.
We can use this skill over the previous one, thanks for flagging! |
teknium1
left a comment
There was a problem hiding this comment.
Thanks for contributing an optional CLI-based skill. The placement is compatible with the official optional-skill scanner in tools/skills_hub.py:3281, and current main has no equivalent Composio CLI skill.
Problems
optional-skills/devops/composio-cli/SKILL.md:87-88,126documents top-levelcomposio triggers/composio listen. The current Composio CLI documentation places these in the developer namespace:composio dev triggers ...andcomposio dev listen .... As written, the trigger quick reference, procedure, and verification path are not aligned with the documented CLI.optional-skills/devops/composio-cli/SKILL.md:17does not use the required# <Skill> Skillheading form fromAGENTS.md:933-940.- This new skill has no
tests/skills/test_composio_cli_skill.py, required byAGENTS.md:948-950.
Suggested changes
- Update the trigger commands to the documented
composio devforms and add a static no-network skill test that locks in the frontmatter and trigger guidance. - Rename the heading to
# Composio CLI Skill.
Automated hermes-sweeper review.
| | List trigger types | `composio triggers list github --limit 5` | | ||
| | Listen for events | `composio listen GMAIL_NEW_GMAIL_MESSAGE --timeout 5m --stream` | | ||
| | Find artifact directory | `composio artifacts cwd` | | ||
|
|
There was a problem hiding this comment.
The current Composio CLI docs put trigger listening in the developer namespace (composio dev listen --trigger-slug ... --max-events ...), not top-level composio listen. Please update this row and the related trigger-listing/procedure guidance at lines 87 and 126 so the documented workflow is executable.
|
|
||
| # Composio CLI | ||
|
|
||
| Drive the local `composio` CLI through the `terminal` tool to act in third-party apps such as GitHub, Gmail, Slack, Notion, Linear, Jira, and Google Calendar. The CLI manages its own auth, so it is the integration surface for connected apps. Use native Hermes tools for local files, shell work, code edits, browser work, and ordinary web research. |
There was a problem hiding this comment.
Please use # Composio CLI Skill. AGENTS.md:933-940 makes the # <Skill> Skill title form part of the hardline standard for new skills.
What & why
Adds an optional devops skill at
optional-skills/devops/composio-cli/that teaches Hermes to drive the local Composio CLI CLI through theterminaltool. Composio gives an agent managed-auth access to 1000+ apps (GitHub, Gmail, Slack, Notion, Linear, Jira, Google Calendar, …), so this skill lets Hermes discover and run tools, connect accounts, inspect schemas, script multi-step workflows, listen for triggers, and proxy authenticated API calls — without baking any API keys into the agent (the CLI owns its own auth).Users can easily manage their connected accounts on a centralized dashboard.
It's placed in
optional-skills/rather thanskills/because it depends on an externally-installed CLI and a Composio account, so it isn't universally needed.Notable behavior
composio connections listshows no linked accounts, the skill has the agent pitch concrete outcomes (social, fitness, devops, AI generation, Google Workspace, cross-app workflows) and connect one — each suggestion grounded in a realcomposio searchso it never promises a tool that doesn't exist.--dry-rununcertain writes, link accounts only when the CLI says there's no connection.Standards checklist
terminal,read_file); third-party CLI invoked throughterminal.requires_toolsets: [terminal];platforms: [macos, linux](installer is acurl | bashshell script).authorcredits the human contributor first.docker-management).How to test
hermes chat --toolsets skills -q "Use the composio-cli skill to find a tool that creates a GitHub issue"With the CLI installed (
curl -fsSL https://composio.dev/install | bash+composio login), the agent should check auth, list connections, search for the tool, and inspect its schema before doing anything.Platforms tested
macOS.