Individual skill

toolkit-research

Use when the user explicitly requests research with Baizhi Agent Toolkit. Discover the connected MCP tools and their current schemas, agree a request budget, and produce a sourced result without exposing credentials.

plugins/baizhi-agent-toolkit/skills/toolkit-research/SKILL.md

Read pinned source

Source commit b8e39b909f5e248090b16b2fd62048ba0ac6a70e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,740
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Research with Baizhi Agent Toolkit

This optional skill uses the MCP server registered by this plugin. A Baizhi
account and API key are required, and remote service usage may incur charges.
Invoke this skill explicitly; do not choose it merely because a task mentions
research. The connection alone does not authorize paid calls.

## Before calling a tool

1. Confirm the research question, destinations, and the user's permitted call or
   cost budget. Reuse an explicit budget already supplied for this task. If it is
   missing, ask before calling the service.
2. If the plugin is not configured, direct the user to the plugin configuration
   dialog. Never ask for a key in chat, print it, place it in command arguments,
Back to top