Replace ~~placeholder strings with readable tool names in user-facing text

[yoheidemachi]

Summary

Several plugin command and skill files display ~~category placeholder strings verbatim to users instead of showing actual tool names. This makes the onboarding experience confusing.

Changes

File	Change
bio-research/commands/start.md	Replace ~~literature database, ~~chemical database, etc. with actual server names (PubMed, ChEMBL, BioRender, etc.) from .mcp.json, keeping ~~category in parentheses for reference
enterprise-search/commands/search.md	Replace ~~chat, ~~email etc. in the "no sources connected" error message with readable examples (e.g. Slack, Jira, Notion)
sales/skills/draft-outreach/SKILL.md	Replace "check ~~email" with "check your email client"

The ~~category convention in CONNECTORS.md is preserved for internal/workflow references — only user-facing text (welcome messages, error messages, examples) is updated.

Note

The original start.md contained a ~~clinical data platform entry ("clinical trial site ranking and platform help") which has no corresponding category in CONNECTORS.md or 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

[XinySu8]

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?

[fredchu]

Thanks for tackling this — the ~~placeholder strings showing verbatim to users is a real UX issue and this PR addresses the right files.

A few observations after looking at the current state of the repo:

bug: It looks like the repo has since migrated commands/ to skills/ for bio-research and enterprise-search. The paths this PR modifies (bio-research/commands/start.md, enterprise-search/commands/search.md) no longer exist on main, which is likely why the PR shows as conflicting. The current files are:

• bio-research/skills/start/SKILL.md
• enterprise-search/skills/search/SKILL.md

suggestion: As also noted in the comments, hardcoding specific server names (e.g., PubMed, ChEMBL) could be misleading when a user hasn't connected that particular server. Looking at CONNECTORS.md, the ~~category convention is intentionally tool-agnostic — each category can map to multiple servers (e.g., ~~literature could be PubMed, Google Scholar, or Semantic Scholar).

Would something like this work better for user-facing text?

- Literature search (e.g. PubMed, bioRxiv) — biomedical literature

This keeps it readable while making it clear these are examples, not requirements. For the enterprise-search error message, the current PR's approach ("a chat tool (e.g. Slack)") already does this well.

Happy to help rebase onto the current file structure if that would be useful.