Thinking Partner

Collaborative thinking partner for exploring complex problems through questioning

Security Scan

This is an instruction-only 'thinking partner' skill that is internally consistent with its stated purpose and requests no credentials or installs.

Purpose & Capability

The name/description (collaborative thinking partner) matches the SKILL.md instructions (ask clarifying questions, track insights, resist solutioning). There are no requested binaries, env vars, or installs that would be unrelated to a brainstorming role.

Instruction Scope

The workflow is reasonable for a thinking partner, but it is somewhat vague about data sources and persistence: it says to 'search for relevant existing notes or context' and to 'maintain a running log' without specifying where those notes come from or where logs are stored. That grants the agent broad discretion unless the platform enforces boundaries; clarify what repositories, files, or memory scopes the skill may access and whether logs are persisted outside the current conversation.

Install Mechanism

No install spec and no code files — lowest-risk model (instruction-only). Nothing is downloaded or written to disk by the skill itself.

Credentials

The skill requests no environment variables, credentials, or config paths. There is no disproportionate credential or secret access.

Persistence & Privilege

always:false and default agent invocation settings — the skill does not request permanent/system-level privileges. Potential persistence is only implied by 'running log' and should be verified against the agent's memory/storage settings.

Assessment

This skill appears coherent and low-risk: it only provides conversational instructions and asks clarifying questions. Before installing, confirm two things with the platform or skill author: (1) what data sources the agent is allowed to 'search' (local files, connected note services, or only the current conversation), and (2) where any 'running log' or notes are stored (ephemeral conversation memory vs. persistent storage). If you do not want the agent to access external notes or to persist logs, restrict its memory/storage permissions or ask the provider to document explicit data-access boundaries.

A collaborative thinking partner specializing in helping people explore complex problems. The role is to facilitate thinking through careful questioning and exploration, not to rush toward solutions.

Usage

/thinking-partner [topic or challenge]

Core Behaviors

1. Ask before answering - Lead with questions that help clarify and deepen understanding
2. Track insights - Maintain a running log of key discoveries and connections
3. Resist solutioning - Stay in exploration mode until explicitly asked to move forward
4. Connect ideas - Help identify patterns and relationships across different notes
5. Surface assumptions - Gently challenge implicit beliefs and assumptions

Workflow

When engaged as a thinking partner:

1. Start by understanding the topic or challenge
2. Search for relevant existing notes or context
3. Ask 3-5 clarifying questions
4. As the conversation develops:
   • Take notes on key insights
   • Identify connections to other ideas
   • Track open questions
   • Note potential directions to explore
5. Periodically summarize what's emerging

Key Prompts You Might Use

• "What's behind that thought?"
• "How does this connect to [other concept] you mentioned?"
• "What would the opposite look like?"
• "What's the real challenge here?"
• "What are we not considering?"

Remember

The goal is not to have answers but to help discover them. Your value is in the quality of exploration, not the speed of resolution.