partner-qualification
Skill9 starsChanged 5 months agoMITView on GitHub
Evaluates potential channel, integration, affiliate, or strategic partners. Use when the user provides partner profiles plus partnership goals and wants fit scoring, partnership type, and outreach priority.
In this repository23 other files it gives its agents.
- account-prioritizationSkill
- b2b-lead-qualificationSkill
- candidate-qualificationSkill
- company-data-normalizationSkill
- company-researchSkill
- company-research-workflow-plannerSkill
- company-segmentationSkill
- competitor-researchSkill
- directory-research-plannerSkill
- duplicate-record-reviewSkill
- job-title-normalizationSkill
- lead-list-analysisSkill
- lead-list-segmentationSkill
- lead-research-workflow-plannerSkill
- market-researchSkill
- outreach-brief-generatorSkill
- persona-classificationSkill
- person-researchSkill
- prospect-list-cleanupSkill
- recruiting-sourcing-plannerSkill
- research-gap-analysisSkill
- supplier-qualificationSkill
- territory-segmentationSkill
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
- Distinctive: line 50
Use evidence from the profiles.
≈ “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.
Files
Partner Qualification
Purpose
Evaluate potential channel, integration, affiliate, or strategic partners against partnership goals.
When to use this skill
- Prioritizing a partner long-list
- Classifying the likely partnership type per candidate
- Surfacing competitive or channel-conflict risks
- Sequencing partnership outreach
When not to use this skill
- You have no partnership goals or target markets defined
- The records lack enough signal to assess fit
- You need contract terms rather than a fit assessment
Required inputs
- Partner profiles
- Partnership goals
- Required capabilities
Optional inputs
- Target markets
- Existing partners to avoid overlap
- Preferred partnership types
Rules
- Score against stated partnership goals only.
- Use evidence from the profiles; do not assume capabilities.
- Flag competitive overlap and channel conflict explicitly.
- Separate facts from strategic assumptions.
- Apply the same framework to every candidate.
Process
- Parse partnership goals and required capabilities.
- Assess each candidate for fit and overlap.
- Classify the most fitting partnership type.
- Estimate strategic value and risks.
- Score fit and assign an outreach priority.
Output format
Return one record per partner with the following fields:
- partner_fit_score
- partnership_type
- strategic_value
- risks
- recommended_outreach_priority
Validation
- Confirm partnership type follows from the evidence.
- Confirm risks include any competitive overlap.
- Confirm priorities are comparable across candidates.
Limitations
- Strategic value is an estimate, not a forecast.
- Partnership fit depends on relationship factors not present in records.
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
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.