agentleFS
spiralcrew-ouspiralcrew-ou/profilespider-agent-skills/account-prioritization/SKILL.md

account-prioritization

Skill9 starsChanged 5 months agoMITView on GitHub

Ranks companies or accounts by strategic relevance and opportunity. Use when the user provides accounts and wants a priority score, tier, rationale, risks, and next action.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use evidence; do not invent intent or growth signals.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Account Prioritization

Purpose

Rank companies or accounts by strategic relevance and opportunity with a clear rationale.

When to use this skill

  • Sequencing outreach across many accounts
  • Building tiered account lists
  • Focusing limited capacity on the best opportunities
  • Justifying account priority to a team

When not to use this skill

  • Accounts are not yet qualified for fit
  • You have no relevance or opportunity signal
  • You need contact-level routing (use Persona Classification)

Required inputs

  • A set of accounts
  • Prioritization criteria

Optional inputs

  • Opportunity signals (intent, growth)
  • Strategic weighting
  • Capacity constraints

Rules

  1. Rank against the supplied criteria and signals.
  2. Use evidence; do not invent intent or growth signals.
  3. Make tiers consistent with scores.
  4. Flag risks that temper the priority.
  5. Recommend a concrete next action.

Process

  1. Parse prioritization criteria and signals.
  2. Score each account for relevance and opportunity.
  3. Assign a tier.
  4. Explain rationale and risks.
  5. Recommend a next action.

Output format

Return one record per account with the following fields:

  • priority_score
  • priority_tier
  • supporting_evidence
  • opportunity_rationale
  • risks
  • next_action

Validation

  • Confirm tiers follow from scores.
  • Confirm evidence supports each priority.
  • Confirm signals were not invented.

Limitations

  • Priority reflects available signal, not guaranteed outcomes.
  • Stale signals can mislead; refresh before acting.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.