Token导航 LogoToken导航TokenDH.com
效率需要联网clawhub未标认证来源可访问clear审计提醒

resume-reviewer-pdfresume reviewer PDF 效率

Agent Skill

resume-reviewer-pdf 用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目、生成组件或检查界面实现时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,472

周安装

102

GitHub Stars

公开资料未说明

下载量

808
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:resume-reviewer-pdf(resume reviewer PDF 效率)
来源仓库:https://github.com/prabhatkgupta/resume-reviewer-pdf
安装命令:
openclaw skills install resume-reviewer-pdf
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install resume-reviewer-pdf

简介

面向软件工程领域的 PDF 简历审查工具,覆盖前端、后端与 ML 方向评估。

  • 当用户对简历提出反馈请求时,提供结构化评价与改进建议。
  • 分析技术术语准确性、项目描述清晰度与整体逻辑连贯性。
  • 需具备 PDF 解析能力,建议验证文件路径权限与字体渲染兼容性。
  • 注意:评审意见仅供参考,最终录用决策不应完全依赖自动化分析结果。

SKILL.md

name
resume-reviewer
description
Comprehensive review and analysis of software engineering resumes in PDF format (frontend, backend, or ML domains). Use this skill when users ask to review, analyze, provide feedback on, or evaluate a resume PDF. The skill analyzes technical content quality, career progression, ATS compatibility, grammar, structure, and provides actionable improvement suggestions based on current industry trends.

Resume Reviewer for Software Engineers

This skill provides comprehensive analysis and feedback for software engineering resumes (frontend, backend, or ML domains) in PDF format, typically created with LaTeX.

Analysis Framework

Perform analysis in the following order:

1. Extract Resume Content

CRITICAL: Always use the provided script to extract PDF text:

python3 scripts/extract_pdf_text.py <path_to_resume.pdf>

This ensures consistent text extraction and proper handling of LaTeX-formatted PDFs.

2. Initial Assessment

Identify:

  • Candidate's domain (frontend, backend, ML)
  • Experience level (junior: 0-2 years, mid: 3-5 years, senior: 6+ years)
  • Target role type (based on recent experience)
  • Resume format (1-page or 2-page)

3. Technical Content Analysis

Read references/tech_trends.md to understand current technology landscape and evaluation criteria for the identified domain.

Evaluate:

Theme Identification:

  • Primary technical focus areas
  • Technology stack evolution over time
  • Specializations or niche expertise
  • Career trajectory and progression

Company and Impact Analysis:

  • Quality and reputation of companies
  • Scale of systems worked on (users, data volume, traffic)
  • Cross-company skill progression
  • Industry diversity or specialization

Technical Depth:

  • Modern vs. outdated technology usage
  • Alignment with current industry trends
  • Breadth vs. depth of expertise
  • Evidence of continuous learning

Major Contributions:

  • Quantified business impact
  • System design and architecture work
  • Technical leadership indicators
  • Open source or community contributions
  • Cross-functional collaboration

Improvement Opportunities:

  • Missing relevant technologies for target role
  • Weak quantification of impact
  • Lack of leadership/mentoring evidence
  • Outdated technology focus
  • Missing key skills for domain

4. Content Structure and Writing Quality

Read references/writing_quality.md for detailed grammar and style guidelines.

Evaluate:

Section Organization:

  • Logical flow and hierarchy
  • Section completeness (Experience, Skills, Education, etc.)
  • Appropriate emphasis on relevant sections
  • Optimal use of available space

Writing Quality:

  • Action verb usage and strength
  • Tense consistency
  • Conciseness and clarity
  • Grammar and punctuation
  • Parallel structure in lists

Bullet Point Effectiveness:

  • Impact-focused vs. responsibility-focused
  • Specificity and quantification
  • Business value communication
  • Technical detail appropriateness

Formatting Consistency:

  • Date formats
  • Capitalization
  • Punctuation style
  • Technology name casing
  • Number representation

5. ATS Compatibility Analysis

Evaluate:

Structure:

  • Standard section headers
  • Chronological organization
  • Contact information placement
  • Overall layout simplicity

LaTeX-Specific Issues:

  • Multi-column layout problems
  • Special characters or symbols
  • Text extractability (verify with script output)
  • Graphics or custom formatting

Keyword Optimization:

  • Presence of relevant technical keywords
  • Natural keyword integration
  • Acronym definitions
  • Industry-standard terminology

Formatting Risks:

  • Tables or text boxes for critical content
  • Headers/footers with important information
  • Non-standard fonts
  • Complex nested structures

6. Generate Comprehensive Feedback

Structure feedback as follows:

Overall Assessment

  • 2-3 sentence summary of resume strength
  • Primary domain and experience level confirmation
  • Key differentiators or standout qualities

Strengths (What's Good)

  • Specific examples of effective content
  • Well-executed sections or bullet points
  • Strong technical expertise demonstrated
  • Effective quantification or storytelling
  • Good formatting choices

Technical Content Recommendations

  • Missing relevant modern technologies
  • Opportunities to strengthen impact statements
  • Suggestions for better technical positioning
  • Areas to highlight or expand
  • Technologies to add based on target roles

Content Structure and Writing Improvements

  • Grammar or style issues with specific examples
  • Bullet point enhancements with before/after examples
  • Section reorganization suggestions
  • Consistency fixes needed
  • Conciseness improvements

ATS Optimization Recommendations

  • Specific parsing risks identified
  • Keyword additions or improvements
  • Formatting changes for better compatibility
  • Section header standardization

Priority Action Items

  • Rank top 5-7 improvements by impact
  • Quick wins vs. larger rewrites
  • Critical issues vs. nice-to-haves

Output Format

Present feedback in clear, actionable format using markdown headers and bullet points. Use specific examples from the resume when citing issues or strengths. Provide before/after suggestions for concrete improvements.

Be encouraging and constructive while being honest about weaknesses. Frame criticism as opportunities for improvement.

Important Notes

  • Always extract PDF text using the provided script first
  • Consult reference files for domain-specific and writing guidelines
  • Tailor feedback to candidate's experience level and target domain
  • Focus on high-impact improvements first
  • Provide specific, actionable recommendations with examples
  • Consider both ATS parsing and human readability

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

88.73%
按下载量换算717

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills