query

Filter the aweek agent roster by role, keyword, status, and budget to return matching agent slugs.

11|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/runbear-io/aweek --skill query-runbear-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: query
Source: https://github.com/runbear-io/aweek/tree/main/skills/query
Command: npx skills add https://github.com/runbear-io/aweek --skill query-runbear-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Slug-returning filter over the aweek agent roster. Use this skill any time a request names a subset of agents rather than a single one — e.g. 'the active marketers', 'every paused researcher', 'agents whose persona mentions X.com'. Reads identity (name, description, system prompt) live from .claude/agents/<slug>.md, and lifecycle state from the existing stores; never mutates anything.

Core Features & Use Cases

  • Flexible filtering by role, keyword, status, and budget; supports combined queries to narrow the roster.
  • Live identity and lifecycle data read from agent store; downstream skills receive agent ids for further processing.
  • Read-only operation with clear, deterministic outputs suitable for auditing and automation.

Quick Start

Provide your desired filters (role, keyword, status, budget) and run the skill to retrieve matching agent slugs.

Frequently Asked Questions about query

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I filter my agent roster by role and status without modifying data?

Filter agents by role, keyword, status, and budget using a read-only query skill that reads live identity data from .claude/agents/<slug>.md. It returns matching agent slugs without mutating any data.

What is the best way to retrieve a compact list of agent ids for downstream automation?

Producing a compact list of agent ids for downstream automation requires a slug-returning filter over the agent roster. The query skill applies combined filters for role, keyword, status, and budget to produce deterministic outputs suitable for auditing.

Can I search agent personas and system prompts for specific keywords?

You can search agent personas and system prompts for specific keywords. The query skill reads live identity data including name, description, and system prompt from .claude/agents/<slug>.md to filter the roster by keyword.

How do I identify paused researchers or active marketers from my agent store?

Identifying paused researchers or active marketers requires filtering the agent roster by status and role. The query skill reads lifecycle state from existing stores and live identity data to return matching agent slugs for these subsets.

Are there limitations when using combined filters for agent queries?

Limitations when using combined filters for agent queries include strict read-only operation that never mutates data. The query skill reads live identity and lifecycle data to produce deterministic outputs but does not modify the agent store.