qualify

What This Skill Does

The Qualify skill is designed to act as an objective filter for decision-making. In any business or project-based environment, resources are finite. This skill prevents the common pitfall of "sunk cost fallacy" by establishing rigorous criteria at the start of an engagement. It transforms subjective intuition into an explicit, repeatable framework. By utilizing this skill, you can systematically define what a 'qualified' lead, project, or candidate looks like, ensuring that your team's energy is directed exclusively toward high-value, high-fit opportunities. The skill focuses on four core pillars: identifying genuine product-market fit, assessing current readiness, measuring potential value against expected resource expenditure, and documenting clear disqualifiers that act as 'stop-signs' early in the process.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal or dashboard:

clawhub install openclaw/skills/skills/agimodel/qualify

Ensure that your OpenClaw runtime has the necessary permissions if you plan to use this skill to analyze local files or interact with external CRM APIs.

Use Cases

• Sales Pipeline Optimization: Quickly filter out leads that do not match your ideal customer profile (ICP) before wasting valuable hours on discovery calls.
• Hiring & Talent Acquisition: Create a standardized scorecard for reviewing resumes or interview performance, reducing unconscious bias and ensuring a better culture fit.
• Project Intake: Evaluate incoming client requests against your firm's current capacity, expertise, and target revenue margins to decide whether to accept or decline the work.
• Go/No-Go Decisioning: Establish strict gatekeeping logic for new product initiatives or market expansion efforts to prevent "scope creep" before the work begins.

Example Prompts

1. "I am receiving too many unqualified inbound sales inquiries. Can you help me build a qualification scorecard that filters out anyone without a clear budget and decision-making authority?"
2. "We have five potential projects for Q4, but we only have capacity for two. Can you help me define a go/no-go logic framework based on profit margins and team expertise?"
3. "What are some common disqualifiers I should look for when screening candidates for a senior engineering role to ensure we aren't wasting time on candidates who aren't a fit?"

Tips & Limitations

• Be Explicit: The accuracy of the Qualify skill depends on the quality of your inputs. The more precise your internal business requirements, the better the logic framework it will generate.
• Avoid Over-Engineering: Qualification should be a tool for speed, not a bureaucracy. Use the scorecard to highlight obvious red flags rather than creating 50-point checklists that slow down your intake process.
• Regular Audits: Market conditions change. Review your qualification criteria every quarter to ensure you aren't filtering out opportunities that have become viable due to shifts in your business goals.
• Human-in-the-loop: Use this skill to inform your judgment, not replace it. Use the generated outputs to facilitate better conversations with your team or stakeholders.