using-sales

Route ambiguous sales requests to the narrowest applicable child skill.

28|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/labs21-dev/agents-stack --skill using-sales-labs21-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-sales
Source: https://github.com/labs21-dev/agents-stack/tree/main/skills-optional/using-sales
Command: npx skills add https://github.com/labs21-dev/agents-stack --skill using-sales-labs21-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Route ambiguous sales requests to the narrowest applicable child skill to ensure precise outputs.

Core Features & Use Cases

  • Router output to the most specific sales child skill (sales-call-prep, sales-draft-outreach, account-research)
  • Install missing child skills automatically when needed
  • Enforce frontmatter, metadata, and reference consistency with references/children.json
  • Provide guidance on when to route to a given child vs. execute standalone

Quick Start

Route the user's request to the narrowest applicable child skill and execute that skill.

Frequently Asked Questions about using-sales

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

FAQPage Schema
How do I route ambiguous sales requests to the correct sales workflow?

Routing ambiguous sales requests involves directing the input to the narrowest applicable child skill, such as sales-call-prep or account-research, to ensure precise outputs. The router automatically selects and executes the correct sub-skill.

Can I automate sales outreach and meeting prep without manually selecting a skill?

Yes, you can automate sales outreach and meeting prep without manual selection. The router evaluates the request and automatically invokes the specific child skill needed, handling sales-outreach, meeting prep, and account research.

What happens if a required sales child skill is missing during routing?

If a required sales child skill is missing during routing, the router integrates with the system to automatically install the missing children. This ensures the sales workflow continues without manual intervention.

How does the sales router validate child skills before execution?

The sales router validates child skills by enforcing frontmatter validation and checking child metadata against references/children.json. This ensures reference consistency and accurate routing before execution.

When should I route a request to a child skill versus executing it standalone?

You should route a request to a child skill when the input specifically involves sales-outreach, meeting prep, or account research to ensure precise outputs. Standalone execution is suitable when the task does not match these narrow categories.