agentleFS
Sign inStart free
Himalayas-AppHimalayas-App/himalayas-plugin/skills/manage-company-profile/SKILL.md

manage-company-profile

Skill0 starsChanged 25 days agoMITView on GitHub

Keep an employer's Himalayas company profile accurate and attractive to remote candidates, covering the about text and summary, size, founding year, locations, social links, perks and benefits, and tech stack. Use when the user wants to review, set up or update their company's profile, perks or tech stack on Himalayas.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow himalayas-basics for the shared rules.

    line 8
  2. Very specific:

    Call get_company_profile, get_company_perks and, for comparison, get_company_details with the company's slug (the public view candidates …

    line 13
  3. Distinctive:

    Read the profile back.

    line 23

≈ “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

Manage the company profile

Follow himalayas-basics for the shared rules. These tools need an employer account.

1. Review

Call get_company_profile, get_company_perks and, for comparison, get_company_details with the company's slug (the public view candidates see). Report what is missing or thin: about text, summary, size, founding year, locations, social links, perks and tech stack.

2. Update the profile

update_company_profile changes only the fields you pass: about, summary, ceo, num_employees_range, year_founded, location_list and social links. Draft new text, show it, and write after the user confirms. Read the profile back.

3. Perks

  • add_company_perk adds a perk with a title and a category from the fixed list (healthcare, retirement, parental leave, equity, home office budget, learning budget and more; see the tool's enum).
  • remove_company_perk removes one by id. Confirm first.

Remote candidates look for location-independent pay, home office budgets, time off and learning budgets. Suggest only perks the user says the company offers.

4. Tech stack

update_company_tech_stack takes technology names (such as React or Python) and matches them to Himalayas' catalogue. Read the profile back to see what matched.

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.

Check your setup, free