application-form-filler

Files (1)

• SKILL.md

SKILL.md (first lines)

# Application Form Filler

## When to Use This Skill

Use this skill when the user wants to:
- Answer specific questions on a job application form
- Fill out text fields on Greenhouse, Lever, Ashby, Workday, or any ATS
- Write responses to "tell us about yourself" or "why do you want to work here" prompts
- Get clean, copy-pasteable answers to application questions
- Mentions: "fill this out", "what do I write here", "answer this question", "application form", "form field"

## Core Principle

Application form answers should be direct and specific — not a cover letter crammed into a text box. Each field has a purpose. Answer that purpose clearly, then stop.

**The answer should feel like:** A real person typed it, not a template was filled in.

## Before Answering

Always read:
1. **The job description** — mirror its language and priorities
2. **The candidate's CV/profile** — pull real projects, roles, and metrics
3. **The specific question** — answer exactly what was asked, not what you wish was asked

If the user hasn't provided a CV or JD, ask for them before writing.

## Question Types and How to Handle Each

---

### Type 1: Experience/Background Questions

**Examples:**
- "How many years of experience do you have with [technology]?"
- "Describe your experience with [domain]"
- "What backend frameworks have you used?"

**Format:**
```
[Technology/skill] — [X years]. [One sentence on what you used it for, with a
specific project or context]. [Optional: secondary tools in the same category].
```

**Rules:**
- Lead with the most used/relevant technology
- Give years honestly — don't inflate
- Anchor every claim to a real project or role
- For "describe experience" questions: 2-4 sentences max, one project per sentence
- If experience is indirect (adjacent domain), say so and pivot to what is relevant

---

### Type 2: Why This Company / What Interests You

**Examples:**
- "Why do you want to work at [Company]?"
- "What interests you about this role?"
- "Why are you a good fit?"

**Format:**
```
[Specific thing about the company/role that's genuinely interesting — not generic].
[How that connects to something the candidate has actually worked on].
[Optional: one line on why this domain, not just this company].
```

**Rules:**
- Must be specific to this company — no boilerplate
- Research the company before answering if needed
- Connect to real work, not aspirations
- Keep it under 150 words for a form field
- Don't repeat the JD back to them

---

### Type 3: Portfolio / Work Samples

**Examples:**
- "Include any other samples of work you're proud of"
- "Link to relevant projects or repositories"
- "Describe a project you've built end-to-end"

**Format:**
List projects with one-line descriptions and links. Lead with the most relevant.

```
[Project Name] ([live URL] | [github URL]) — [one line: what it is and one
proof point]. [Stack if relevant].
```

**Rules:**
- Only include projects relevant to the role
- Always include links (live demo > GitHub > nothing)
- If the project has paying users or measurable usage, say so — once
- Don't pad with irrelevant projects to look prolific

---

### Type 4: Technical Skill Questions

**Examples:**
- "Which frontend frameworks have you used most extensively?"
- "Rate your proficiency in Python"
- "Describe your experience with cloud infrastructure"

**Format:**
For open-text fields:
```
[Primary skill] — [X years]. [Specific use: what you built with it, in what context].
[Secondary skill] — [X years]. [Same].
[Note any relevant gaps honestly].
```

For rating/dropdown fields: pick the honest level — don't optimize for the highest rating if it's not accurate.

**Rules:**
- Years + context beats years alone
- Acknowledge gaps rather than hiding them
- If asked to rate, rate honestly — inflated ratings create problems in technical interviews

From Infrasity-Labs/dev-gtm-claude-skills, MIT.

More from Infrasity-Labs/dev-gtm-claude-skills