agentsclimarketplace
Sign in

Docsbot question history

Skill uglyrobot/docsbot-agent-skills/skills/docsbot-question-history

Search and fetch prior DocsBot bot questions, answers, and conversation history through a per-bot remote MCP server. Activate when a user asks to analyze support history, find past answers, review escalations, inspect unresolved questions, or reuse previous DocsBot conversations.From its SKILL.md

Install
npx -y skills add uglyrobot/docsbot-agent-skills --skill docsbot-question-history

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.9 KB, 535 tokens by cl100k_base, as published. Nobody here has run it

DocsBot Question History

Use this skill when working with a specific DocsBot bot's historical question and answer data through the per-bot Question History server:

https://api.docsbot.ai/teams/{teamId}/bots/{botId}/questions/mcp/

This server gives an authorized agent a focused read-only retrieval surface over prior bot conversations:

  • search runs semantic search across logged questions, answers, and conversation history.
  • fetch retrieves a full question or conversation by ID returned from search.

Search results can include operational metadata such as whether the bot could answer, escalation state, resolved state, sentiment, and topic when that data is available.

Setup

Configure the MCP server with the DocsBot team ID, bot ID, and a Bearer token:

{
  "mcpServers": {
    "docsbot-question-history": {
      "url": "https://api.docsbot.ai/teams/{teamId}/bots/{botId}/questions/mcp/",
      "headers": {
        "Authorization": "Bearer <TOKEN>"
      }
    }
  }
}

The token can be a DocsBot API key or a DocsBot MCP OAuth token prefixed with mcp-. Question History search requires a bot with at least 5,000 logged questions.

Workflow

  1. Identify the target DocsBot team and bot before searching.
  2. Use search first with the user's natural-language query, support topic, customer issue, escalation phrase, or answer pattern.
  3. Review result metadata such as couldAnswer, escalation, resolved, escalated, sentiment, and topic when present.
  4. Use fetch for question IDs returned by search when the task needs the full conversation or exact answer history.
  5. Summarize patterns, cite relevant prior answers, and call out limits when history is sparse or unavailable.

Constraints

  • Do not use this skill for DocsBot account administration; use DocsBot Administration for teams, bots, sources, settings, members, integrations, or billing.
  • Do not invent team IDs, bot IDs, question IDs, conversation history, or support outcomes.
  • Respect the privacy of logged questions and conversations. Do not expose more customer data than the user needs for the task.
  • If the bot has fewer than 5,000 logged questions, report that Question History search is not available for that bot yet.
  • Successful search and fetch calls consume DocsBot AI Credits.

References

What ships with it: 2 files

64.1 KB alongside SKILL.md

assets/

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.