btw

Answer side questions using only existing conversation context.

1.0k|92|Updated May 22, 2026
One-click install
npx skills add https://github.com/open-gsd/gsd-pi --skill btw-open-gsd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: btw
Source: https://github.com/open-gsd/gsd-pi/tree/main/src/resources/skills/btw
Command: npx skills add https://github.com/open-gsd/gsd-pi --skill btw-open-gsd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly answer questions using only what has already occurred in the conversation context, without reading files or running tools.

Core Features & Use Cases

  • Context-bound answers derived solely from the current session.
  • No tool execution or external lookups, ensuring safety and speed.
  • Use Case: when you need a quick clarification from prior decisions or discussed details without interrupting the main task.

Quick Start

Parse the argument after /btw as the question and answer it directly from the current conversation context.

Frequently Asked Questions about btw

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

FAQPage Schema
How do I answer quick side questions using only the current conversation context?

You can answer quick side questions using conversation context by parsing the question and generating a succinct response derived solely from existing session messages. It returns a single concise answer without executing external lookups or tools.

Can I get a quick clarification from prior decisions without interrupting the main session?

Yes, you can get quick clarifications from prior decisions without interrupting your main session. The system answers directly from established conversation context, enforcing no file reads or command execution to ensure safety and speed.

Does a no-tools context-bound answer prevent file reads and command execution?

Yes, a no-tools context-bound answer strictly prevents file reads, command execution, and external tool calls. It uses only the information already present in the current conversation session to return a safe and immediate response.

What should I do if the conversation context is insufficient to answer my side question?

If the conversation context is insufficient to answer your side question, you should rephrase your input as a normal prompt. This allows the system to bypass the context-bound restriction and use standard tools for external lookups.

When do I need a no-tools prompt for quick answers in an ongoing session?

You need a no-tools prompt for quick answers in an ongoing session when you want a fast clarification from discussed details without triggering file reads or command execution. It ensures immediate responses based solely on prior conversation context.

What is the best way to retrieve information already discussed in a conversation without running tools?

The best way to retrieve information already discussed without running tools is to query the existing session context directly. This approach yields a single concise answer derived purely from past messages and decisions, avoiding any external lookups.