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

build-candidate-profile

Skill0 starsChanged 25 days agoMITView on GitHub

Build and improve the user's Himalayas candidate profile, which drives job matches, tailored documents and how employers find them, by importing from LinkedIn or a resume, editing experience, education, skills, work permits, salary expectations and search status, and setting a photo, ID verification and email preferences. Use when the user wants to set up, import, review or update their Himalayas profile or account settings.

The file

We split this skill into the rules it gives an agent

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

  • 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_my_profile. Report what is missing or weak for the user's goal: primary role, location, work permits, salary expectations, search …

    line 13

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

Build the candidate profile

Follow himalayas-basics for the shared rules. Profile tools need a Himalayas account.

1. Review what is there

Call get_my_profile. Report what is missing or weak for the user's goal: primary role, location, work permits, salary expectations, search status, experience with descriptions and skills, education, and tech stack.

2. Import (fastest for a new profile)

import_profile fills the profile from a LinkedIn profile URL or pasted resume text. It runs in the background for a few minutes; call get_my_profile afterwards to see the result.

  • append_only adds what is missing and keeps what is there.
  • replace_all overwrites the profile. Ask the user before using it.

3. Edit

  • update_profile: name, bio, intro, location, career_search_status (actively_searching, open_to_roles, closed_to_roles), primary role, salary expectations, work permits and skills. Only the fields you pass change.
  • add_experience, update_experience, delete_experience and the matching education tools take ids from get_my_profile. Deletes can't be undone.
  • update_tech_stack replaces the list of tools and technologies. Names are matched to Himalayas' catalogue; unknown ones are requested for review.

Show the changes before writing them, then read the profile back.

4. Photo and verification

  • update_profile_photo sets the avatar or cover photo from an https image URL (JPEG, PNG, WebP or GIF, up to 5 MB).
  • list_headshots lists headshots the user already made on Himalayas, and use_headshot_as_profile_photo sets one as the photo. get_headshots_link returns the page where they make new ones.
  • get_verification_link returns the next step for verifying the user's identity and work permits (the verified badge): the status, a verification link, or a checkout link. A passport or national ID verifies identity and the work permit for that country; a driver's licence verifies identity only. The user does the verification or payment on Stripe themselves.

5. Settings

  • update_email_preferences turns Himalayas emails on or off; only the settings you pass change.
  • update_account sets the account time zone used for email timing.
  • Email address, password and account deletion can only be changed on himalayas.app.

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