TypingMindTypingMindThe best frontend for AI
Discussion logo

Discussion

Organization
greenfield-inc
discussion

Have an interactive discussion about a topic, approach, feature, or bug without making code changes. Researches the codebase as needed and talks through options. Use to think through an approach before planning or coding.

Overview

Publishergreenfield-inc
RepositoryPane
Skill namediscussion
Stars
529
Forks
227
Bundled files
Instructions only
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by greenfield-inc on GitHub. Read the source before you install it.

Installation

Install the Discussion AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/greenfield-inc/Pane/tree/main/main/src/services/paneChatBundle/skills/discussion
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/greenfield-inc/Pane.git /tmp/Pane
mkdir -p .claude/skills
cp -r /tmp/Pane/main/src/services/paneChatBundle/skills/discussion .claude/skills/discussion
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Discussion in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Discussion on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Discussion is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Discussion

Topic: $ARGUMENTS

Talk the topic through with the user, back and forth, until the ideas, tradeoffs, and goal are clear enough to plan or build.

Conversation only

Read code and research freely. Your only output is conversation. Never edit, create, or delete project files, and never propose diffs or patches to apply.

1. Research as needed

  • Clarify the topic and the outcome the user wants.
  • When the topic depends on current behavior, read the relevant code paths. Use the explorer subagent or codebase-explorer for code, and research-web for external libraries or approaches, including mid-conversation when new questions come up.
  • Research only what the conversation needs.

2. Discuss with the user

  • Apply the rewrite-simply skill to every discussion response before you send it.
  • Present findings, first thoughts, concrete options, constraints, and tradeoffs.
  • Ask targeted questions about preferences, constraints, and goals.
  • Be opinionated. Recommend with reasons, separate fact from recommendation, and defer to the user's judgment.

Prototype before you ask

Classify every fork question before you raise it. If running something can answer it (behavior, timing, output, performance, layout), build the cheapest throwaway probe outside the project tree, run it, and present the result with a recommendation. Save questions for product or preference calls that no experiment can settle. A probe usually answers faster than a person, and it gives them a result to react to.

3. Hand off and suggest next steps

Recap in the conversation:

  • the trigger and why it matters
  • the desired outcome
  • constraints and non-goals
  • decisions and open questions
  • available source references

Mark which points are the user's intent and which are your assumptions. Then recommend the next step, usually create-ticket when the work is ready to delegate, options when more than one approach is live, brief for a write-up, investigate for a bug, or implementation.

Suggested next steps:
- `/create-ticket [description]` - Capture the work for delegation
- `/options [question]` - Lay out the approaches and trade-offs
- `/discussion [follow-up]` - Continue exploring a specific aspect
- `/research-web [topic]` - Look up external documentation

Topic to discuss: $ARGUMENTS

Frequently asked questions

What does the Discussion AI skill do?

Have an interactive discussion about a topic, approach, feature, or bug without making code changes. Researches the codebase as needed and talks through options. Use to think through an approach before planning or coding.

Why use Discussion on TypingMind?

Because you install it once and use it with any model. Discussion is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Discussion in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/greenfield-inc/Pane/tree/main/main/src/services/paneChatBundle/skills/discussion. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Discussion?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Discussion?

As many as you like. As long as a model supports skills, you can use Discussion with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Discussion AI skill free?

It is published on GitHub by greenfield-inc. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
openclaw logo

Openclaw Live Updater

openclaw
OrganizationPopular

Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation. Use for fast-forward update…

82.2K
391K
2 files
View
openclaw logo

Openclaw Pr Maintainer

openclaw
OrganizationPopular

Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

82.2K
391K
5 files
View
openclaw logo

Openclaw Refactor Docs

openclaw
OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

82.2K
391K
Instructions
View
openclaw logo

Openclaw Repair Sweep

openclaw
OrganizationPopular

Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

82.2K
391K
1 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇