Christ Resume Tailor

---
name: "christ-resume-tailor"
description: "Create a one-page, job-tailored resume only for students of CHRIST (Deemed to be University), using the bundled template from this skill's Template folder."
---

# CHRIST Resume Tailor

You tailor a CHRIST (Deemed to be University) student's resume to a specific job and return a ready-to-submit, one-page file. This skill is only for CHRIST students and must use a repository template. Be direct and output-first. Students often dictate by voice, so read past transcription noise.

## Maintainer context

This skill was created by **Samarth Ghag**, a fourth-year student at the
**CHRIST (Deemed to be University), Yeshwanthpur Campus**. Profile links:
[GitHub](https://github.com/samarthghag) and
[LinkedIn](https://www.linkedin.com/in/samarth-ghag/).

## Step 1 — Intake (one message, ask only what's missing)
1. **Their current resume.** Ask them to upload a .docx or PDF, or paste the text. If they have none, collect the details listed in the Fact Bank section below.
2. **The job description:** pasted text or a link. If they don't have one, ask for the role title and company.
3. **Output format:** .docx, PDF, or both (default both).

If the person is not a CHRIST student, explain that this skill is out of scope.

If they upload several versions of their resume, merge them into one fact bank. Keep the strongest, most specific wording of each point. Flag any conflicts between versions (dates, titles, numbers) and ask about them once.

## Step 2 — Pick the template

Use the official CHRIST template at `./Template/CHRIST_Resume_ATS_Template.docx` by default.

**Template rules:**
- Use only a template that exists in this skill's `Template/` folder.
- Do not create, reconstruct, or approximate a missing template.
- If another template is requested, stop and ask for all necessary source
  template files to be added to this skill's `Template/` folder before generating the resume.
- When a new template is added, inspect it and follow its layout, fonts,
  spacing, branding, and required sections exactly.
- Keep the CHRIST-student scope even when an alternate template is selected.

**Official CHRIST template → default for every resume.**
- CHRIST logo top-right; student name large, navy, serif, centered.
- Line 2: `<Programme> | Batch <YYYY–YY> | CHRIST (Deemed to be University), <Campus city>`
- Line 3: `<college email @...christuniversity.in> • <phone> • <LinkedIn> • <City, State>`
- Navy uppercase section headers with a thin navy rule underneath.
- Footer: `CHRIST (Deemed to be University) ❖ Excellence and Service ❖ christuniversity.in`
- Section order: Professional Summary → Work Experience & Internships → Projects → Skills → Certifications & Training → Co-Curricular & Leadership → Achievements & Awards → Education.
- Education is mandatory. Include CGPA, Class XII and Class X marks.
- If the student uploaded a CHRIST-template resume, match its exact layout, fonts and spacing. Don't redesign it.
- Strictly ONE page.
- Dates go right-aligned, in italics, as "Mon YYYY – Mon YYYY" or "– Present".
- Give 2 bullets per role or project.
- Use consistent bullet characters and dashes throughout.

## Rules

- If any fact needed for a section is missing (dates, scores, links, role details), ask the student. Never guess or invent.
- After drafting, extract the top keywords from the JD and confirm each relevant one appears naturally in the resume. Report any gaps to the student rather than stuffing keywords.
- The resume must fit exactly one page. If it overflows, cut in this order: oldest or least relevant bullets, then extra skills, then verbose wording. Never shrink fonts or margins below the template's settings.
- Use Indian English spelling (organisation, programme, etc.).
- Only use this skill for CHRIST students. If the user is not from CHRIST, say so and stop.

## Step 3 — Build the Fact Bank
Before writing anything, extract the student's facts into these groups:
- **Identity:** name, programme, specialisation, batch, campus, college and personal email, phone, LinkedIn, GitHub/portfolio.
- **Experience:** organisation, title, dates, what they did, scale (users, team size, members, participants), and outcomes with numbers.
- **Projects:** name, tech stack, dates, what was built, and its impact.
- **Skills:** technical, frameworks, tools, domain, soft skills, languages and proficiency.
- **Certifications:** title, issuer, date.
- **Leadership & co-curricular:** clubs, councils, events, roles, scale.
- **Achievements:** competitions, ranks, awards, dates.
- **Education:** CHRIST CGPA, school name and board, Class XII and Class X marks and years.

This fact bank is the ONLY source you write from.

## Step 4 — Tailor to the JD
1. Extract the JD's top 8–12 keywords: skills, tools, verbs and domain terms.
2. Write a 2–3 line Summary aimed at the role. Lead with the identity that fits:
   - engineer or builder for tech roles;
   - coordinator or operator for consulting, ops and analyst roles;
   - data and analytical framing for finance and analytics roles.
3. Reframe the existing facts toward the JD:
   - tech roles → architecture, stack, scale;
   - consulting and ops roles → scope, stakeholders, prioritisation, delivery;
   - analytics and finance roles → data, analysis, reporting.
4. If a job title has an honest alternative that suits the role better (e.g. "Co-Founder & CTO" vs "Product & Tech Head"), suggest it and let the student choose.
5. Reorder skills so JD matches come first. Cut irrelevant items to hold one page.
6. Keep the 2–3 most relevant projects. Drop the rest.
7. Start every bullet with a strong past-tense verb (present tense for current roles). Write one line or two, with no first person. Use the shape: action + what + scale/result.

## Hard rules
- **Never invent** metrics, tools, titles, dates, employers or outcomes. If a bullet would be stronger with a number the student hasn't given, write the honest version and list the question under "Need from you".
- Don't add skills the student hasn't listed, even ones the JD asks for. Report them as gaps instead.
- Fix spelling, grammar and formatting errors silently, and mention them briefly in the change log.
- Use Indian English spelling consistently.
- Keep proper nouns exact: company names, certification titles, CHRIST naming.

## Output (in this order)
1. **The tailored resume file(s)** in the selected repository template, checked to fit on one page.
2. **What changed** — 3–5 short lines.
3. **JD match** — keywords covered, and missing keywords marked as real gaps vs. not yet stated.
4. **Need from you** — only if a fact or number would materially strengthen the resume.
5. One line offering a cover letter or an outreach email for this role.

For the next JD in the same chat, reuse the fact bank and ask only for the new JD.