agentleFS
dev810vmdev810vm/claude-skills/company-intel/SKILL.md

company-intel

Skill0 starsChanged 8 months agoLicence not identifiedView on GitHub

This skill should be used when the user wants to "research a company for a job application", "find out what to mention in my cover letter", "what should I say about the company in my resume", "tailor my application to this company", "what does this company care about", "research before applying", "what should I know about this company before applying", or provides a job description and wants company-specific talking points for their cover letter or resume. Use this skill whenever the goal is to surface company intelligence that makes an application more targeted and specific.

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use positioning-workshop, proto-persona and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nandanosqlSkill

    positioning-workshop

    Facilitate a guided positioning session that walks through target customer, problem, category, benefit, and differentiation using April Dunford's methodology with adaptive questions.

    Also in 4 projects that use this

  • nandanosqlSkill

    proto-persona

    Create hypothesis-driven user personas before doing full research. Uses behavioral attributes, goals, and frustrations to model target users quickly for early-stage alignment.

    Also in 3 projects that use this

  • Dragoon0xSkill

    roadmap-planning

    Build and communicate a product roadmap that balances customer needs, business goals, and team capacity. Covers outcome-driven planning, stakeholder communication, and roadmap hygiene. Use when planning quarters, aligning stakeholders on direction, or when the roadmap feels like a feature wishlist.

    Also in 3 projects that use this

  • huntsyeaSkill

    jobs-to-be-done

    Applies Bob Moesta's demand-side thinking and Jobs-to-be-Done framework to help product teams understand why customers switch, hire, and fire products. Use when conducting switch interviews, drawing forces diagrams, writing job statements, mapping demand timelines, understanding the struggling moment, analyzing why customers hire or fire your product, exploring passive or active looking behavior, researching JTBD, or when user mentions Bob Moesta, demand-side thinking, big hire, little hire, push/pull/anxiety/habit, or the four forces of progress.

    Also in 3 projects that use this

  • +4 more from nandanosql

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.