Get Job
agentenatalie/get-job.skill
实习.skill / get-job.skill：从岗位调研、简历改写到分轮次面试准备的全流程求职 skill。适合找工作、投实习、校招、秋招、春招、暑期实习、社招、跳槽、转行、跨专业求职、留学生求职，以及产品经理、运营、市场、咨询、AI 产品、AI Coding、数据分析、技术岗等目标岗位准备。
Review, tailor, score, or rewrite IT and cybersecurity resumes.
Install Cyber Resume Reviewer
$ npx skills add mubix/cyber-resume-reviewer-skill --skill cyber-resume-reviewer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mubix/cyber-resume-reviewer-skill cyber-resume-reviewer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mubix/cyber-resume-reviewer-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cyber-resume-reviewer .claude/skills/cyber-resume-reviewer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cyber-resume-reviewer" agent skill from https://github.com/mubix/cyber-resume-reviewer-skill/tree/main/cyber-resume-reviewer into .claude/skills/cyber-resume-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cyber-resume-reviewer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mubix/cyber-resume-reviewer-skill/tree/main/cyber-resume-reviewerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mubix/cyber-resume-reviewer-skill --skill cyber-resume-reviewer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mubix/cyber-resume-reviewer-skill cyber-resume-reviewer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mubix/cyber-resume-reviewer-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cyber-resume-reviewer .agents/skills/cyber-resume-reviewer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cyber-resume-reviewer" agent skill from https://github.com/mubix/cyber-resume-reviewer-skill/tree/main/cyber-resume-reviewer into .agents/skills/cyber-resume-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cyber-resume-reviewer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mubix/cyber-resume-reviewer-skill --skill cyber-resume-reviewer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mubix/cyber-resume-reviewer-skill cyber-resume-reviewer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mubix/cyber-resume-reviewer-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cyber-resume-reviewer .cursor/skills/cyber-resume-reviewer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cyber-resume-reviewer" agent skill from https://github.com/mubix/cyber-resume-reviewer-skill/tree/main/cyber-resume-reviewer into .cursor/skills/cyber-resume-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cyber-resume-reviewer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mubix/cyber-resume-reviewer-skill.git --path cyber-resume-reviewer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mubix/cyber-resume-reviewer-skill --skill cyber-resume-reviewer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mubix/cyber-resume-reviewer-skill cyber-resume-reviewer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mubix/cyber-resume-reviewer-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cyber-resume-reviewer .gemini/skills/cyber-resume-reviewer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cyber-resume-reviewer" agent skill from https://github.com/mubix/cyber-resume-reviewer-skill/tree/main/cyber-resume-reviewer into .gemini/skills/cyber-resume-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cyber-resume-reviewer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mubix/cyber-resume-reviewer-skill cyber-resume-reviewerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mubix/cyber-resume-reviewer-skill --skill cyber-resume-reviewer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mubix/cyber-resume-reviewer-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/cyber-resume-reviewer .github/skills/cyber-resume-reviewer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cyber-resume-reviewer" agent skill from https://github.com/mubix/cyber-resume-reviewer-skill/tree/main/cyber-resume-reviewer into .github/skills/cyber-resume-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cyber-resume-reviewer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mubix/cyber-resume-reviewer-skill --skill cyber-resume-reviewer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mubix/cyber-resume-reviewer-skill cyber-resume-reviewer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mubix/cyber-resume-reviewer-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cyber-resume-reviewer .opencode/skills/cyber-resume-reviewer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cyber-resume-reviewer" agent skill from https://github.com/mubix/cyber-resume-reviewer-skill/tree/main/cyber-resume-reviewer into .opencode/skills/cyber-resume-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cyber-resume-reviewer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cyber-resume-reviewer- GitHub stars
- 184
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,320 words
- Files
- 51 (incl. scripts, references, assets)
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review, tailor, score, or rewrite IT and cybersecurity resumes.
- Works in 9 steps: Read the supplied resume and target. For… → Resolve only essential uncertainty. No… → Triage blockers, risks, and unknowns.… → …
- Candid critique
- SKILL.md covers Start with the requested…, Working sequence, Truth and scope invariants and Reference routing, plus 2 more sections
- Calls python3
What it does
Cyber Resume Reviewer is an agent skill from mubix/cyber-resume-reviewer-skill. Review, tailor, score, or rewrite IT and cybersecurity resumes. Use for candid critique, job-description fit, exact edits, or complete rewrites; never rank candidates.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 54 other files, including scripts, reference files and assets (for example `CHANGELOG.md`, `README.md` and `agents/openai.yaml`).
It sits in Business, Finance & HR, covering Recruiting and HR. The repository describes itself as: A skill to help cybersecurity folks update and tweak their resume. The licence is MIT.
When your agent uses it
- Candid critique
- Job-description fit
- Complete rewrites
- Never rank candidates
Example prompts
- “/cyber-resume-reviewer”
Requirements
- Python 3
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Read the supplied resume and target. For PDF/DOCX, use available document extraction and rendering capabilities; do not assume specific…
- Resolve only essential uncertainty. No resume: ask for it. No JD: use a supplied title and label the role profile inferred. A company or…
- Triage blockers, risks, and unknowns. Read submission triage. An observed defect, an explicit unmet requirement, and an unverified fact…
- Build a small evidence map. Read review framework. Distinguish candidate-stated facts, job requirements, reviewer inferences, and…
- Review the relevant role and evidence. Use the references below selectively. Check scope, ownership, technical meaning, and results. A…
- Use the text helper when useful. For a full text review or repeated checks, run python3 scripts/analyze_resume_text.py --resume resume.txt…
- Make the changes the user asked for. Prefer exact source quotes and replacements supported entirely by known facts. Move or merge text…
- Produce the artifacts. Write a full review or JD fit report as Markdown first. Treat it as the only content source, then render the PDF…
- Verify the result. Check factual traceability, dates, titles, credential status wording, technical meaning, and unresolved placeholders…
What it can do on your machine
Read from SKILL.md and the folder at commit 263acc3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cyber Resume Reviewer loads about 2.9k tokens when it runs, and up to ~22k if it reads all its reference files. Until then it costs about 47 tokens; SKILL.md has 1,320 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from mubix/cyber-resume-reviewer-skill at commit 263acc3, republished under its MIT licence (© mubix). 1,320 words, ~2,863 tokens.
Download SKILL.mdSave it as
.claude/skills/cyber-resume-reviewer/SKILL.md (or your agent's skills folder). This skill also uses 50 other files; get the full folder from GitHub.- name
- cyber-resume-reviewer
- description
- Review, tailor, score, or rewrite IT and cybersecurity resumes. Use for candid critique, job-description fit, exact edits, or complete rewrites; never rank candidates.
- metadata.version
- 4.1.0
IT and Cybersecurity Resume Reviewer
Improve how the candidate communicates relevant work. Preserve the useful four-lens model: Machine-read (document extraction), Human-skim (first impression), Human-believe (evidence), and Human-act (target alignment). These are review lenses, not a universal hiring sequence or a prediction of recruiter behavior.
Start with the requested deliverable
| Request | Deliver | Default artifact |
|---|---|---|
| Review or improve | Candid verdict, strongest evidence to preserve, prioritized findings, exact edits, and important open questions. Use the standard report template selectively. | Markdown and a PDF rendered from that Markdown |
| Quick review | Up to five material findings and useful exact edits. Omit scoring unless requested. | In conversation, or Markdown when asked |
| Tailor to a JD | Map requirements to evidence, then make truthful changes. Separate employer requirements from assumed role expectations. | Markdown and PDF for a fit report; requested format for a resume rewrite |
| Rewrite / give me an updated resume | Produce the complete rewrite now using established facts. Do not require a full report or another opt-in. Explain material changes briefly. | Rewritten resume in the requested format |
| Score | Use the anchored rubric and show assessed coverage. Score the document, not the person's worth or hiring probability. | Part of the accompanying report |
| JSON | Use the report schema and validator. The analyzer's JSON is a different artifact. | JSON only |
| Interview stories / compare versions | Use the corresponding template only when requested or useful to the stated task. | Markdown unless another format is requested |
Working sequence
- Read the supplied resume and target. For PDF/DOCX, use available document extraction and rendering capabilities; do not assume specific skill names or tools exist. Read images visually or with OCR, checking uncertain text. Preserve role boundaries, dates, and source locations. If only pasted text is available, assess content and mark visual layout and original-file parsing Not assessed.
- Resolve only essential uncertainty. No resume: ask for it. No JD: use a supplied title and label the role profile inferred. A company or industry alone does not define a job. No target: perform a useful general IT/cyber review now; suggest one or two plausible directions and ask which to target before making role-specific claims. Do not withhold all edits.
- Triage blockers, risks, and unknowns. Read submission triage. An observed defect, an explicit unmet requirement, and an unverified fact are different findings. Missing content on a redacted review copy is not a candidate failure.
- Build a small evidence map. Read review framework. Distinguish candidate-stated facts, job requirements, reviewer inferences, and unknowns. Link every new substantive claim to a resume location or user statement. Do not import facts from another candidate, a sample, the JD, or prior personal context about the reviewer.
- Review the relevant role and evidence. Use the references below selectively. Check scope, ownership, technical meaning, and results. A skill listed without an example is uncorroborated in this document, not automatically false. Specific qualitative outcomes and well-described operational work count; numbers are optional.
- Use the text helper when useful. For a full text review or repeated checks, run
python3 scripts/analyze_resume_text.py --resume resume.txt --jd jd.txt(omit--jdwhen absent). It finds candidate signals, never ATS acceptance, skill mastery, or hiring odds. Small edits do not need a mandatory script run. Read helper interpretation before using its output. - Make the changes the user asked for. Prefer exact source quotes and replacements supported entirely by known facts. Move or merge text without changing its employer, dates, participation level, or context. Place questions for stronger future claims outside the clean rewrite. If essential facts are missing, provide the useful supported portion and identify the limitation.
- Produce the artifacts. Write a full review or JD fit report as Markdown first. Treat it as the only content source, then render the PDF from it. Read report rendering before rendering in a session. Prefer
python3 scripts/render_report.py /path/to/review.md /path/to/resume-review.pdf; if its dependencies are unavailable, use the host's PDF capability while preserving the same content and visual evidence rules. Save candidate artifacts outside the skill directory. Present both files. If the host cannot create files, provide the complete Markdown in conversation and state that the PDF could not be generated there. - Verify the result. Check factual traceability, dates, titles, credential status wording, technical meaning, and unresolved placeholders. For a PDF, inspect every rendered page, confirm the page count from the file, and compare extracted reading order with the visual document. Confirm that no
[VERIFY]token appears in a supported-replacement block. Report only checks actually performed.
Show full SKILL.md (582 more words)Show less
Truth and scope invariants
- Do not invent or upgrade employers, titles, duties, tools, metrics, education, certifications, clearances, authorization, team size, budget authority, board access, or project outcomes.
- Keep operated / built / supported / led / advised / approved distinct. Lab, course, volunteer, personal, client, and production work must retain their context. Preserve team attribution.
- Put assumptions in analysis, never as facts inside the resume. No
[Assumed: ...]claims. For a requested fill-in draft use[VERIFY: specific fact], list every occurrence in a verification table, and label that draft incomplete. Prefer a clean supported version plus optional questions over a resume full of blanks. - An example is illustrative, never candidate evidence. Read truth, bias, and privacy for redaction, career gaps, and sensitive operational information.
- Keep live candidate data out of reusable skill files, templates, examples, test fixtures, logs, and source-control history. Never turn a live review into a reusable example. Generated review files belong outside the skill directory.
- Never equate keyword overlap with qualifications, fit percentage, ATS score, or interview probability. Do not diagnose deception, personality, motivation, or retention risk from prose style or career history.
- The visual layer may not assert what the prose may not assert. Do not use score gauges, progress bars, percentage rings, letter grades, match percentages, radar charts, or proficiency bars. Colour may distinguish finding priority and evidence provenance; it may not rate the person. See report rendering.
- Verify time-sensitive external claims when they matter: employer requirements, certification availability/prerequisites, federal instructions, vendor parser behavior, and framework naming. Use source policy. If browsing is unavailable, state what remains unverified and continue the content work.
Reference routing
| Situation | Read |
|---|---|
| All substantial reviews | Review framework, submission triage |
| Scores requested or a comprehensive scored review | Scoring rubric |
| Role family, level, industry, IT/cyber pivots | Role taxonomy |
| File formatting, reading order, ATS question | Parser risk |
| JD requirements / keyword alignment | Requirement triage, fit mapping |
| Bullet or summary changes | Rewrite guide, anti-pattern examples |
| First impression or visible layout | Reader review |
| Technical claims, cyber metrics, framework wording | Technical claim checks |
| Managers, executives, BISO, Field CISO, fractional leaders | Leadership |
| Career transition, military translation, return to work | Transitions |
| Actual learning or credential gaps | Learning |
| Federal, contractor, clearance, DCWF | Federal and cleared roles |
| Sensitive details, redacted source, bias concerns | Truth, bias, and privacy |
| External factual claims | Sources and refresh rules |
| Analyzer output | Helper interpretation |
| Markdown/PDF deliverables, formatting conventions, renderer setup, or PDF checks | Report rendering |
Output resources
Choose, trim, and reorder these to match the request; do not fill every section by default:
- Standard report
- Quick review
- Exact edits
- Complete rewrite
- Optional intake
- Interview stories
- Change tracking
- Structured report schema: validate with
python3 scripts/validate_report.py report.json; requiresjsonschemafor this optional mode. - Worked example: illustrative, not a required report length.
- Report rendering: two-artifact contract, visual evidence rules, metadata, setup, and verification.
- House stylesheet: print design used by the renderer.
- PDF renderer: render with
python3 scripts/render_report.py /path/to/review.md /path/to/resume-review.pdf.
Quality bar
Lead with the main assessment. Explain what the resume demonstrates, what is unclear, and the highest-value repair. Preserve strengths as deliberately as you fix weaknesses. Be candid without ridicule, canned praise, or invented urgency. Use plain language and the candidate's voice. Do not manufacture five problems, ten edits, a certification plan, or a warning banner when the evidence does not warrant them.
Before delivery, ask: Does each replacement say only what the candidate established? Did missing evidence become an accusation? Did a formatting heuristic become a guarantee? Did the design imply a claim the prose cannot support? Does the output fulfill the requested review, tailoring, or rewrite?
© mubix, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 50 other files (scripts, references, assets) in cyber-resume-reviewer of mubix/cyber-resume-reviewer-skill.
- SKILL.md
- CHANGELOG.md
- README.md
- agents/openai.yaml
- assets/report.css
- examples/example-output-summary.md
- examples/example-report.json
- examples/sample-job-description-cloud-security.txt
- examples/sample-resume-redacted.txt
- references/analyzer-interpretation.md
- references/anti-pattern-gallery.md
- references/ats-formatting-and-parser-risk.md
- references/bias-and-ethics-guardrails.md
- references/career-transition-translation.md
- references/certifications-and-learning.md
- references/cybersecurity-role-taxonomy.md
- references/executive-and-leadership-resumes.md
- … and 34 more
Open the folder on GitHubat commit 263acc3
Compare with similar skills
Cyber Resume Reviewer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cyber Resume Reviewer this skillmubix/cyber-resume-reviewer-skill | 184 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Get Jobagentenatalie/get-job.skill | 632 | — | ~1.7k | Automated safety check: Pass | CC-BY-NC-ND-4.0 | |
| Resume Reviewerweeelin98/ResumeDom | 173 | — | ~2.4k | Automated safety check: Pass | None | |
| Build Resume Portfolio Sitetao943/build-resume-portfolio-site | 195 | — | ~5.8k | Automated safety check: Pass | None | |
| Repo To Resume TailorSsabby1/repo-to-resume-tailor | 127 | — | ~1.8k | Automated safety check: Pass | MIT | |
| GitHub Project Contributor Finder API Skillbrowser-act/skills | 6.1k | 1 repos | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Resume Reviewer
weeelin98/ResumeDom
Build, assess, review, and tailor evidence-backed US-market technology resumes for computer-science interns and new graduates.
Build Resume Portfolio Site
tao943/build-resume-portfolio-site
A skill your agent uses when turning resume materials and an optional job description into verified, approved content and a runnable React + Vite resume or portfolio site, or when redesigning an…
Repo To Resume Tailor
Ssabby1/repo-to-resume-tailor
Analyze a full code repository and generate one resume-ready project description grounded in repository evidence.
GitHub Project Contributor Finder API Skill
browser-act/skills
This skill helps users extract GitHub repository project details and contributor contact information using keywords, stars, and update dates.
Candidate Status
yc-software/recruiting
Look up the full status of a recruiting candidate by name. An agent skill from yc-software/recruiting.
Related
Categories
Questions about Cyber Resume Reviewer
What does Cyber Resume Reviewer do?
Review, tailor, score, or rewrite IT and cybersecurity resumes. Cyber Resume Reviewer is an agent skill from mubix/cyber-resume-reviewer-skill. Review, tailor, score, or rewrite IT and cybersecurity resumes.
When should I use Cyber Resume Reviewer?
Cyber Resume Reviewer fits situations like: candid critique; job-description fit; complete rewrites; never rank candidates.
How do I install Cyber Resume Reviewer in Claude Code?
Run `npx skills add mubix/cyber-resume-reviewer-skill --skill cyber-resume-reviewer -a claude-code`. Or copy the skill folder (cyber-resume-reviewer in mubix/cyber-resume-reviewer-skill) into .claude/skills/cyber-resume-reviewer in your project. Claude Code loads it when a task matches its description.
How do I install Cyber Resume Reviewer in Codex?
Run `npx skills add mubix/cyber-resume-reviewer-skill --skill cyber-resume-reviewer -a codex`. Or copy the skill folder (cyber-resume-reviewer in mubix/cyber-resume-reviewer-skill) into .agents/skills/cyber-resume-reviewer in your project. Codex loads it when a task matches its description.
Can I use Cyber Resume Reviewer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mubix/cyber-resume-reviewer-skill --skill cyber-resume-reviewer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cyber-resume-reviewer, .gemini/skills/cyber-resume-reviewer, .github/skills/cyber-resume-reviewer and .opencode/skills/cyber-resume-reviewer in your project.
What does Cyber Resume Reviewer need to run?
Going by SKILL.md and its folder, Cyber Resume Reviewer needs the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Cyber Resume Reviewer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cyber Resume Reviewer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Cyber Resume Reviewer use?
Cyber Resume Reviewer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cyber Resume Reviewer use?
About 2.9k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 19k tokens, read only when the agent opens those files.
What are the alternatives to Cyber Resume Reviewer?
Skills that share tags, products or a category with Cyber Resume Reviewer: Get Job (agentenatalie/get-job.skill, 632 stars), Resume Reviewer (weeelin98/ResumeDom, 173 stars), Build Resume Portfolio Site (tao943/build-resume-portfolio-site, 195 stars) and Repo To Resume Tailor (Ssabby1/repo-to-resume-tailor, 127 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cyber Resume Reviewer?
mubix (a GitHub user) maintains it in mubix/cyber-resume-reviewer-skill, which has 184 GitHub stars. The repository was last updated on September 20, 2026.
Source: mubix/cyber-resume-reviewer-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.