Results for “mining”

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see page-cro.

The English summary is being prepared. Showing the original description.

Diagnose OpenClaw problems involving models, providers, tools, and streamed responses. Use targeted logs, repeat the failing operation, and inspect stored conversations and attachments to identify the cause, guide a repair, and verify the result.

• Investigating differences between local tests and live runs
• Checking which tools are actually visible to a model
• Diagnosing delayed or stalled streamed responses

Investigate Node.js bugs by pausing execution, examining variables, and stepping through code. Diagnose stalled asynchronous work and unreliable tests, or collect memory snapshots and CPU profiles to investigate growing memory use and slow execution.

• Investigate stalled asynchronous work
• Debug tests that fail inconsistently
• Examine startup timing and child processes

Investigate Python bugs by pausing execution, inspecting variables, and stepping through code. Choose between local debugging with pdb or breakpoint(), exception inspection, and connecting debugpy to remote or already running processes.

• Inspecting variables in a failing Python test
• Tracing unexpected changes to program state
• Examining program state after an exception

Sharpen a plan or design through persistent questioning while creating documentation along the way. The resulting documents include architecture decision records, which capture design choices, and a glossary of terms used in the discussion.

• Sharpening a plan through detailed questions
• Examining a design through an interview
• Documenting design decisions during discussion

Record a website's network traffic in a HAR file, a log of requests and responses, then derive an HTTP client from its JSON requests. Reuse captured request details to run searches or fetch data without repeated browser interaction.

• Building a command-line client for a website
• Repeating searches without browser interaction
• Examining autocomplete or feed requests

Test a plan before implementation through structured, challenging questions. Work through decisions in dependency order, receive recommendations with each question, and finish with a clear account of agreed choices, open issues, and scope.

• Clarifying an idea before implementation
• Testing authentication or payment plans
• Examining failure scenarios and rollback options

Investigate Python bugs by pausing execution, inspecting variables, and stepping through code. Choose pdb for local inspection or debugpy for remote connections, with guidance for failing tests, crash analysis, and already running processes.

• Inspecting variables in a failing test
• Tracing changes to a collection inside a function
• Examining local variables at a crash site

Add two or three specific follow-up questions after actionable advice, plans, estimates, or analysis. The questions help users examine facts, reasoning, and missing context before acting, with clear exclusions and a limit of once per conversation.

• Examining assumptions behind cost or timeline estimates
• Checking reasoning behind a recommended plan
• Spotting missing context in proposals or email drafts

Review a development plan before implementation by challenging its premise, comparing alternative approaches, and examining design, security, testing, and operations. Choose whether to expand, maintain, or reduce scope, then receive a summary of agreed decisions.

• Challenging a plan's purpose and assumptions
• Comparing minimal and ideal approaches
• Deciding whether to expand or reduce scope

Review an implementation plan before coding, checking system structure, data flow, diagrams, edge cases, test coverage, and performance. Discuss issues interactively with concrete recommendations to settle technical decisions before implementation begins.

• Reviewing an implementation plan before coding
• Checking system structure and data flow
• Reviewing edge cases and test coverage

Challenge important design and implementation decisions with a separate reviewer that does not inherit the working session's context. Identify hidden assumptions and failure cases, then assess each finding against the artifact and its requirements.

• Challenging assumptions in an architecture proposal
• Reviewing decisions in unfamiliar code
• Checking authentication or security-sensitive logic

Build a narrative project history from records stored in claude-mem. The report traces architectural changes, breakthroughs, debugging efforts, and work patterns, with timeline statistics and estimates of token savings from reusing recorded knowledge.

• Reviewing a project's development history
• Tracing architectural decisions and their consequences
• Examining recurring debugging and work patterns

Retrieve publicly tracked military aircraft positions from OpenSky and Wingbits. Filter by geographic area, operator, or aircraft type, then review callsigns, altitude, aircraft details, and detected groups of activity to understand observed regional air activity.

• Checking tracked military aircraft in a region
• Filtering aircraft by operator
• Reviewing tanker and surveillance aircraft activity

Compare historical consumer prices, interest rates, and government bond yields from stored official reports. Keep source dates, index bases, reporting frequency, yield definitions, and missing observations visible when examining trends across countries.

• Compare inflation trends across countries
• Review US interest rate history
• Examine government bond yield trends and definitions

Check current pressure on shipping markets and supply chains using carrier and freight indicators. Retrieve a combined stress score, its level, and the underlying market inputs to assess whether shipping conditions show signs of disruption.

• Checking current pressure on supply chains
• Reviewing overall container shipping stress
• Examining market inputs behind a stress score

Fetch execution traces, records of an agent’s actions, from LangSmith Studio to debug LangChain and LangGraph agents. Inspect errors, tool calls, memory operations, execution times, and token usage, or export records for further review.

• Investigating an agent failure
• Checking tool selection and execution order
• Investigating memory storage and recall

Turn complex goals into actionable steps by examining requirements, expected effects, and costs. Build a path from the current situation to the desired outcome, then revise the plan when actions fail or conditions change.

• Breaking a complex goal into smaller tasks
• Planning steps around dependencies and costs
• Replanning after failures or changing conditions

Experiment with the policies that govern an AI agent, such as planning, memory, and tool use. Test one policy change per variant in a sandbox, an isolated environment, and promote only candidates with measured improvements.

• Finding policy changes that improve low evaluation scores
• Exploring initial agent settings for a new domain
• Comparing manual tuning with an evolved baseline

Measure performance in the agentic-flow worker system, including trigger detection, agent selection, caching, and concurrent operations. Run a full suite or individual benchmarks to compare response times and resource usage against configured targets.

• Checking overall worker system performance
• Measuring trigger detection and agent selection speed
• Examining cache behavior and memory usage

Store project files and conversation transcripts as searchable memories while preserving their original text. Retrieve past decisions, code, and notes by meaning, inspect stored content, and review how well memories are organized.

• Retrieve past decisions from conversation history
• Make project files searchable by meaning
• Inspect stored memories and their organization

Extract information from a project or conversation and store it as memories in MemPalace for later retrieval. The skill follows the step-by-step mining instructions returned by the MemPalace command.

• Saving information from a project for later reference
• Extracting memories from a conversation
• Following MemPalace’s instructions to store memories

Set up and maintain MemPalace as a searchable store of project and conversation memories. Configure a private installation, a shared hub, or a hub client, connect agent tools, and audit how stored information is organized.

• Setting up a private memory store
• Sharing a memory hub between AI agents
• Connecting Claude or Codex through MCP

Research companies from the terminal using a domain name. Intelwatch combines financial data and technology stack detection into readable company profiles, with an optional AI due diligence mode for examining potential acquisition targets.

• Researching competitors from their company domains
• Preparing company background information for sales
• Running AI due diligence on acquisition candidates