Agent skill

People Directory

by sickn33 in sickn33/agentic-awesome-skills

Employee master record: name, employee id, department, job title, grade, manager, employment type, contact and emergency details, access role, start and end dates, status.

MITAuto-check passed

Install People Directory

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill people-directory -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills people-directory --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/people-directory .claude/skills/people-directory && rm -rf skills-src

Use ~/.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/

Facts

Skill name
people-directory
GitHub stars
47k
Used in
1 other repo
Token cost
~4.5k tokens
SKILL.md length
1,549 words
Files
1
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

Employee master record: name, employee id, department, job title, grade, manager, employment type, contact and emergency details, access role, start and end dates, status.

  • Works in 5 steps: Identify intent → Ask only what is missing → Hold the internal context → …
  • SKILL.md covers Overview, When to Use This Skill, How It Works and Field Reference, plus 9 more sections
  • Reaches linkedin.com and json-schema.org

What it does

People Directory is an agent skill from sickn33/agentic-awesome-skills. Employee master record: name, employee id, department, job title, grade, manager, employment type, contact and emergency details, access role, start and end dates, status. Use for people records.

Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

Example prompts

  • “/people-directory”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify intent
  2. Ask only what is missing
  3. Hold the internal context
  4. Recommend the smallest workflow
  5. Build only on request

What it can do on your machine

Read from SKILL.md and the folder at commit b84d35a. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, csv, sql, json and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • linkedin.com
    • json-schema.org

    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

People Directory loads about 4.5k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 1,549 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~4.5k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 1,549 words, ~4,495 tokens.

Download SKILL.mdSave it as .claude/skills/people-directory/SKILL.md (or your agent's skills folder).
name
people-directory
description
Employee master record: name, employee id, department, job title, grade, manager, employment type, contact and emergency details, access role, start and end dates, status. Use for people records.
category
business
risk
safe
source
self
source_type
self
date_added
2026-09-26
author
WHOISABHISHEKADHIKARI
tags
sme, business, operations, database, csv, notion, sql, onboard
source_repo
WHOISABHISHEKADHIKARI/sme-ops-system-builder

People Directory

What it is: Employee master data.

Overview

Works out the smallest useful People Directory setup for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on request, from one field list so they cannot drift apart.

Layer: Layer 3: Onboard. Fits: Starter stage. Table code: n/a.

When to Use This Skill

  • employee directory
  • people directory template
  • employee master data
  • staff database

Also use it when the user says "employee master data", or describes the same process happening in a spreadsheet, a document or someone inboxes.

Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

  • "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
  • "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
  • "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
  • "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: How many people are in the company today?

Step 2 - Ask only what is missing

Skip anything the user already answered, in any earlier message. Ask the rest one at a time, and stop as soon as the remaining answers would not change the output.

  • People - How many people? / Full time, part time, contractors? / Any remote?
  • Data - Store salary on it? / Store emergency contacts? / What is sensitive?
  • Structure - Reporting lines? / Grades or bands? / Locations?
  • Current process - Where is the list now? / HR system or spreadsheet? / How stale is it?
  • Outcome - What do you need? / A directory, a master record or reporting?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless they ask, and it never carries a value the user did not give.

yaml
module: people-directory
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "People": null
  "Data": null
  "Structure": null
  "Current process": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking
Step 4 - Recommend the smallest workflow

If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.

Recommended approach: One person record per human, with the sensitive fields separated out. Most modules should link to it, not duplicate it.

Why this one: A people directory is the root record. If it is wrong, leave, assets, payroll and reviews are all wrong, so it is worth doing properly once.

Workflow: Joiner → Person record → Links to other modules → Change → Exit record

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the requested artifacts. For machine-readable text, keep prose outside the data; for files, provide a usable link. Report material validation failures or limitations separately.

A selected Notion output is rendered by notion-manual-import, so route the Notion step there. When the user selects Notion, hand that step to @notion-manual-import: it holds the CSV, the property mapping, the import steps and the verification checklist, and it renders the Field Reference below instead of defining a table of its own. Do not restate the mapping here and do not improvise the import steps. Manual CSV and mapping outputs need no connection. For requested workspace changes, follow the shared contract: verify actual tool access and the target before writing. A user saying "connected" is not tool evidence. Never ask for a Notion password or token.

For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the text correctly. A CSV is not an .xlsx workbook; create .xlsx only when the user requests a workbook. A CSV carries no types, so after it, name the columns that need a number, date or currency format applied.

csv
Full Name,Annual CTC,Currency,Date of Birth,Department,Email,Accounts,Emergency Contact,Emergency Phone,Employee ID,Employment Type,End Date,Grade Level,KPIs,Job Title,Access Role,LinkedIn,Manager,Nationality,Notes,Phone,Probation Status,Profile Photo URL,Skills,Start Date,Status,Time Zone,Work Location
Aarav Sharma,1200000.00,INR,1991-04-18,Delivery,aarav.sharma@example.com,"Payroll portal, HRIS",Anil Sharma,+91 98xxxxxx34,,Full Time,2027-03-31,L1,On-time delivery %,Delivery Manager,Line manager,https://linkedin.com/in/aarav-sharma-example,Sneha Iyer,Indian,Joined from a competitor; notice period is one month.,+91 98xxxxxx21,Passed,https://example.com/photo.jpg,"Excel, SQL, Client Handling",2021-03-08,Active,IST (UTC+5:30),Bengaluru
sql
CREATE TABLE people_directory (
  full_name VARCHAR(255),
  annual_ctc NUMERIC(14,2) NOT NULL,
  currency VARCHAR(255),
  date_of_birth DATE NOT NULL,
  department VARCHAR(255),
  email VARCHAR(255),
  accounts VARCHAR(255),
  emergency_contact VARCHAR(255),
  emergency_phone VARCHAR(255),
  employee_id SERIAL PRIMARY KEY,
  employment_type VARCHAR(100) NOT NULL,
  end_date DATE,
  grade_level VARCHAR(100) NOT NULL,
  kpis VARCHAR(255),
  job_title VARCHAR(255),
  access_role VARCHAR(255),
  linkedin TEXT,
  manager VARCHAR(255),
  nationality VARCHAR(255),
  notes TEXT,
  phone VARCHAR(255),
  probation_status VARCHAR(100) NOT NULL,
  profile_photo_url TEXT,
  skills VARCHAR(255),
  start_date DATE NOT NULL,
  status VARCHAR(100) NOT NULL,
  time_zone VARCHAR(255),
  work_location VARCHAR(255),
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_people_directory_status ON people_directory (status);
json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "People Directory",
  "type": "object",
  "additionalProperties": false,
  "properties": {
    "Full Name": {
      "type": "string"
    },
    "Annual CTC": {
      "type": "number"
    },
    "Currency": {
      "type": "string"
    },
    "Date of Birth": {
      "type": "string",
      "format": "date"
    },
    "Department": {
      "type": "string"
    },
    "Email": {
      "type": "string",
      "format": "email"
    },
    "Accounts": {
      "type": "string"
    },
    "Emergency Contact": {
      "type": "string"
    },
    "Emergency Phone": {
      "type": "string"
    },
    "Employee ID": {
      "type": "integer"
    },
    "Employment Type": {
      "type": "string"
    },
    "End Date": {
      "type": "string",
      "format": "date"
    },
    "Grade Level": {
      "type": "string"
    },
    "KPIs": {
      "type": "string"
    },
    "Job Title": {
      "type": "string"
    },
    "Access Role": {
      "type": "string"
    },
    "LinkedIn": {
      "type": "string",
      "format": "uri"
    },
    "Manager": {
      "type": "string"
    },
    "Nationality": {
      "type": "string"
    },
    "Notes": {
      "type": "string"
    },
    "Phone": {
      "type": "string"
    },
    "Probation Status": {
      "type": "string"
    },
    "Profile Photo URL": {
      "type": "string",
      "format": "uri"
    },
    "Skills": {
      "type": "string"
    },
    "Start Date": {
      "type": "string",
      "format": "date"
    },
    "Status": {
      "type": "string"
    },
    "Time Zone": {
      "type": "string"
    },
    "Work Location": {
      "type": "string"
    }
  },
  "required": [
    "Annual CTC",
    "Date of Birth",
    "Employment Type",
    "Grade Level",
    "Probation Status",
    "Start Date",
    "Status"
  ]
}
markdown
| CSV column | Notion property | Set after import |
|---|---|---|
| Full Name | Title | Use as the database title |
| Annual CTC | Number (format: currency) | Convert to Number, set format to Currency |
| Currency | Text | Leave as Text |
| Date of Birth | Date | Convert to Date |
| Department | Text | Leave as Text |
| Email | Email | Convert to Email |
| Accounts | Text | Leave as Text |
| Emergency Contact | Text | Leave as Text |
| Emergency Phone | Text | Leave as Text |
| Employee ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
| Employment Type | Select (add options after import) | Convert to Select, add options: "Full Time", "Part Time", "Contract", "Intern", "Consultant" |
| End Date | Date | Convert to Date |
| Grade Level | Select (add options after import) | Convert to Select, add options: "L1", "L2", "L3", "L4", "L5", "M1", "M2" |
| KPIs | Text | Leave as Text |
| Job Title | Text | Leave as Text |
| Access Role | Text | Leave as Text |
| LinkedIn | URL | Convert to URL |
| Manager | Text | Leave as Text |
| Nationality | Text | Leave as Text |
| Notes | Text | Leave as Text |
| Phone | Text | Leave as Text |
| Probation Status | Select (add options after import) | Convert to Select, add options: "Not Started", "In Progress", "Passed", "Failed", "Extended" |
| Profile Photo URL | URL | Convert to URL |
| Skills | Text | Leave as Text |
| Start Date | Date | Convert to Date |
| Status | Select (add options after import) | Convert to Select, add options: "Active", "On Leave", "Notice Period", "Exited" |
| Time Zone | Text | Leave as Text |
| Work Location | Text | Leave as Text |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date, and anything pointing at another table stays relation.

Field Reference

End Date may be absent before the relevant lifecycle stage or when no verified source exists. Do not invent values to satisfy a schema.

#FieldTypeSQLJSON SchemaNotionCSV example
1Full NametextVARCHAR(255)stringTextAarav Sharma
2Annual CTCcurrencyNUMERIC(14,2)numberNumber (format: currency)1200000.00
3CurrencytextVARCHAR(255)stringTextINR
4Date of BirthdateDATEstring, format: dateDate1991-04-18
5DepartmenttextVARCHAR(255)stringTextDelivery
6EmailemailVARCHAR(255)string, format: emailEmailaarav.sharma@example.com
7AccountstextVARCHAR(255)stringTextPayroll portal, HRIS
8Emergency ContacttextVARCHAR(255)stringTextAnil Sharma
9Emergency PhonetextVARCHAR(255)stringText+91 98xxxxxx34
10Employee IDidSERIAL PRIMARY KEYintegerText (preserve source ID)(blank)
11Employment TypeselectVARCHAR(100)stringSelect (add options after import)Full Time
12End DatedateDATEstring, format: dateDate2027-03-31
13Grade LevelselectVARCHAR(100)stringSelect (add options after import)L1
14KPIstextVARCHAR(255)stringTextOn-time delivery %
15Job TitletextVARCHAR(255)stringTextDelivery Manager
16Access RoletextVARCHAR(255)stringTextLine manager
17LinkedInurlTEXTstring, format: uriURLhttps://linkedin.com/in/aarav-sharma-example
18ManagertextVARCHAR(255)stringTextSneha Iyer
19NationalitytextVARCHAR(255)stringTextIndian
20Noteslong_textTEXTstringTextJoined from a competitor; notice period is one month.
21PhonetextVARCHAR(255)stringText+91 98xxxxxx21
22Probation StatusselectVARCHAR(100)stringSelect (add options after import)Passed
23Profile Photo URLurlTEXTstring, format: uriURLhttps://example.com/photo.jpg
24SkillstextVARCHAR(255)stringTextExcel, SQL, Client Handling
25Start DatedateDATEstring, format: dateDate2021-03-08
26StatusselectVARCHAR(100)stringSelect (add options after import)Active
27Time ZonetextVARCHAR(255)stringTextIST (UTC+5:30)
28Work LocationtextVARCHAR(255)stringTextBengaluru
Show full SKILL.md (505 more words)Show less

Select Options

Employment Type

Full Time | Part Time | Contract | Intern | Consultant

Grade Level

L1 | L2 | L3 | L4 | L5 | M1 | M2

Probation Status

Not Started | In Progress | Passed | Failed | Extended

Status

Active | On Leave | Notice Period | Exited

Relations

Link fields: none

Examples

Prompt

Our employee list lives in three spreadsheets and none agree.

Context first - one question per message, nothing already answered:

Q: Store salary on it? A: Yes, HR only.

Q: Remote? A: Half the team.

Q: Where is it now? A: Three spreadsheets.

Recommended next step - offered, not built:

One person record per human, with the sensitive fields separated out. Most modules should link to it, not duplicate it.

Workflow: Joiner → Person record → Links to other modules → Change → Exit record

Want the CSV, SQL, JSON Schema and Notion mapping for this?

Best Practices

  • Build when requested; recommend and offer a build for advice-only requests.
  • One question per message. A batched intake reads as a form and gets guessed at.
  • Keep display names identical across CSV and JSON; document normalized SQL identifiers.
  • Use relation for anything that points at another table, text only for free text.
  • Money fields are currency, never text. Dates are date, never free text.
  • If the user requests an example row, keep it obviously fake so nobody imports it as real data.

Limitations

  • Empty template only. It does not compute payroll, tax, leave balances or KPIs.
  • Notion relations need both databases imported before the link column resolves.
  • Select options are a starting set. Rename them to match how the business talks.
  • No automation, reminders or sync. Those need the integration layer.
  • Does not hold payroll, tax or banking data. It references those, it does not own them.
  • Legal, tax and HR review is still required before this drives real decisions.

Security & Safety Notes

  • Never fill in real names, salaries, medical or banking data. Placeholders only.
  • Label example rows as synthetic, and keep bank details masked.
  • Local reads, generation commands, and validation are part of a requested artifact build. External writes, messages, provisioning, and publication require authorization for that action and target; existing explicit authorization does not need to be repeated.
  • If sensitive data is supplied, avoid repeating unnecessary identifiers. Use only what the requested review needs; keep generated templates empty. Do not claim deletion from the conversation or service storage.
  • Privacy, legal and disciplinary cases need a qualified human reviewer before anything is acted on.

Common Pitfalls

  • Problem: a static mapping is described as a completed workspace build. Solution: deliver manual mappings without a connection; claim a live change only after the authorized tool operation succeeds.
  • Problem: asked all six questions in one message. Solution: ask one, wait, and drop any the first answer already covered.
  • Problem: built a full system when one table was asked for. Solution: build what was requested; mention the parent skill separately.
  • Problem: all four artifacts drift apart. Solution: derive all four from the field list in this file, never by hand.
  • Problem: Notion import shows every column as Text. Solution: that is expected. Apply the property mapping table once, after import.

Reusable Prompt

I want to set up employee master data for my company.
Ask me one short question at a time, and only about what I have not already told you.
Then recommend the smallest setup that fits, and wait for me to ask before you build it.
When I ask, output CSV, SQL DDL, JSON Schema, a Notion property mapping or an Excel workbook. Data only.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/people-directory of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit b84d35a

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

People Directory 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.

People Directory compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
People Directory this skillsickn33/agentic-awesome-skills47k1 repos~4.5kAutomated safety check: PassMIT
Job Search With A Recordmohitagw15856/pm-claude-skills1.4k—~1.3kAutomated safety check: PassMIT
Recordingcodewhale-hq/Codewhale41k—~540Automated safety check: PassMIT
Technical Job Searchgithub/awesome-copilot40k—~1.2kAutomated safety check: PassMIT
Job Application AssistantMadsLorentzen/ai-job-search45k—~1.2kAutomated safety check: NotesMIT
Job Application Managerreactive-resume/reactive-resume44k—~13kAutomated safety check: PassMIT

Similar skills

  • Job Search With A Record

    mohitagw15856/pm-claude-skills

    Run a job search when you have a criminal record — where to apply, when and how to disclose, and how to turn the question into a short, confident answer instead of a dealbreaker.

    1.4k GitHub stars~1.3k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed
  • Recording

    codewhale-hq/Codewhale

    Capture screenshots on registered computers, record on macOS or HarmonyOS, and manage saved captures.

    41k GitHub stars~540 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Technical Job Search

    github/awesome-copilot

    Official

    A skill your agent uses when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV/resume, writing a cover letter, evaluating a job offer…

    40k GitHub stars~1.2k tokensUpdated 2 days ago
    Business, Finance & HRAuto-check passed
  • Job Application Assistant

    MadsLorentzen/ai-job-search

    Evaluates job postings against your profile, then tailors a LaTeX CV and cover letter and prepares interview answers for the roles you pursue.

    45k GitHub stars~1.2k tokensUpdated 2 days ago
    Business, Finance & HRAuto-check: notes
  • Job Application Manager

    reactive-resume/reactive-resume

    Runs the job-search pipeline. An agent skill from reactive-resume/reactive-resume.

    44k GitHub stars~13k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed
  • Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README.

    276k GitHub starsUsed in 4 repos~1.8k tokens
    DevelopmentAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,497 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about People Directory

What does People Directory do?

Employee master record: name, employee id, department, job title, grade, manager, employment type, contact and emergency details, access role, start and end dates, status. People Directory is an agent skill from sickn33/agentic-awesome-skills. Employee master record: name, employee id, department, job title, grade, manager, employment type, contact and emergency details, access role, start and end dates, status.

How do I install People Directory in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill people-directory -a claude-code`. Or copy the skill folder (skills/people-directory in sickn33/agentic-awesome-skills) into .claude/skills/people-directory in your project. Claude Code loads it when a task matches its description.

How do I install People Directory in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill people-directory -a codex`. Or copy the skill folder (skills/people-directory in sickn33/agentic-awesome-skills) into .agents/skills/people-directory in your project. Codex loads it when a task matches its description.

Can I use People Directory 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 sickn33/agentic-awesome-skills --skill people-directory -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/people-directory, .gemini/skills/people-directory, .github/skills/people-directory and .opencode/skills/people-directory in your project.

What does People Directory need to run?

SKILL.md names no scripts, command-line tools or credentials: People Directory is instructions for the agent only.

Does People Directory access the network?

SKILL.md names 2 domains. In commands or code: linkedin.com and json-schema.org; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is People Directory 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. Review the folder before installing.

What licence does People Directory use?

People Directory 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 People Directory use?

About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to People Directory?

Skills that share tags, products or a category with People Directory: Job Search With A Record (mohitagw15856/pm-claude-skills, 1.4k stars), Recording (codewhale-hq/Codewhale, 41k stars), Technical Job Search (github/awesome-copilot, 40k stars) and Job Application Assistant (MadsLorentzen/ai-job-search, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains People Directory?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.