New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Slack QA Investigate

by warpdotdev in warpdotdev/oz-skills

Investigate and answer repository questions in read-only mode.

MITAuto-check passed

Install Slack QA Investigate

skills CLI
$ npx skills add warpdotdev/oz-skills --skill slack-qa-investigate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install warpdotdev/oz-skills slack-qa-investigate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/warpdotdev/oz-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/slack-qa-investigate .claude/skills/slack-qa-investigate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
slack-qa-investigate
GitHub stars
825
Token cost
~806 tokens
SKILL.md length
422 words
Files
2
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Investigate and answer repository questions in read-only mode.

  • Works in 5 steps: Understand the question - Clarify scope… → Search broadly - Use semantic search,… → Read deeply - Examine the actual… → …
  • Asked for research-backed answers that require codebase and documentation investigation without making file changes
  • SKILL.md covers Core Principles, Investigation Process and Prohibited Actions (HARD RULES…
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Slack QA Investigate is an agent skill from warpdotdev/oz-skills. Investigate and answer repository questions in read-only mode. Use when asked for research-backed answers that require codebase and documentation investigation without making file changes.

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).

It works with Slack. The licence is MIT.

When your agent uses it

  • Asked for research-backed answers that require codebase and documentation investigation without making file changes

Example prompts

  • “/slack-qa-investigate”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Understand the question - Clarify scope before diving in
  2. Search broadly - Use semantic search, grep, and file glob to find relevant areas
  3. Read deeply - Examine the actual code/config, not just file names
  4. Trace connections - Follow imports, function calls, and references
  5. Synthesize - Combine findings into a clear, accurate answer

What it can do on your machine

Read from SKILL.md and the folder at commit 6c08c49. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Slack QA Investigate loads about 806 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 422 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~806

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from warpdotdev/oz-skills at commit 6c08c49, republished under its MIT licence (© warpdotdev). 422 words, ~806 tokens.

Download SKILL.mdSave it as .claude/skills/slack-qa-investigate/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
slack-qa-investigate
description
Investigate and answer repository questions in read-only mode. Use when asked for research-backed answers that require codebase and documentation investigation without making file changes.
license
MIT

Q&A Investigation Bot

You are a research-focused Q&A assistant. Your role is to thoroughly investigate questions and provide accurate, well-supported answers without modifying any code or files.

Core Principles

Deep Investigation First
  • Never answer from assumptions; always verify through investigation
  • Search the codebase, read relevant files, and trace through logic before responding
  • Cross-reference multiple sources when information could be outdated or ambiguous
  • Follow the chain: if one file references another, read that file too
  • Check tests, docs, and comments for additional context
  • When reading markdown files, READMEs, or docs, look for URLs and references
  • Fetch linked pages (docs, wikis, external references) for fuller context
  • Follow internal links to other repo docs before answering
  • If a doc references an external API/library, fetch those docs too
Use Web Search When Needed
  • Search the web for external libraries, APIs, or tools referenced in the code
  • Fetch official docs when the codebase uses third-party dependencies
  • Use web search if the answer requires knowledge beyond the repo (e.g. "what does this error mean")
  • Prefer authoritative sources: official docs > Stack Overflow > blogs
Read-Only Mode (STRICT)
  • Do NOT create, edit, or delete any files under ANY circumstances
  • Do NOT run commands that modify state (no git commits, no file writes, no installs)
  • Only use read operations: grep, file reads, semantic search, safe shell commands
  • If asked to make code changes, write code, or modify files. Refuse and tell the user you only serve to answer questions
  • Redirect to what you CAN do: investigate, explain, analyze, find patterns
Show full SKILL.md (168 more words)Show less
Answer Quality
  • Cite specific files/lines when referencing code
  • Distinguish between what the code does vs what docs say vs what you infer
  • Acknowledge uncertainty; say "I couldn't find..." rather than guessing
  • Provide concise answers but include enough context to be useful

Investigation Process

  1. Understand the question - Clarify scope before diving in
  2. Search broadly - Use semantic search, grep, and file glob to find relevant areas
  3. Read deeply - Examine the actual code/config, not just file names
  4. Trace connections - Follow imports, function calls, and references
  5. Synthesize - Combine findings into a clear, accurate answer

Prohibited Actions (HARD RULES - NO EXCEPTIONS)

  • create_file, edit_files - NEVER use these tools
  • Any shell command with side effects (write, delete, install, commit)
  • Writing code snippets intended to be applied as changes
  • Providing diffs, patches, or "here's what I would change" responses
  • Making assumptions without verification
  • Answering "I don't know" without first investigating

If a user requests code changes: Refuse politely, remind them you're read-only, and offer to answer questions about the code instead.

© warpdotdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/slack-qa-investigate of warpdotdev/oz-skills.

  • SKILL.md
  • README.md

Open the folder on GitHubat commit 6c08c49

Compare with similar skills

Slack QA Investigate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Slack QA Investigate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Slack QA Investigate this skillwarpdotdev/oz-skills825—~806Automated safety check: PassMIT
Agent Browser CLIvercel-labs/agent-browser44k24 repos~864Automated safety check: PassApache-2.0
Slack GIF Creatoranthropics/skills180k29 repos~2kAutomated safety check: PassApache-2.0
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Electron App Automationvercel-labs/agent-browser44k5 repos~1.7kAutomated safety check: PassApache-2.0
Slack Browser Automationvercel-labs/agent-browser44k1 repos~2.1kAutomated safety check: PassApache-2.0

Similar skills

  • Agent Browser CLI

    vercel-labs/agent-browser

    Official

    Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…

    44k GitHub starsUsed in 24 repos~864 tokens
    Productivity & AutomationAuto-check passed

  • Slack GIF Creator

    anthropics/skills

    Official

    Provides Slack size and frame limits, Python animation helpers and validators for building animated GIFs sized for emoji and messages.

    180k GitHub starsUsed in 29 repos~2k tokens
    Media & CreativeAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Electron App Automation

    vercel-labs/agent-browser

    Official

    Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.

    44k GitHub starsUsed in 5 repos~1.7k tokens
    Productivity & AutomationAuto-check passed

  • Slack Browser Automation

    vercel-labs/agent-browser

    Official

    Drives the Slack web app with the agent-browser CLI to check unread channels, search, read channel details and extract information, with screenshots as evidence.

    44k GitHub starsUsed in 1 repo~2.1k tokens
    Productivity & AutomationAuto-check passed

  • Composio

    ComposioHQ/composio

    Route and complete Composio work across Composio For You and Composio Platform.

    30k GitHub starsUsed in 1 repo~1.7k tokens
    Productivity & AutomationAuto-check passed

More from warpdotdev/oz-skills

All 13 skills in this repo

  • SEO Aeo Audit

    warpdotdev/oz-skills

    Optimize for search engine visibility, ranking, and AI citations.

    825 GitHub stars~4.9k tokensUpdated 1 mo ago
    Auto-check passed

  • Web Accessibility Audit

    warpdotdev/oz-skills

    Audit web applications for WCAG accessibility compliance. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~3.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Webapp Testing

    warpdotdev/oz-skills

    Test local web applications with Playwright. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~914 tokensUpdated 1 mo ago
    Auto-check passed

  • GitHub Bug Report Triage

    warpdotdev/oz-skills

    Triage GitHub bug reports for actionability. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Analysis Artifacts

    warpdotdev/oz-skills

    Generate reproducible analysis artifacts — SQL queries, Python visualizations, and summary tables — as you work through a BigQuery data analysis.

    825 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • CI Fix

    warpdotdev/oz-skills

    Diagnose and fix GitHub Actions CI failures. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~790 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Questions about Slack QA Investigate

What does Slack QA Investigate do?

Investigate and answer repository questions in read-only mode. Slack QA Investigate is an agent skill from warpdotdev/oz-skills. Investigate and answer repository questions in read-only mode.

When should I use Slack QA Investigate?

Slack QA Investigate fits situations like: asked for research-backed answers that require codebase and documentation investigation without making file changes.

How do I install Slack QA Investigate in Claude Code?

Run `npx skills add warpdotdev/oz-skills --skill slack-qa-investigate -a claude-code`. Or copy the skill folder (.agents/skills/slack-qa-investigate in warpdotdev/oz-skills) into .claude/skills/slack-qa-investigate in your project. Claude Code loads it when a task matches its description.

How do I install Slack QA Investigate in Codex?

Run `npx skills add warpdotdev/oz-skills --skill slack-qa-investigate -a codex`. Or copy the skill folder (.agents/skills/slack-qa-investigate in warpdotdev/oz-skills) into .agents/skills/slack-qa-investigate in your project. Codex loads it when a task matches its description.

Can I use Slack QA Investigate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add warpdotdev/oz-skills --skill slack-qa-investigate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/slack-qa-investigate, .gemini/skills/slack-qa-investigate, .github/skills/slack-qa-investigate and .opencode/skills/slack-qa-investigate in your project.

What does Slack QA Investigate need to run?

SKILL.md names no scripts, command-line tools or credentials: Slack QA Investigate is instructions for the agent only.

Does Slack QA Investigate access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Slack QA Investigate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Slack QA Investigate use?

Slack QA Investigate is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Slack QA Investigate use?

About 806 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Slack QA Investigate?

Skills that share tags, products or a category with Slack QA Investigate: Agent Browser CLI (vercel-labs/agent-browser, 44k stars), Slack GIF Creator (anthropics/skills, 180k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars) and Electron App Automation (vercel-labs/agent-browser, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Slack QA Investigate?

warpdotdev (a GitHub organization) maintains it in warpdotdev/oz-skills, which has 825 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on August 15, 2026.

Source: warpdotdev/oz-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.