tech-qa

Answer technical questions with cited explanations from authoritative sources.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gawashi/dotfiles --skill tech-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-qa
Source: https://github.com/gawashi/dotfiles/tree/main/.claude/skills/tech-qa
Command: npx skills add https://github.com/gawashi/dotfiles --skill tech-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Answers technical questions with live research from authoritative sources. Always leads with the answer and cites sources.

Core Features & Use Cases

  • Live research from authoritative sources to provide accurate explanations.
  • Built-in deferral rules to avoid giving project-specific guidance or debugging steps.
  • Clear, cited reasoning suitable for learning concepts, APIs, and architecture.

Quick Start

Ask a technical question to get a sourced, concise explanation.

Frequently Asked Questions about tech-qa

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

FAQPage Schema
How do I get cited explanations for technical questions about APIs?

To get cited explanations for APIs, you ask a technical question and receive a sourced answer researched from authoritative sources. The explanation leads with the answer and includes live-source citations for verification.

What is the best way to understand how a specific library or tool works in isolation?

The best way to understand how a library or tool works in isolation is to request a concept-definition explanation. The system researches authoritative sources to deliver structured reasoning about the mechanism and provides citations.

Can I use this to get debugging steps and project-specific guidance for my codebase?

No, you cannot use this to get debugging steps or project-specific guidance. Built-in deferral rules strictly avoid project-specific guidance, limiting responses to general explanations of how things work, what concepts mean, or how to use APIs.

Does the technical explanation include sources for verifying architecture concepts?

Yes, the technical explanation includes sources for verifying architecture concepts. It satisfies requirements for live-source citations, ensuring that every explanation of architecture or concepts is backed by authoritative references.

When should I avoid using a research-backed tech explanation tool?

You should avoid using a research-backed tech explanation tool when you need debugging steps, project-specific guidance, or implementation help within your own codebase. Strict deferral rules limit the scope to general concepts and isolated API usage.