Repository navigation
Re-export the skills with AgentID apps and release 0.5.0 - #16
Merged
Merged
Conversation
AgentMail is renaming the AgentID noun "provider" to "app"
(plans/specs/provider-to-app-rename-phase-1.md in agentmail-api). The
hosted MCP tools are renamed outright to list_apps, search_apps,
get_app and connect_app, with appId / appName fields.
- skills/ is re-exported from the agentmail-skills PR branch with
`skills.py build --target`: agentid ("AgentID: Accounts at Apps",
plus its openai.yaml display copy), agentmail-mcp, and the "Connect
inbox to app" row in the agent-email-patterns threat model.
- README: the AgentID intro, the tool table, and the safety model say
app and name the app tools.
- CHANGELOG adds 0.5.0, and every manifest is bumped to 0.5.0 so
installed plugins pick up the renamed tools.
provider_connect stays the permission name until phase 2.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Sep 30, 2026
Closed
Contributor
Author
|
Dependency links (opened after this PR): agentmail-api phase 1 is agentmail-to/agentmail-api#1512; the Fern/SDK change is agentmail-to/agentmail-docs#282. |
Folded from #17 so the rename ships as one 0.5.0 release (one changelog entry). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Folded #17 in: skills re-exported with |
sidharth0612
marked this pull request as ready for review
October 1, 2026 23:36
duharry0915
approved these changes
Oct 1, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This mirrors agentmail-to/agentmail-skills#18. AgentID's services are now apps, and the hosted MCP tools are renamed outright with no aliases:
list_apps,search_apps,get_appandconnect_app, withappId/appNamefields.list_accountskeeps its name.skills/: re-exported from the skills PR branch withpython3 scripts/skills.py build --target <this checkout>. Only these generated files changed:skills/agentid/SKILL.md: "AgentID: Accounts at Apps", with the app tools and fields, and "App" as the resource a 404 names.skills/agentid/agents/openai.yaml: "Create accounts at apps for your agent".skills/agentmail-mcp/SKILL.md: the catalog group and the verify step.skills/agent-email-patterns/references/threat-model.md: the canonical row is "Connect inbox to app".README.md: the AgentID intro and the tool table now list the app tools, and the safety model says "App sign-ins require a direct request naming the app and inbox."CHANGELOG.md: a new0.5.0 - Unreleasedentry. Earlier entries are left as written, since they are history..claude-plugin,.codex-plugin,.cursor-plugin,.plugin) are bumped to 0.5.0, so installed Claude Code and Codex plugins pick up the renamed tools. This follows the 0.4.0 release.Unchanged on purpose
provider_connectpermission name in the README and the skill. It is renamed in phase 2.agent-email-patterns.compatibility.json. Its drift predates this PR and it doesn't cover this change.Dependencies (why this is a draft)
Ship together with agentmail-to/agentmail-skills#18, and only after agentmail-to/agentmail-mcp#63 is deployed. The 0.5.0 bump is what reaches installed plugins. Shipping it before the connector serves the app tools would point agents at tools that don't exist yet.
Before marking ready
python3 scripts/skills.py build --target <this checkout>from agentmail-skills.UnreleasedinCHANGELOG.mdwith the release date.Checks run
python3 scripts/validate_repo.py: passed (4 manifests, 9 skills). This includes the manifest-version sync and the CHANGELOG entry check.claude plugin validate . --strict: passed.python3 scripts/skills.py build --check --target <this checkout>is clean.Release order
Phase 1 of the provider → app rename. The spec is
plans/specs/provider-to-app-rename-phase-1.mdin agentmail-api./v0/apps*beside/v0/providers*and addsapp_id/app_nameto every Account.apps.yml. agentmail-node then releasesclient.apps.*, withclient.providers.*kept but deprecated.agentmailto that SDK, then publishagentmail-toolkit0.10.0.mcp-manifest.json, then deploy the connector.backend-contract.jsonagainst agentmail-mcpmain) and Re-export the skills with AgentID apps and release 0.5.0 #16 (re-export from Release 0.5.0 #18).The MCP tools are renamed outright, with no alias tools. Once the connector deploys, the skills and plugins must ship the same day. Until then they name tools that no longer exist.
🤖 Generated with Claude Code