Skip to content
Back to skills

Who Our Good Customers Look Like

ASecurity

Use whenever you are picking, sorting, scoring or cutting companies — enriching a list, qualifying an inbound lead, researching before a call, deciding who to chase. Read this before you decide who is worth someone's time, so the answer comes back sorted by who to call rather than alphabetically.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsgo

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add alfera-labs/company-use --skill who-our-good-customers-look-like --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Who Our Good Customers Look Like?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Who Our Good Customers Look Like
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/alfera-labs-who-our-good-customers-look-like/badge)](https://www.skillsdirectory.com/skills/alfera-labs-who-our-good-customers-look-like)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: who-our-good-customers-look-like
description: Use whenever you are picking, sorting, scoring or cutting companies — enriching a list, qualifying an inbound lead, researching before a call, deciding who to chase. Read this before you decide who is worth someone's time, so the answer comes back sorted by who to call rather than alphabetically.
license: Apache-2.0
compatibility: ">=1.0"
metadata:
  display_name: Who our good customers look like
  author: Alfera
  triggers:
    - which of these are worth calling
    - enrich this list
    - is this a good fit
    - should we chase this one
---

# Who our good customers look like

This is the workspace's own definition of a good customer. Fill it in once; every job that
touches companies gets sharper.

## Fill this in

Replace each line. Keep it short — this gets read on every relevant turn, so length costs you.

```
Best fit          <size band> · <what makes them ours> · <where>
Signs off         <the two or three titles who actually decide>
Worth a call when <the events that mean now, not someday>
Not for us        <who to cut, and the one-line reason>
```

`references/filled-example.md` has one filled in, to copy the shape from.

## How to use it

- When you rank a list, rank by fit against **Best fit**, not by size and not alphabetically.
- When you cut something, say which **Not for us** line cut it. A cut without a reason reads as a
  mistake and someone will put it back.
- When you write a "why now", prefer the events under **Worth a call when**. Anything else is a
  fact about the company, not a reason to call it.
- When a company matches nothing here, say so plainly rather than stretching a match.

## The part people skip

**Not for us** does most of the work. Knowing who you are not for is what stops a list being
noise. Write at least two lines there, each with the reason — "under 50 staff: nobody owns the
process yet" is useful; "too small" is not.

Files in this skill

  • SKILL.md1.9 KB
  • alfera.json1.8 KB
  • references/filled-example.md994 B
  • references/signals.md961 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.