cx-viewer 1.0.2 → 1.0.4

package/concepts/en/Tool-SendMessage.md

@@ -1,41 +0,0 @@
-# SendMessage
-
-## Definition
-
-Sends messages between agents within a team. Used for direct communication, broadcasting, and protocol messages (shutdown requests/responses, plan approval).
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `to` | string | Yes | Recipient: teammate name, or `"*"` for broadcast to all |
-| `message` | string / object | Yes | Plain text message or structured protocol object |
-| `summary` | string | No | A 5-10 word preview shown in the UI |
-
-## Message Types
-
-### Plain Text
-Direct messages between teammates for coordination, status updates, and task discussions.
-
-### Shutdown Request
-Asks a teammate to gracefully shut down: `{ type: "shutdown_request", reason: "..." }`
-
-### Shutdown Response
-Teammate approves or rejects a shutdown: `{ type: "shutdown_response", approve: true/false }`
-
-### Plan Approval Response
-Approves or rejects a teammate's plan: `{ type: "plan_approval_response", approve: true/false }`
-
-## Broadcast vs Direct
-
-- **Direct** (`to: "teammate-name"`): Send to a specific teammate — preferred for most communication
-- **Broadcast** (`to: "*"`): Send to all teammates — use sparingly, only for critical team-wide announcements
-
-## Related Tools
-
-| Tool | Purpose |
-|------|---------|
-| `TeamCreate` | Create a new team |
-| `TeamDelete` | Remove team when done |
-| `Agent` | Spawn teammates that join the team |
-| `TaskCreate` / `TaskUpdate` / `TaskList` | Manage the shared task list |

package/concepts/en/Tool-Skill.md

@@ -1,56 +0,0 @@
-# Skill
-
-## Definition
-
-Executes a skill within the main conversation. Skills are specialized capabilities that users can invoke via slash commands (e.g., `/commit`, `/review-pr`).
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `skill` | string | Yes | Skill name (e.g., "commit", "review-pr", "pdf") |
-| `args` | string | No | Skill arguments |
-
-## Use Cases
-
-**Good for:**
-- When the user enters a slash command in the `/<skill-name>` format
-- When the user's request matches the functionality of a registered skill
-
-**Not good for:**
-- Built-in CLI commands (e.g., `/help`, `/clear`)
-- A skill that is already running
-- Skill names not in the available skills list
-
-## Notes
-
-- Once invoked, the skill expands into a full prompt
-- Supports fully qualified names (e.g., `ms-office-suite:pdf`)
-- The available skills list is provided in system-reminder messages
-- When you see a `<command-name>` tag, it means the skill is already loaded — execute it directly rather than calling this tool again
-- Do not mention a skill without actually calling the tool
-
-## Original Text
-
-<textarea readonly>Execute a skill within the main conversation
-
-When users ask you to perform tasks, check if any of the available skills match. Skills provide specialized capabilities and domain knowledge.
-
-When users reference a "slash command" or "/<something>" (e.g., "/commit", "/review-pr"), they are referring to a skill. Use this tool to invoke it.
-
-How to invoke:
-- Use this tool with the skill name and optional arguments
-- Examples:
-  - `skill: "pdf"` - invoke the pdf skill
-  - `skill: "commit", args: "-m 'Fix bug'"` - invoke with arguments
-  - `skill: "review-pr", args: "123"` - invoke with arguments
-  - `skill: "ms-office-suite:pdf"` - invoke using fully qualified name
-
-Important:
-- Available skills are listed in system-reminder messages in the conversation
-- When a skill matches the user's request, this is a BLOCKING REQUIREMENT: invoke the relevant Skill tool BEFORE generating any other response about the task
-- NEVER mention a skill without actually calling this tool
-- Do not invoke a skill that is already running
-- Do not use this tool for built-in CLI commands (like /help, /clear, etc.)
-- If you see a <command-name> tag in the current conversation turn, the skill has ALREADY been loaded - follow the instructions directly instead of calling this tool again
-</textarea>

package/concepts/en/Tool-Task.md

@@ -1,51 +0,0 @@
-# Task
-
-> **Note:** In newer versions of Claude Code, this tool has been renamed to **Agent**. See the [Tool-Agent](Tool-Agent) document.
-
-## Definition
-
-Launches a SubAgent to autonomously handle complex multi-step tasks. SubAgents are independent subprocesses, each with their own dedicated tool set and context.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `prompt` | string | Yes | Description of the task for the SubAgent to execute |
-| `description` | string | Yes | A 3-5 word short summary |
-| `subagent_type` | string | Yes | SubAgent type, determines the available tool set |
-| `model` | enum | No | Specify model (sonnet / opus / haiku), defaults to inheriting from parent |
-| `max_turns` | integer | No | Maximum number of agentic turns |
-| `run_in_background` | boolean | No | Whether to run in the background; background tasks return an output_file path |
-| `resume` | string | No | Agent ID to resume, continues from the last execution |
-| `isolation` | enum | No | Isolation mode, `worktree` creates a temporary git worktree |
-
-## SubAgent Types
-
-| Type | Purpose | Available Tools |
-|------|---------|-----------------|
-| `Bash` | Command execution, git operations | Bash |
-| `general-purpose` | General multi-step tasks | All tools |
-| `Explore` | Quick codebase exploration | All tools except Task/Edit/Write/NotebookEdit/ExitPlanMode |
-| `Plan` | Design implementation plans | All tools except Task/Edit/Write/NotebookEdit/ExitPlanMode |
-| `claude-code-guide` | Claude Code usage guide Q&A | Glob, Grep, Read, WebFetch, WebSearch |
-| `statusline-setup` | Configure status bar | Read, Edit |
-
-## Use Cases
-
-**Good for:**
-- Complex tasks requiring multi-step autonomous completion
-- Codebase exploration and deep research (using Explore type)
-- Parallel work requiring isolated environments
-- Long-running tasks that need to run in the background
-
-**Not good for:**
-- Reading a specific file path — use Read or Glob directly
-- Searching within 2-3 known files — use Read directly
-- Searching for a specific class definition — use Glob directly
-
-## Notes
-
-- After completion, the SubAgent returns a single message; its results are not visible to the user and need to be relayed by the main agent
-- Multiple Task calls can be issued in parallel within a single message for efficiency
-- Background tasks are checked for progress via the TaskOutput tool
-- The Explore type is slower than directly calling Glob/Grep; only use it when simple searches are insufficient

package/concepts/en/Tool-TaskCreate.md

@@ -1,78 +0,0 @@
-# TaskCreate
-
-## Definition
-
-Creates a structured task list entry for tracking progress, organizing complex tasks, and demonstrating work progress to the user.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `subject` | string | Yes | Short task title in imperative form (e.g., "Fix authentication bug") |
-| `description` | string | Yes | Detailed description including context and acceptance criteria |
-| `activeForm` | string | No | Present continuous text displayed when in progress (e.g., "Fixing authentication bug") |
-| `metadata` | object | No | Arbitrary metadata attached to the task |
-
-## Use Cases
-
-**Good for:**
-- Complex multi-step tasks (more than 3 steps)
-- When the user provides multiple to-do items
-- Tracking work in plan mode
-- When the user explicitly requests a todo list
-
-**Not good for:**
-- A single simple task
-- Simple operations with 3 or fewer steps
-- Pure conversation or information queries
-
-## Notes
-
-- All newly created tasks have an initial status of `pending`
-- `subject` uses imperative form ("Run tests"), `activeForm` uses present continuous ("Running tests")
-- After creating a task, use TaskUpdate to set dependencies (blocks/blockedBy)
-- Before creating, call TaskList first to check for duplicate tasks
-
-## Original Text
-
-<textarea readonly>Use this tool to create a structured task list for your current coding session. This helps you track progress, organize complex tasks, and demonstrate thoroughness to the user.
-It also helps the user understand the progress of the task and overall progress of their requests.
-
-## When to Use This Tool
-
-Use this tool proactively in these scenarios:
-
-- Complex multi-step tasks - When a task requires 3 or more distinct steps or actions
-- Non-trivial and complex tasks - Tasks that require careful planning or multiple operations
-- Plan mode - When using plan mode, create a task list to track the work
-- User explicitly requests todo list - When the user directly asks you to use the todo list
-- User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)
-- After receiving new instructions - Immediately capture user requirements as tasks
-- When you start working on a task - Mark it as in_progress BEFORE beginning work
-- After completing a task - Mark it as completed and add any new follow-up tasks discovered during implementation
-
-## When NOT to Use This Tool
-
-Skip using this tool when:
-- There is only a single, straightforward task
-- The task is trivial and tracking it provides no organizational benefit
-- The task can be completed in less than 3 trivial steps
-- The task is purely conversational or informational
-
-NOTE that you should not use this tool if there is only one trivial task to do. In this case you are better off just doing the task directly.
-
-## Task Fields
-
-- **subject**: A brief, actionable title in imperative form (e.g., "Fix authentication bug in login flow")
-- **description**: Detailed description of what needs to be done, including context and acceptance criteria
-- **activeForm**: Present continuous form shown in spinner when task is in_progress (e.g., "Fixing authentication bug"). This is displayed to the user while you work on the task.
-
-**IMPORTANT**: Always provide activeForm when creating tasks. The subject should be imperative ("Run tests") while activeForm should be present continuous ("Running tests"). All tasks are created with status `pending`.
-
-## Tips
-
-- Create tasks with clear, specific subjects that describe the outcome
-- Include enough detail in the description for another agent to understand and complete the task
-- After creating tasks, use TaskUpdate to set up dependencies (blocks/blockedBy) if needed
-- Check TaskList first to avoid creating duplicate tasks
-</textarea>

package/concepts/en/Tool-TaskGet.md

@@ -1,56 +0,0 @@
-# TaskGet
-
-## Definition
-
-Retrieves the full details of a task by its task ID.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `taskId` | string | Yes | The task ID to retrieve |
-
-## Return Content
-
-- `subject` — Task title
-- `description` — Detailed requirements and context
-- `status` — Status: `pending`, `in_progress`, or `completed`
-- `blocks` — List of tasks blocked by this task
-- `blockedBy` — List of prerequisite tasks blocking this task
-
-## Use Cases
-
-**Good for:**
-- Getting the full description and context of a task before starting work
-- Understanding task dependencies
-- Getting complete requirements after being assigned a task
-
-## Notes
-
-- After retrieving a task, check whether the `blockedBy` list is empty before starting work
-- Use TaskList to view summary information for all tasks
-
-## Original Text
-
-<textarea readonly>Use this tool to retrieve a task by its ID from the task list.
-
-## When to Use This Tool
-
-- When you need the full description and context before starting work on a task
-- To understand task dependencies (what it blocks, what blocks it)
-- After being assigned a task, to get complete requirements
-
-## Output
-
-Returns full task details:
-- **subject**: Task title
-- **description**: Detailed requirements and context
-- **status**: 'pending', 'in_progress', or 'completed'
-- **blocks**: Tasks waiting on this one to complete
-- **blockedBy**: Tasks that must complete before this one can start
-
-## Tips
-
-- After fetching a task, verify its blockedBy list is empty before beginning work.
-- Use TaskList to see all tasks in summary form.
-</textarea>

package/concepts/en/Tool-TaskList.md

@@ -1,56 +0,0 @@
-# TaskList
-
-## Definition
-
-Lists all tasks in the task list to view overall progress and available work.
-
-## Parameters
-
-No parameters.
-
-## Return Content
-
-Summary information for each task:
-- `id` — Task identifier
-- `subject` — Short description
-- `status` — Status: `pending`, `in_progress`, or `completed`
-- `owner` — Owner (agent ID), empty means unassigned
-- `blockedBy` — List of incomplete task IDs blocking this task
-
-## Use Cases
-
-**Good for:**
-- Viewing available tasks (status is pending, no owner, not blocked)
-- Checking overall project progress
-- Finding blocked tasks
-- Finding the next task after completing one
-
-## Notes
-
-- Prefer processing tasks in ID order (lowest ID first), as earlier tasks usually provide context for later ones
-- Tasks with `blockedBy` cannot be claimed until dependencies are resolved
-- Use TaskGet to get full details of a specific task
-
-## Original Text
-
-<textarea readonly>Use this tool to list all tasks in the task list.
-
-## When to Use This Tool
-
-- To see what tasks are available to work on (status: 'pending', no owner, not blocked)
-- To check overall progress on the project
-- To find tasks that are blocked and need dependencies resolved
-- After completing a task, to check for newly unblocked work or claim the next available task
-- **Prefer working on tasks in ID order** (lowest ID first) when multiple tasks are available, as earlier tasks often set up context for later ones
-
-## Output
-
-Returns a summary of each task:
-- **id**: Task identifier (use with TaskGet, TaskUpdate)
-- **subject**: Brief description of the task
-- **status**: 'pending', 'in_progress', or 'completed'
-- **owner**: Agent ID if assigned, empty if available
-- **blockedBy**: List of open task IDs that must be resolved first (tasks with blockedBy cannot be claimed until dependencies resolve)
-
-Use TaskGet with a specific task ID to view full details including description and comments.
-</textarea>

package/concepts/en/Tool-TaskOutput.md

@@ -1,40 +0,0 @@
-# TaskOutput
-
-## Definition
-
-Gets the output of a running or completed background task. Applicable to background shells, async agents, and remote sessions.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `task_id` | string | Yes | Task ID |
-| `block` | boolean | Yes | Whether to block and wait for task completion, default `true` |
-| `timeout` | number | Yes | Maximum wait time in milliseconds, default 30000, max 600000 |
-
-## Use Cases
-
-**Good for:**
-- Checking the progress of background agents launched via Task (`run_in_background: true`)
-- Getting the execution results of background Bash commands
-- Waiting for async tasks to complete and retrieving output
-
-**Not good for:**
-- Foreground tasks — foreground tasks return results directly, no need for this tool
-
-## Notes
-
-- `block: true` blocks until the task completes or times out
-- `block: false` is for non-blocking checks of the current status
-- Task IDs can be found via the `/tasks` command
-- Applicable to all task types: background shells, async agents, remote sessions
-
-## Original Text
-
-<textarea readonly>- Retrieves output from a running or completed task (background shell, agent, or remote session)
-- Takes a task_id parameter identifying the task
-- Returns the task output along with status information
-- Use block=true (default) to wait for task completion
-- Use block=false for non-blocking check of current status
-- Task IDs can be found using the /tasks command
-- Works with all task types: background shells, async agents, and remote sessions</textarea>

package/concepts/en/Tool-TaskStop.md

@@ -1,32 +0,0 @@
-# TaskStop
-
-## Definition
-
-Stops a running background task.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `task_id` | string | No | The background task ID to stop |
-| `shell_id` | string | No | Deprecated, use `task_id` instead |
-
-## Use Cases
-
-**Good for:**
-- Terminating long-running tasks that are no longer needed
-- Canceling erroneously started background tasks
-
-## Notes
-
-- Returns a success or failure status
-- The `shell_id` parameter is deprecated; use `task_id` instead
-
-## Original Text
-
-<textarea readonly>
-- Stops a running background task by its ID
-- Takes a task_id parameter identifying the task to stop
-- Returns a success or failure status
-- Use this tool when you need to terminate a long-running task
-</textarea>

package/concepts/en/Tool-TaskUpdate.md

@@ -1,123 +0,0 @@
-# TaskUpdate
-
-## Definition
-
-Updates the status, content, or dependencies of a task in the task list.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `taskId` | string | Yes | The task ID to update |
-| `status` | enum | No | New status: `pending` / `in_progress` / `completed` / `deleted` |
-| `subject` | string | No | New title |
-| `description` | string | No | New description |
-| `activeForm` | string | No | Present continuous text displayed when in progress |
-| `owner` | string | No | New task owner (agent name) |
-| `metadata` | object | No | Metadata to merge (set to null to delete a key) |
-| `addBlocks` | string[] | No | List of task IDs blocked by this task |
-| `addBlockedBy` | string[] | No | List of prerequisite task IDs blocking this task |
-
-## Status Workflow
-
-```
-pending → in_progress → completed
-```
-
-`deleted` can be entered from any status and permanently removes the task.
-
-## Use Cases
-
-**Good for:**
-- Marking a task as `in_progress` when starting work
-- Marking a task as `completed` when work is done
-- Setting dependencies between tasks
-- Updating task content when requirements change
-
-**Important rules:**
-- Only mark a task as `completed` when it is fully finished
-- Keep the task as `in_progress` when encountering errors or blockers
-- Do not mark as `completed` if tests are failing, implementation is incomplete, or unresolved errors exist
-
-## Notes
-
-- Before updating, retrieve the task's latest status via TaskGet to avoid stale data
-- After completing a task, call TaskList to find the next available task
-
-## Original Text
-
-<textarea readonly>Use this tool to update a task in the task list.
-
-## When to Use This Tool
-
-**Mark tasks as resolved:**
-- When you have completed the work described in a task
-- When a task is no longer needed or has been superseded
-- IMPORTANT: Always mark your assigned tasks as resolved when you finish them
-- After resolving, call TaskList to find your next task
-
-- ONLY mark a task as completed when you have FULLY accomplished it
-- If you encounter errors, blockers, or cannot finish, keep the task as in_progress
-- When blocked, create a new task describing what needs to be resolved
-- Never mark a task as completed if:
-  - Tests are failing
-  - Implementation is partial
-  - You encountered unresolved errors
-  - You couldn't find necessary files or dependencies
-
-**Delete tasks:**
-- When a task is no longer relevant or was created in error
-- Setting status to `deleted` permanently removes the task
-
-**Update task details:**
-- When requirements change or become clearer
-- When establishing dependencies between tasks
-
-## Fields You Can Update
-
-- **status**: The task status (see Status Workflow below)
-- **subject**: Change the task title (imperative form, e.g., "Run tests")
-- **description**: Change the task description
-- **activeForm**: Present continuous form shown in spinner when in_progress (e.g., "Running tests")
-- **owner**: Change the task owner (agent name)
-- **metadata**: Merge metadata keys into the task (set a key to null to delete it)
-- **addBlocks**: Mark tasks that cannot start until this one completes
-- **addBlockedBy**: Mark tasks that must complete before this one can start
-
-## Status Workflow
-
-Status progresses: `pending` → `in_progress` → `completed`
-
-Use `deleted` to permanently remove a task.
-
-## Staleness
-
-Make sure to read a task's latest state using `TaskGet` before updating it.
-
-## Examples
-
-Mark task as in progress when starting work:
-```json
-{"taskId": "1", "status": "in_progress"}
-```
-
-Mark task as completed after finishing work:
-```json
-{"taskId": "1", "status": "completed"}
-```
-
-Delete a task:
-```json
-{"taskId": "1", "status": "deleted"}
-```
-
-Claim a task by setting owner:
-```json
-{"taskId": "1", "owner": "my-name"}
-```
-
-Set up task dependencies:
-```json
-{"taskId": "2", "addBlockedBy": ["1"]}
-```
-</textarea>

package/concepts/en/Tool-TeamCreate.md

@@ -1,38 +0,0 @@
-# TeamCreate
-
-## Definition
-
-Creates a new team to coordinate multiple agents working on a project. Teams enable parallel task execution through a shared task list and inter-agent messaging.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `team_name` | string | Yes | Name for the new team |
-| `description` | string | No | Team description/purpose |
-| `agent_type` | string | No | Type/role of the team lead |
-
-## What It Creates
-
-- **Team config file**: `~/.claude/teams/{team-name}/config.json` — stores member list and metadata
-- **Task list directory**: `~/.claude/tasks/{team-name}/` — shared task list for all teammates
-
-Teams have a 1:1 correspondence with task lists.
-
-## Team Workflow
-
-1. **TeamCreate** — create the team and its task list
-2. **TaskCreate** — define tasks for the team
-3. **Agent** (with `team_name` + `name`) — spawn teammates that join the team
-4. **TaskUpdate** — assign tasks to teammates via `owner`
-5. Teammates work on tasks, communicate via **SendMessage**
-6. **Shutdown** teammates when done, then **TeamDelete** to clean up
-
-## Related Tools
-
-| Tool | Purpose |
-|------|---------|
-| `TeamDelete` | Remove team and task directories |
-| `SendMessage` | Inter-agent communication within the team |
-| `TaskCreate` / `TaskUpdate` / `TaskList` / `TaskGet` | Manage the shared task list |
-| `Agent` | Spawn teammates that join the team |

package/concepts/en/Tool-TeamDelete.md

@@ -1,30 +0,0 @@
-# TeamDelete
-
-## Definition
-
-Removes a team and its associated task directories when multi-agent collaboration work is complete. This is the cleanup counterpart to TeamCreate.
-
-## Behavior
-
-- Removes the team directory: `~/.claude/teams/{team-name}/`
-- Removes the task directory: `~/.claude/tasks/{team-name}/`
-- Clears team context from the current session
-
-**Important**: TeamDelete will fail if the team still has active members. Teammates must be gracefully shut down first via SendMessage shutdown requests.
-
-## Typical Usage
-
-TeamDelete is called at the end of a team workflow:
-
-1. All tasks are completed
-2. Teammates are shut down via `SendMessage` with `shutdown_request`
-3. **TeamDelete** removes team and task directories
-
-## Related Tools
-
-| Tool | Purpose |
-|------|---------|
-| `TeamCreate` | Create a new team and its task list |
-| `SendMessage` | Communicate with teammates / send shutdown requests |
-| `TaskCreate` / `TaskUpdate` / `TaskList` / `TaskGet` | Manage the shared task list |
-| `Agent` | Spawn teammates that join the team |

package/concepts/en/Tool-WebFetch.md

@@ -1,55 +0,0 @@
-# WebFetch
-
-## Definition
-
-Fetches web page content from a specified URL, converts HTML to markdown, and processes the content using an AI model based on the prompt.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `url` | string (URI) | Yes | The full URL to fetch |
-| `prompt` | string | Yes | Describes what information to extract from the page |
-
-## Use Cases
-
-**Good for:**
-- Fetching content from public web pages
-- Consulting online documentation
-- Extracting specific information from web pages
-
-**Not good for:**
-- URLs requiring authentication (Google Docs, Confluence, Jira, GitHub, etc.) — look for a dedicated MCP tool first
-- GitHub URLs — prefer using the `gh` CLI
-
-## Notes
-
-- The URL must be a complete, valid URL
-- HTTP is automatically upgraded to HTTPS
-- Results may be summarized if the content is too large
-- Includes a 15-minute self-cleaning cache
-- When a URL redirects to a different host, the tool returns the redirect URL, and you need to re-request with the new URL
-- If an MCP-provided web fetch tool is available, prefer using that one
-
-## Original Text
-
-<textarea readonly>IMPORTANT: WebFetch WILL FAIL for authenticated or private URLs. Before using this tool, check if the URL points to an authenticated service (e.g. Google Docs, Confluence, Jira, GitHub). If so, you MUST use ToolSearch first to find a specialized tool that provides authenticated access.
-
-- Fetches content from a specified URL and processes it using an AI model
-- Takes a URL and a prompt as input
-- Fetches the URL content, converts HTML to markdown
-- Processes the content with the prompt using a small, fast model
-- Returns the model's response about the content
-- Use this tool when you need to retrieve and analyze web content
-
-Usage notes:
-  - IMPORTANT: If an MCP-provided web fetch tool is available, prefer using that tool instead of this one, as it may have fewer restrictions.
-  - The URL must be a fully-formed valid URL
-  - HTTP URLs will be automatically upgraded to HTTPS
-  - The prompt should describe what information you want to extract from the page
-  - This tool is read-only and does not modify any files
-  - Results may be summarized if the content is very large
-  - Includes a self-cleaning 15-minute cache for faster responses when repeatedly accessing the same URL
-  - When a URL redirects to a different host, the tool will inform you and provide the redirect URL in a special format. You should then make a new WebFetch request with the redirect URL to fetch the content.
-  - For GitHub URLs, prefer using the gh CLI via Bash instead (e.g., gh pr view, gh issue view, gh api).
-</textarea>