Repository navigation
Ship the agentmail-agentid skill and release 0.4.0 - #15
Conversation
Export the new AgentID skill from agentmail-skills (#17) so Codex, Claude Code, and Cursor agents know how to find providers, sign an inbox in with connect_provider, and list provider accounts. The README gains an AgentID section with example prompts and per-client invocation, and every manifest now mentions AgentID so it shows up in marketplace listings. The version bump is what makes installed Claude Code and Codex plugins pick up the new skill. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Re-export agentmail-agentid, which is now organized around requests like "create an account at Firecrawl". The README AgentID section, the Codex long description and default prompt, and the changelog describe the product the same way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
| - "Log my agent back in to Turso." | ||
| - "Which services is support-bot@agentmail.to signed up for?" | ||
|
|
||
| The `agentmail-agentid` skill carries the whole job. It finds the provider, picks the inbox that will own the account (creating one if needed), and checks for an existing account and the provider's sign-up cap. Then it hands you a single-use sign-in link and confirms the account exists. Finally it helps you get what you came for, usually an API key stored in your secret store. Invoke it explicitly with `$agentmail-agentid` in Codex or `/agentmail:agentmail-agentid` in Claude Code; in Cursor, just ask. |
There was a problem hiding this comment.
Naming nit, and cheap only before 0.4.0 ships: this becomes /agentmail:agentmail-agentid. skills.json pluginExport.legacyIds already maps agentmail-* action skills to short IDs (send-email, …). Adding "agentmail-agentid": "agentid" would give /agentmail:agentid and $agentid, consistent with the others. Renaming after release breaks installs.
There was a problem hiding this comment.
Done. skills.json in agentmail-skills#17 now maps "agentmail-agentid": "agentid" in legacyIds (863fa6f). This PR re-exports it as skills/agentid/, so it's /agentmail:agentid and $agentid (6b51153). The README, changelog, and validate_repo.py MCP-dependency set use agentid, and so does the docs guide in agentmail-docs#279. It stays agentmail-agentid on skills.sh.
Re-export from agentmail-skills#17: the skill now exports under the short ID agentid (/agentmail:agentid, $agentid), matching send-email, check-email, and manage-inboxes, and picks up the review fixes on the sign-up cap, 404 meanings, and error codes. README, changelog, and the MCP-dependency check use the new ID. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@shalim786 Re-exported after the skills#17 fixes (6b51153), with the |
shalim786
left a comment
There was a problem hiding this comment.
Rename to agentid and the re-exported fixes look good (6b51153). LGTM. Merge order still applies: publish agentmail-toolkit 0.9.1 from #66, bump the connector's pin to it, regenerate mcp-manifest.json and deploy; then merge skills#17, plugins#15 and docs#279.
Summary
This makes AgentID (provider connect and accounts) available in the Cursor, Claude Code, and Codex plugins.
skills.py build --target .:skills/agentid/(canonicalagentmail-agentid, exported under the short IDagentidlikesend-email, so it's/agentmail:agentidand$agentid), with an MCP dependency inagents/openai.yamlagentmail-mcpnow covers Claude.ai / ChatGPT connector setup and the tool groupscheck-emailnow usesget_messageagentid, the CodexlongDescriptionexplains AgentID, and one CodexdefaultPromptis now "Create an account at Firecrawl for my agent with AgentID."validate_repo.py:agentidis added to the skills that must declare the hosted MCP dependency.Not changed: the
compatibility.jsonpins.check_compatibility.pyreports drift that was already there before this PR: TS SDK 0.5.31, Python SDK 2.0.5, CLI 1.7.0, toolkit TS 0.9.0. Moving those pins means re-verifying the SDK signature tests, which belongs in its own PR.Test plan
python3 scripts/validate_repo.py: passed (4 manifests, 9 skills)claude plugin validate . --strictand.claude-plugin/plugin.json --strict: passedskills.py build --check --target .against the skills branch: cleanlist_providersas a read-only checkMerge order
agentmail-toolkit0.9.1 to npmmcp-manifest.json, then confirm the connector deployskills.py sync --backendagainst the regenerated manifestSkills, plugins, and docs wait for the connector so they don't describe
ownerSignupLimitand unlisted-by-ID behavior that the live 0.9.0 tool descriptions contradict.🤖 Generated with Claude Code