Skip to content

splash0047/resume-generator / skills/fresher-signal-analyzer

Fresher Signal Analyzer

Verified

Evaluate new-grad hiring evidence across education, DSA, projects, repositories, deployment, internships, and role alignment without inventing a universal fresher score.

Fresher Signal Analyzer

Purpose

Identify which parts of a new-grad profile are strong, weak, missing, or irrelevant for a target role.

Do not assign a universal 1-10 score or imply a specific signal predicts callbacks.

Evidence Areas

Education

Record degree, expected graduation, CGPA/percentage when supplied, and relevant coursework only if it helps the role.

DSA / Problem Solving

Evidence can include:

  • verified coding profiles;
  • contest results;
  • coursework/projects with algorithmic depth;
  • interview-assessment performance supplied by the candidate.

Do not assume lack of a public profile means lack of DSA ability.

Internship / Work Evidence

Check:

  • clarity of employer/program naming;
  • actual responsibilities;
  • tools used;
  • deliverables;
  • measured results with provenance.

Project Depth

For the top relevant projects, check:

  • implemented architecture;
  • meaningful technical decisions;
  • tests;
  • failure handling;
  • deployment;
  • documentation;
  • current repository consistency.

GitHub Quality

Check repository hygiene qualitatively:

  • setup works;
  • README reflects current code;
  • secrets are not exposed;
  • meaningful commits/files exist;
  • tests/CI where appropriate;
  • no obviously fabricated benchmark claims.

Deployment Evidence

Classify as:

  • local only;
  • publicly deployed demo;
  • production/operational only when supported by real evidence.

Certifications

Separate:

  • exam-based professional certifications;
  • training completions / badges;
  • courses.

Communication of Role Identity

Check whether the profile consistently supports one target role family rather than listing unrelated tools.

Application Readiness

Check hard eligibility first: graduation batch, degree, dates, experience requirements, location/work authorization, and availability.

Output

SignalStatusEvidenceGapNext action
EducationStrong / Adequate / Weak / Unknown.........
DSA............
Internship............
Project depth............
GitHub quality............
Deployment............
Certifications............
Role identity............
Application readiness............

Then provide:

  • strongest 3 signals;
  • weakest 3 signals;
  • highest-leverage improvements before the next application cycle.

Guardrails

  • No callback-rate claims.
  • No universal fresher score.
  • No requirement for public LeetCode/GitHub metrics unless the role or user specifically values them.
  • Evidence strength matters more than quantity.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall