ls-communication-and-tools

Guide agent communication and tool selection within Localsetup projects.

3|2|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/CruxExperts/localsetup --skill ls-communication-and-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ls-communication-and-tools
Source: https://github.com/CruxExperts/localsetup/tree/main/_localsetup/skills/ls-communication-and-tools
Command: npx skills add https://github.com/CruxExperts/localsetup --skill ls-communication-and-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides how to communicate effectively and select and enhance tools, with periodic context updates to maintain aligned agent behavior within the Localsetup environment.

Core Features & Use Cases

  • Communication and response guidelines: Planning mode by default; concise, factual, output structure; use clickable links; provide options and wait for confirmation; guarantee capability-aware formatting.
  • Tool selection and enhancement: Prefer native, project-local tools; detect available tools before suggesting new ones; use vetted tools; avoid overwriting defaults; annotation about context updates.
  • Periodic environment monitoring and MCP focus: Regular context refresh cadence; monitor tool availability; maintain auditable context for workflows.

Quick Start

Describe your goal and I will respond with concise, guideline-driven communication and tool recommendations.

Frequently Asked Questions about ls-communication-and-tools

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

FAQPage Schema
How do I improve agent communication and tool selection in coding projects?

Agent communication and tool selection improve by enforcing planning mode, concise factual output, and native tool detection before suggesting new tools. This maintains safe, auditable interactions within your project context.

What is the best way to manage context updates for agent workflows?

Context updates for agent workflows are managed through a regular refresh cadence that monitors tool availability. This periodic environment monitoring maintains aligned agent behavior and auditable context.

How do coding assistants detect native tools before suggesting external ones?

Coding assistants detect native tools by scanning the project-local environment before recommending external options. This vetted tool selection avoids overwriting defaults and ensures capability-aware output formatting.

Can I enforce capability-aware output formatting for assistant interactions?

Capability-aware output formatting is enforced by applying communication guidelines that structure responses concisely. This guarantees safe interactions by providing clickable links and waiting for user confirmation.

Why does an agent overwrite default tools instead of using project-local ones?

An agent overwrites default tools when context refresh cadence fails to detect available native tools. Applying tool selection guidelines prevents this by prioritizing vetted, project-local tools over external suggestions.

Does agent communication require planning mode by default?

Agent communication requires planning mode by default to ensure structured, concise, and factual responses. This guideline-driven approach provides options and waits for confirmation before executing actions.