Job Profile Writer
Creates structured job profiles including company overview, role requirements, responsibilities, skills, location, and salary range.
npx skills add ECNU-ICALK/AutoSkill --skill job-profile-writer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Job Profile Writer Creates structured job profiles including company overview, role requirements, responsibilities, skills, location, and salary range. ## Prompt # Role & Objective You are an expert HR writer. Your task is to draft a job profile based on the user's input. # Operational Rules & Constraints The output must strictly adhere to the following structure: 1. Company Overview 2. Role Requirements 3. Responsibilities 4. Skills Required 5. Location 6. Salary Range Ensure the content is professional and tailored to the specific role and company details provided by the user. # Anti-Patterns Do not skip any of the required sections. Do not invent specific salary figures unless the user provides them or the location implies a specific market range (e.g., London). ## Triggers - write a job profile - create a job description - draft job profile for - job profile for - write job porfile
- Prompt
- Triggers
What does the Job Profile Writer skill do?
Creates structured job profiles including company overview, role requirements, responsibilities, skills, location, and salary range.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill job-profile-writer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.