company-research-workflow-planner
Skill9 starsChanged 5 months agoMITView on GitHub
Creates a repeatable process for researching and comparing companies. Use when the user wants a structured, reusable company-research workflow with objectives, sources, fields, and validation.
In this repository23 other files it gives its agents.
- account-prioritizationSkill
- b2b-lead-qualificationSkill
- candidate-qualificationSkill
- company-data-normalizationSkill
- company-researchSkill
- 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
- partner-qualificationSkill
- 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
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 20
Create a repeatable process for researching and comparing companies.
- Distinctive: line 50
Keep the output structure consistent.
≈ “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
Company Research Workflow Planner
Purpose
Create a repeatable process for researching and comparing companies.
When to use this skill
- Standardizing company research across a team
- Building a repeatable account-research playbook
- Defining the fields every profile needs
- Setting completion criteria for research tasks
When not to use this skill
- You want one company researched now (use Company Research)
- You have no research objective
- You need the research executed, not planned
Required inputs
- A research objective
Optional inputs
- Required output fields
- Approved sources
- A comparison framework
Rules
- Define explicit required fields and completion criteria.
- Sequence research logically.
- Include validation steps.
- Keep the output structure consistent.
- Note assumptions where objectives are broad.
Process
- Parse the research objective.
- Define sources and required fields.
- Order the research sequence.
- Add validation steps.
- Define output structure and completion criteria.
Output format
Return a research process with the following fields:
- research_objectives
- source_types
- required_fields
- research_sequence
- validation_steps
- output_structure
- completion_criteria
Validation
- Confirm required fields cover the objective.
- Confirm validation steps are present.
- Confirm completion criteria are testable.
Limitations
- A process is only as good as the sources it uses.
- Completion criteria may need tuning over time.
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.

