QA_source_index-en

Name: QA_source_index-en
Author: agentscope-ai

24kstars2.8kforks

How to install QA_source_index-en?

agentscope-ai/qwenpaw/qa_source_index-en

$npx -y skills add agentscope-ai/QwenPaw --skill QA_source_index-en

Installs into the current project.

Summary

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, configuratio

Files · 1

View on GitHub

SKILL.md

1	# Documentation and Source Code Quick Reference
2
3	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.
4
5	## Usage Steps
6
7	1. Extract the topic from the user's question (match against the left column or synonyms in the table below).
8	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.
9	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/`.
10	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.
11
12	## Topic / Keywords → Preferred Documentation and Source Code
13
14	\| Topic or Keywords (examples) \| Preferred Documentation (`$DOCS_DIR/`) \| Common Source Entry Points (relative to `$QWENPAW_ROOT`) \|
15	\|---------------------\|-----------------------------------\|-----------------------------------\|
16	\| Installation, dependencies, getting started \| `quickstart`, `intro` \| `src/qwenpaw/cli/`, `pyproject.toml` \|
17	\| Configuration, config.json, environment variables \| `config` \| `src/qwenpaw/config/config.py`, `src/qwenpaw/constant.py` \|
18	\| Skills, SKILL, skill_pool, built-in skills \| `skills` \| `src/qwenpaw/agents/skill_system/`, `src/qwenpaw/agents/skills/` \|
19	\| MCP, plugins \| `mcp` \| `src/qwenpaw/app/routers/` (grep `mcp` as needed) \|
20	\| Multi-agent, workspace, agent, built-in QA \| `multi-agent` \| `src/qwenpaw/app/routers/agents.py`, `src/qwenpaw/app/migration.py`, `src/qwenpaw/constant.py` (`BUILTIN_QA_AGENT_ID`, etc.) \|
21	\| Memory, MEMORY, memory_search \| `memory` \| `src/qwenpaw/agents/memory/memory_manager.py`, `src/qwenpaw/agents/tools/memory_search.py` \|
22	\| Console, frontend \| `console` \| `console/` \|
23	\| CLI, subcommands, init \| `cli` \| `src/qwenpaw/cli/` (e.g., `init_cmd.py`) \|
24	\| Channels, sessions \| `channels` \| Search for `channels` keyword under `src/qwenpaw` \|
25	\| Context, window \| `context` \| `config` docs + related logic in `src/qwenpaw/agents/` \|
26	\| Models, API Key \| `models` \| `src/qwenpaw/config/config.py` \|
27	\| Heartbeat, HEARTBEAT \| `heartbeat` \| Search for `heartbeat` / `HEARTBEAT` under `src/qwenpaw` \|
28	\| Desktop client \| `desktop` \| `desktop/` (if present in the repository) \|
29	\| Security \| `security` \| Read `security.<lang>.md` first \|
30	\| Errors, FAQ \| `faq` \| Read `faq.<lang>.md` first, then examine source code as needed \|
31	\| Commands and slash commands \| `commands` \| CLI/command registration modules under `src/qwenpaw` (search as needed) \|
32
33	## Conventions
34
35	- 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/`.
36	- 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.
37
38	## Notes
39
40	- This skill does not replace `read_file`: after identifying candidate paths, you should immediately read and verify the content.
41	- 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.

People who liked this also viewed

6 picks

Type

QA_source_index-en

24kstars2.8kforks

View on GitHub

How to install QA_source_index-en?

agentscope-ai/qwenpaw/qa_source_index-en

$npx -y skills add agentscope-ai/QwenPaw --skill QA_source_index-en

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Documentation and Source Code Quick Reference
2
3	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.
4
5	## Usage Steps
6
7	1. Extract the topic from the user's question (match against the left column or synonyms in the table below).
8	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.
9	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/`.
10	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.
11
12	## Topic / Keywords → Preferred Documentation and Source Code
13
14	\| Topic or Keywords (examples) \| Preferred Documentation (`$DOCS_DIR/`) \| Common Source Entry Points (relative to `$QWENPAW_ROOT`) \|
15	\|---------------------\|-----------------------------------\|-----------------------------------\|
16	\| Installation, dependencies, getting started \| `quickstart`, `intro` \| `src/qwenpaw/cli/`, `pyproject.toml` \|
17	\| Configuration, config.json, environment variables \| `config` \| `src/qwenpaw/config/config.py`, `src/qwenpaw/constant.py` \|
18	\| Skills, SKILL, skill_pool, built-in skills \| `skills` \| `src/qwenpaw/agents/skill_system/`, `src/qwenpaw/agents/skills/` \|
19	\| MCP, plugins \| `mcp` \| `src/qwenpaw/app/routers/` (grep `mcp` as needed) \|
20	\| Multi-agent, workspace, agent, built-in QA \| `multi-agent` \| `src/qwenpaw/app/routers/agents.py`, `src/qwenpaw/app/migration.py`, `src/qwenpaw/constant.py` (`BUILTIN_QA_AGENT_ID`, etc.) \|
21	\| Memory, MEMORY, memory_search \| `memory` \| `src/qwenpaw/agents/memory/memory_manager.py`, `src/qwenpaw/agents/tools/memory_search.py` \|
22	\| Console, frontend \| `console` \| `console/` \|
23	\| CLI, subcommands, init \| `cli` \| `src/qwenpaw/cli/` (e.g., `init_cmd.py`) \|
24	\| Channels, sessions \| `channels` \| Search for `channels` keyword under `src/qwenpaw` \|
25	\| Context, window \| `context` \| `config` docs + related logic in `src/qwenpaw/agents/` \|
26	\| Models, API Key \| `models` \| `src/qwenpaw/config/config.py` \|
27	\| Heartbeat, HEARTBEAT \| `heartbeat` \| Search for `heartbeat` / `HEARTBEAT` under `src/qwenpaw` \|
28	\| Desktop client \| `desktop` \| `desktop/` (if present in the repository) \|
29	\| Security \| `security` \| Read `security.<lang>.md` first \|
30	\| Errors, FAQ \| `faq` \| Read `faq.<lang>.md` first, then examine source code as needed \|
31	\| Commands and slash commands \| `commands` \| CLI/command registration modules under `src/qwenpaw` (search as needed) \|
32
33	## Conventions
34
35	- 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/`.
36	- 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.
37
38	## Notes
39
40	- This skill does not replace `read_file`: after identifying candidate paths, you should immediately read and verify the content.
41	- 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.

People who liked this also viewed

6 picks

Type