Replace ~~placeholder strings with readable tool names in user-facing text#89
Open
yoheidemachi wants to merge 1 commit intoanthropics:mainfrom
Open
Replace ~~placeholder strings with readable tool names in user-facing text#89yoheidemachi wants to merge 1 commit intoanthropics:mainfrom
yoheidemachi wants to merge 1 commit intoanthropics:mainfrom
Conversation
… text The ~~category convention is used internally for tool-agnostic references, but user-facing text (welcome messages, error messages, examples) should show actual tool names for clarity. - bio-research/commands/start.md: Replace ~~literature database, ~~chemical database, etc. with PubMed, ChEMBL, BioRender and other actual server names - enterprise-search/commands/search.md: Replace ~~chat, ~~email etc. in the "no sources connected" message with readable examples (e.g. Slack, Jira) - sales/skills/draft-outreach/SKILL.md: Replace "check ~~email" with "check your email client" Fixes anthropics#71 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Thanks for opening this PR for #71. One concern: in bio-research/commands/start.md, replacing categories with specific server names (PubMed/ChEMBL/BioRender, etc.) could be misleading for users who haven’t connected those MCP servers. Would you consider making these explicitly examples (e.g., “Literature (e.g., PubMed, bioRxiv)”) or switching to generic wording like “your literature database / your chemical database” while keeping the ~~category reference internally? |
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
Several plugin command and skill files display
~~categoryplaceholder strings verbatim to users instead of showing actual tool names. This makes the onboarding experience confusing.Changes
~~literature database,~~chemical database, etc. with actual server names (PubMed, ChEMBL, BioRender, etc.) from.mcp.json, keeping~~categoryin parentheses for reference~~chat,~~emailetc. in the "no sources connected" error message with readable examples (e.g. Slack, Jira, Notion)The
~~categoryconvention in CONNECTORS.md is preserved for internal/workflow references — only user-facing text (welcome messages, error messages, examples) is updated.Note
The original
start.mdcontained a~~clinical data platformentry ("clinical trial site ranking and platform help") which has no corresponding category inCONNECTORS.mdor server in.mcp.json. This line was removed as it appears to be an outdated/orphaned entry. If this should be kept, please let me know what the correct tool name is and I'll add it back.Fixes #71