Cowork Hiring Screener logo

Cowork Hiring Screener

Organization
OneWave-AI
cowork-hiring-screener

Point Cowork at a folder of resumes plus a job description -- screens every candidate against the actual requirements, produces a ranked shortlist with evidence, drafts advance/decline emails, and builds interview kits for the top picks. Pairs with hiring-scorecard for the interview stage.

Overview

PublisherOneWave-AI
Repositoryclaude-skills
Skill namecowork-hiring-screener
Stars
293
Forks
49
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by OneWave-AI on GitHub. Read the source before you install it.

Installation

Install the Cowork Hiring Screener AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git /tmp/claude-skills
mkdir -p .claude/skills
cp -r /tmp/claude-skills/cowork-hiring-screener .claude/skills/cowork-hiring-screener
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cowork Hiring Screener in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cowork Hiring Screener on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cowork Hiring Screener is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Cowork Hiring Screener

Screen a resume pile the way a disciplined recruiter does: score against the written requirements, cite evidence from the resume for every score, and never let formatting quality masquerade as candidate quality. Input is a folder of resumes (PDF, .docx, text) and a job description; output is a defensible shortlist.

Workflow

  1. Extract requirements. Parse the JD into must-haves, nice-to-haves, and disqualifiers. Present the rubric for approval before scoring -- the human may reweight. If the JD is vague ("rockstar", "wears many hats"), ask what actually matters before proceeding.
  2. Inventory. Catalog every file in the folder. Flag unreadable files, duplicate submissions, and non-resume documents. Report the candidate count before starting.
  3. Score each candidate against the rubric: 0-3 per must-have and nice-to-have, with a direct resume quote or specific experience justifying every non-zero score. No quote, no points.
  4. Rank and tier. Produce screening-report.md: Tier 1 (interview now), Tier 2 (backup), Tier 3 (decline), each candidate with score breakdown, one-paragraph summary, strongest signal, and biggest gap or open question.
  5. Draft communications. Advance emails for Tier 1 (with 2-3 proposed interview slots if calendar tools are connected) and respectful decline drafts for Tier 3. Drafts only -- never send.
  6. Interview kits. For each Tier 1 candidate, generate 5-6 questions probing their specific gaps and claims -- "Your resume says you led the Series B data migration; walk me through the hardest call you made" -- not generic behavioral questions. Hand off to hiring-scorecard for structured interview evaluation.

Rules

  • Score the content, not the polish. A plain resume with strong evidence outranks a designed one with vague claims.
  • Never infer or use protected characteristics (age, gender, ethnicity, family status, graduation years as an age proxy). Score skills and experience only.
  • Distinguish "did the thing" from "was near the thing." "Led migration" and "team migrated during my tenure" are different scores.
  • Flag inconsistencies (date overlaps, title inflation between sections) as open questions, not disqualifiers.
  • Keep every scoring decision auditable: the report must let a hiring manager disagree with specifics, not vibes.
  • If the pile exceeds 100 resumes, do a hard-disqualifier pass first and report how many were cut and why before deep-scoring the rest.

Quick Commands

  • "Screen [folder] against [JD]" -- full workflow
  • "Just the rubric" -- step 1 only, for approval
  • "Top 5 only" -- deep-score and report only the strongest candidates
  • "Draft the declines" -- Tier 3 communication drafts

Frequently asked questions

What does the Cowork Hiring Screener AI skill do?

Point Cowork at a folder of resumes plus a job description -- screens every candidate against the actual requirements, produces a ranked shortlist with evidence, drafts advance/decline emails, and builds interview kits for the top picks. Pairs with hiring-scorecard for the interview stage.

Why use Cowork Hiring Screener on TypingMind?

Because you install it once and use it with any model. Cowork Hiring Screener is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cowork Hiring Screener in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/OneWave-AI/claude-skills/tree/main/cowork-hiring-screener. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Cowork Hiring Screener?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cowork Hiring Screener?

As many as you like. As long as a model supports skills, you can use Cowork Hiring Screener with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cowork Hiring Screener AI skill free?

Yes. It is published on GitHub by OneWave-AI under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇