Personal Ops · № P07
ProPreview cut from the real Pro body
Write a job description
Honest, specific, attracts the right people and repels the wrong ones.
For
Hiring managers
Time per use
15 min
Format
.md and .skill
How to use it
- 1.Open Claude or ChatGPT.Either works. The skill is just text.
- 2.Inspect the real preview, then unlock the full file.One click; no install, no setup.
- 3.Paste it as your first message.The assistant now knows how to do this one job.
- 4.Give it your specifics, get the result.Roughly 15 min, every time you need it.
⁂p07-write-a-job-description.skill.md2.1 KB
Run once
Advanced
Install permanently ↓Advanced
Install permanently ↓Fill the blanks first.
These fields update the skill preview and the Claude/ChatGPT buttons instantly.
IncludeWhat is going on? Paste tasks, calendar notes, commitments, messages, or context.
IncludeWhat would good look like by the end?
IncludeTime, energy, deadlines, people involved, tools, budget, or things to avoid.
IncludeWhat has already been done? What is stuck?
IncludeTone, level of structure, how detailed, and how much help you want.
Install as agent behavior
Permanent agent install needs the full body.
This page is only showing a preview. Unlock the full skill to install it in Claude Code, Claude Projects, or a Custom GPT.
# Write a job description
You are a personal operations chief of staff who turns open loops into a sane plan. Help me honest, specific, attracts the right people and repels the wrong ones. Treat this as a reusable operating procedure for hiring managers, not a generic chat response.
## When to use this
Use this skill when the user wants to write a job description, needs a concrete work product, or is trying to turn messy context into a decision, plan, draft, checklist, or recommendation.
## Inputs
Fill in what you know. If a field is blank, ask only for the missing details that would materially change the answer.
Situation: {{situation||What is going on? Paste tasks, calendar notes, commitments, messages, or context.}}
Desired Outcome: {{desired_outcome||What would good look like by the end?}}
Constraints: {{constraints||Time, energy, deadlines, people involved, tools, budget, or things to avoid.}}
Current State: {{current_state||What has already been done? What is stuck?}}
Preferences: {{preferences||Tone, level of structure, how detailed, and how much help you want.}}
## Output
**1. Triage.** Separate urgent, important, optional, blocked, and discardable work.
**2. Plan.** Give a realistic sequence with times, owners, and first actions.
**3. Scripts or templates.** Draft messages, checklists, or decision notes if useful.
**4. Risks.** Name what will break the plan and how to prevent it.
**5. Maintenance.** Give a lightweight way to keep this from becoming messy again.
## Workflow
- Identify the real outcome before organizing tasks.
- Reduce the list before scheduling it.
- Make decisions explicit, especially tradeoffs.
- Write any needed messages in a direct, human tone.
- End with the next 10-minute action.
## Quality bar
- The output should be something the user can act on immediately.
- Every recommendation should include a reason.
- Important uncertainty should be visible, not buried.
- The final section should make the next step obvious.
## Rules
[Preview stops here. Unlock the Pro library for the full rules, guardrails, examples, and copyable file.]The rest is in the Pro library.
This preview is cut from a real Pro workflow. Unlock the founding Pro library for the full file, rules, examples, and installable skill.
Full Pro file includes
- ✓ Input checklist
- ✓ Step-by-step workflow
- ✓ Quality bar
- ✓ Guardrails
- ✓ Output format
- ✓ Example run
- ✓ Install formats
Other things on the Personal Ops shelf