Skip to content
cccskills
FreePublished on GitHub

QA_source_index

Find relevant QwenPaw documentation and source files for questions about setup, configuration, skills, memory, and other features. It maps question keywords to likely file paths so the agent can read and verify the right material.

OriginalShow the original description

Maps topics and keywords from user questions to QwenPaw official documentation paths and common source code entry points, reducing blind searching. Intended for the built-in QA Agent to quickly identify which files to read when answering questions about installation, configuration, skills, MCP, multi-agent, memory, CLI, etc.

See how to install

Good for

  • Find documentation for installation or configuration questions
  • Locate source files related to skills or memory
  • Identify where to investigate errors or CLI behavior

Files included (1)

  • SKILL.md4.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Documentation and Source Code Quick Reference

When answering questions about installation, configuration, or behavioral principles, first classify by keyword, then open 1–2 paths most likely to contain the answer from the table below, avoiding aimless directory traversal.

Usage Steps

  1. Extract the topic from the user's question (match against the left column or synonyms in the table below).
  2. Resolve $QWENPAW_ROOT: use which qwenpaw to get the executable path. If it is …/.qwenpaw/bin/qwenpaw, the source root is three levels up (consistent with the guidance skill); otherwise, determine it from the user-provided installation path.
  3. Resolve $DOCS_DIR first (cross-install compatible): run python3 -c "from qwenpaw.constant import DOCS_DIR; print(DOCS_DIR or '')" 2>/dev/null. If it returns a valid path, use it directly. Otherwise, fallback to $QWENPAW_ROOT/website/public/docs/.
  4. Read documentation first: $DOCS_DIR/<topic>.<language>.md (use the same language as the user: zh / en.). If that is insufficient, read the source entry points listed in the table.

Topic / Keywords → Preferred Documentation and Source Code

Topic or Keywords (examples)Preferred Documentation ($DOCS_DIR/)Common Source Entry Points (relative to $QWENPAW_ROOT)
Installation, dependencies, getting startedquickstart, introsrc/qwenpaw/cli/, pyproject.toml
Configuration, config.json, environment variablesconfigsrc/qwenpaw/config/config.py, src/qwenpaw/constant.py
Skills, SKILL, skill_pool, built-in skillsskillssrc/qwenpaw/agents/skill_system/, src/qwenpaw/agents/skills/
MCP, pluginsmcpsrc/qwenpaw/app/routers/ (grep mcp as needed)
Multi-agent, workspace, agent, built-in QAmulti-agentsrc/qwenpaw/app/routers/agents.py, src/qwenpaw/app/migration.py, src/qwenpaw/constant.py (BUILTIN_QA_AGENT_ID, etc.)
Memory, MEMORY, memory_searchmemorysrc/qwenpaw/agents/memory/memory_manager.py, src/qwenpaw/agents/tools/memory_search.py
Console, frontendconsoleconsole/
CLI, subcommands, initclisrc/qwenpaw/cli/ (e.g., init_cmd.py)
Channels, sessionschannelsSearch for channels keyword under src/qwenpaw
Context, windowcontextconfig docs + related logic in src/qwenpaw/agents/
Models, API Keymodelssrc/qwenpaw/config/config.py
Heartbeat, HEARTBEATheartbeatSearch for heartbeat / HEARTBEAT under src/qwenpaw
Desktop clientdesktopdesktop/ (if present in the repository)
SecuritysecurityRead security.<lang>.md first
Errors, FAQfaqRead faq.<lang>.md first, then examine source code as needed
Commands and slash commandscommandsCLI/command registration modules under src/qwenpaw (search as needed)

Conventions

  • Full documentation path: $DOCS_DIR/<topic>.<language>.md (fall back to .en.md if the corresponding language file does not exist). Prefer DOCS_DIR from qwenpaw.constant; fallback to $QWENPAW_ROOT/website/public/docs/.
  • The source entry points in the table are starting points; use read_file or targeted grep to narrow down to specific symbols — do not read through an entire large directory listing at once.

Notes

  • This skill does not replace read_file: after identifying candidate paths, you should immediately read and verify the content.
  • If a path does not exist locally (e.g., an installation tree without source code), use the installed documentation package or the root directory provided by the user, and clearly state which path you are relying on.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

alicloud_cli

FreeSummary

Find installation steps, configuration guidance, and command examples for Alibaba Cloud CLI using local Chinese documentation. The skill checks its quick reference or relevant documentation pages before suggesting commands, parameters, and options.

  • Look up installation and configuration steps
  • Check commands for querying ECS instances
  • Find output filtering and pagination options
agentscope-ai/QwenPaw35.9KUpdated Oct 21, 2026

browser

FreeSummary

Use QwenPaw's built-in Browser SDK, a browser control interface, to read pages, search, fill forms, click controls, and capture screenshots through asynchronous Python. The workflow checks the page before and after actions and hands authentication steps to a person.

  • Search a website and inspect the resulting page
  • Fill forms and select options in a browser
  • Read page text and capture screenshots
agentscope-ai/QwenPaw35.9KUpdated Oct 21, 2026

browser

FreeSummary

Automate browser tasks through QwenPaw's built-in Browser SDK using asynchronous Python. Read page content, fill forms, click controls, and capture screenshots, checking the resulting page after each action to verify what happened.

  • Search a website and inspect the results
  • Fill forms and operate page controls
  • Capture page screenshots
agentscope-ai/QwenPaw35.9KUpdated Oct 21, 2026

browser_cdp

FreeSummary

Connect an agent to an existing Chrome browser, find local CDP ports used for remote browser control, or start a browser on a specified port for sharing with other agents and tools.

  • Connecting to Chrome with existing logins and open tabs
  • Finding available local browser debugging ports
  • Starting a browser on a fixed debugging port
agentscope-ai/QwenPaw35.9KUpdated Oct 21, 2026

browser_cdp

FreeSummary

Connect to an existing Chrome browser or launch one with an explicit debugging port for sharing across agents and tools. It also covers scanning local CDP ports, the connection endpoints used to control a browser.

  • Connect to Chrome with existing logins and open tabs
  • Find available local browser debugging ports
  • Launch a browser with a fixed debugging port
agentscope-ai/QwenPaw35.9KUpdated Oct 21, 2026

browser_visible

FreeSummary

Configure how the browser starts, including window visibility, proxy settings, extra launch options, and a custom browser executable. It also explains opening a local debugging port so other local tools can connect.

  • Show the browser window during automation
  • Start a browser with a proxy or incognito mode
  • Choose a specific installed browser
agentscope-ai/QwenPaw35.9KUpdated Oct 21, 2026

See all skills by agentscope-ai

Report a problem with this skill