asb-carol-strengths

Distills raw company observations into classified strength and weakness attributes in a markdown chart.

Updated Nov 15, 2025
One-click install
npx skills add https://github.com/evanish/reusable-PM-templates --skill asb-carol-strengths-evanish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asb-carol-strengths
Source: https://github.com/evanish/reusable-PM-templates/tree/main/Templates%20to%20reuse/Work/asb-customer-discovery/asb-carol-strengths
Command: npx skills add https://github.com/evanish/reusable-PM-templates --skill asb-carol-strengths-evanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product and strategy teams collect honest observations about their company but struggle to turn that raw evidence into a short, actionable list of real strengths and weaknesses. This Skill guides the distillation step of an ideal-customer-profile (ICP) method, converting an observations file into a classified STRENGTHS-WEAKNESSES.md chart. ## Core Features & Use Cases - Evidence-based distillation: Proposes one attribute at a time, each citing its supporting observations (O1, O2, ...), and merges observations pointing at the same underlying truth. - Opposite Test gate: Rejects generic attributes like "great customer service" unless worded specifically enough that a competitor could rationally claim the opposite. - Classification rubric: Classifies each attribute as strength, weakness, both (a flagged strategic choice), or a cut, using market-perception and buy/refuse-for-this-alone criteria. - Use Case: After running an honest-look exercise that produced OBSERVATIONS.md with 30 numbered observations about your product, use this Skill to distill them into 4-8 strengths and a similar count of weaknesses, recorded in STRENGTHS-WEAKNESSES.md for the later keystones step. ## Quick Start Read my OBSERVATIONS.md file and distill the observations into classified strengths and weaknesses, one attribute at a time.

Frequently Asked Questions about asb-carol-strengths

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

FAQPage Schema
How do I turn customer observations into strengths and weaknesses?

Provide a numbered observations file and the Skill proposes one candidate attribute at a time with its supporting observation citations. Each attribute passes an Opposite Test for specificity, then is classified as strength, weakness, both, or cut using a market-perception rubric.

What is the Opposite Test for company attributes?

The Opposite Test asks whether any successful company would rationally claim the opposite of your attribute. "Easy to use" fails because nobody claims "difficult to use," while "transparent, simple pricing" passes because enterprise vendors proudly use call-for-pricing models.

Can I use this skill without an observations file?

Distilling from memory is refused because it produces generic charts. The Skill offers to run a prior observation-gathering step or capture a quick in-chat set of observations covering customer praise, indefensible complaints, and best-versus-worst customer differences.

What output file does the strengths and weaknesses analysis produce?

It creates STRENGTHS-WEAKNESSES.md in the same directory as the input, containing numbered strengths (S1, S2), weaknesses (W1, W2), a cuts list with reasoning, and parked notes for downstream steps like keystones and deal-breakers.

When should an attribute be classified as both strength and weakness?

Classify as both when different market segments disagree, such as "one hundred features" being completeness to some buyers and bloat to others. Both-attributes are flagged as pending strategic choices rather than collapsed into one column.