Agent skill

Projects Work Management

by sickn33 in sickn33/agentic-awesome-skills

Project register: owner, team, priority, progress percentage, milestones, deliverables and budget against actual cost.

MITAuto-check passedProduct & Project Management

Install Projects Work Management

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill projects-work-management -a claude-code

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

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills projects-work-management --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/projects-work-management .claude/skills/projects-work-management && 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
projects-work-management
GitHub stars
47k
Used in
1 other repo
Token cost
~4.1k tokens
SKILL.md length
1,463 words
Files
1
Skills in repo
1,394
Repo updated
First seen
Licence
MIT

At a glance

Project register: owner, team, priority, progress percentage, milestones, deliverables and budget against actual cost.

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

What it does

Projects Work Management is an agent skill from sickn33/agentic-awesome-skills. Project register: owner, team, priority, progress percentage, milestones, deliverables and budget against actual cost. Use for project tracking.

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

It sits in Product & Project Management, covering Project management. 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.

When your agent uses it

  • Project tracking
  • Tasks that involve Project management

Example prompts

  • “/projects-work-management”

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 1e53ce2. 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:

    • 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

Projects Work Management loads about 4.1k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 1,463 words of instructions outside code blocks.

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

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 1e53ce2, republished under its MIT licence (© sickn33). 1,463 words, ~4,107 tokens.

Download SKILL.mdSave it as .claude/skills/projects-work-management/SKILL.md (or your agent's skills folder).
name
projects-work-management
description
Project register: owner, team, priority, progress percentage, milestones, deliverables and budget against actual cost. Use for project tracking.
category
business
risk
safe
source
self
source_type
self
date_added
2026-09-26
author
WHOISABHISHEKADHIKARI
tags
sme, business, operations, database, csv, notion, sql, operate
source_repo
WHOISABHISHEKADHIKARI/sme-ops-system-builder

Projects & Work Management

What it is: Work delivery.

Overview

Works out the smallest useful Projects & Work Management 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 8: Operate. Fits: Starter stage. Table code: n/a.

When to Use This Skill

  • project tracker
  • work management sheet
  • milestone tracker
  • project database

Also use it when the user says "work delivery", 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 are projects tracked right now?

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.

  • Projects - How many active? / How long? / Who owns each?
  • Work - Tasks or milestones? / Dependencies tracked? / Estimates used?
  • Team - How many people per project? / Allocated by percentage? / Changing often?
  • Current process - What tool today? / Board or spreadsheet? / What is missing?
  • Outcome - What do you need? / A project register, a task view or both?

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: projects-work-management
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Projects": null
  "Work": null
  "Team": 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: Use the project tool people already update for tasks, and keep this as the register of projects, owners, dates and health.

Why this one: Two systems fail at the boundary. If tasks live in a tool, the register should hold only what the tool cannot: ownership, dates and health.

Workflow: Project created → Owner and dates → Tasks tracked → Status review → Closed

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
Project Name,Actual Cost,Budget,Currency,Invoices,Client / Stakeholder,Client Account,Client Satisfaction Score,Deliverables,Department,End Date,Milestones,Notes,Priority,Progress %,Project ID,Project Manager,Project Type,Sprint,Start Date,Status,Team Members
Website Redesign,98000.00,250000.00,INR,"INV-1041, INV-1042",Northwind Traders,Northwind Traders,4,"Wireframes, Build, Launch",Delivery,2026-04-30,"Wireframes, Build, Launch",Client check-in on 12 Feb; scope revisit agreed for March.,Low,60,,Sneha Iyer,Fixed Price,Sprint 3,2026-01-05,Active,"Priya Nair, Rohit Verma"
sql
CREATE TABLE projects_work_management (
  project_name VARCHAR(255),
  actual_cost NUMERIC(14,2) NOT NULL,
  budget NUMERIC(14,2) NOT NULL,
  currency VARCHAR(255),
  invoices VARCHAR(255),  -- relation -> target record
  client_stakeholder VARCHAR(255),
  client_account VARCHAR(255),  -- relation -> target record
  client_satisfaction_score NUMERIC NOT NULL,
  deliverables VARCHAR(255),
  department VARCHAR(255),
  end_date DATE NOT NULL,
  milestones VARCHAR(255),
  notes TEXT,
  priority VARCHAR(100) NOT NULL,
  progress_pct NUMERIC NOT NULL,
  project_id SERIAL PRIMARY KEY,
  project_manager VARCHAR(255),
  project_type VARCHAR(100) NOT NULL,
  sprint VARCHAR(255),
  start_date DATE NOT NULL,
  status VARCHAR(100) NOT NULL,
  team_members VARCHAR(255),
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_projects_work_management_status ON projects_work_management (status);
json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Projects & Work Management",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Project Name": { "type": "string" },
      "Actual Cost": { "type": "number" },
      "Budget": { "type": "number" },
      "Currency": { "type": "string" },
      "Invoices": { "type": "string" },
      "Client / Stakeholder": { "type": "string" },
      "Client Account": { "type": "string" },
      "Client Satisfaction Score": { "type": "number" },
      "Deliverables": { "type": "string" },
      "Department": { "type": "string" },
      "End Date": { "type": "string", "format": "date" },
      "Milestones": { "type": "string" },
      "Notes": { "type": "string" },
      "Priority": { "type": "string" },
      "Progress %": { "type": "number" },
      "Project ID": { "type": "integer" },
      "Project Manager": { "type": "string" },
      "Project Type": { "type": "string" },
      "Sprint": { "type": "string" },
      "Start Date": { "type": "string", "format": "date" },
      "Status": { "type": "string" },
      "Team Members": { "type": "string" }
  },
  "required": [
      "Actual Cost",
      "Budget",
      "Client Satisfaction Score",
      "End Date",
      "Priority",
      "Progress %",
      "Project Type",
      "Start Date",
      "Status"
  ]
}
markdown
| CSV column | Notion property | Set after import |
|---|---|---|
| Project Name | Title | Use as the database title |
| Actual Cost | Number (format: currency) | Convert to Number, set format to Currency |
| Budget | Number (format: currency) | Convert to Number, set format to Currency |
| Currency | Text | Leave as Text |
| Invoices | Relation (link to the target database) | Convert to Relation, link to the target database |
| Client / Stakeholder | Text | Leave as Text |
| Client Account | Relation (link to the target database) | Convert to Relation, link to the target database |
| Client Satisfaction Score | Number | Convert to Number |
| Deliverables | Text | Leave as Text |
| Department | Text | Leave as Text |
| End Date | Date | Convert to Date |
| Milestones | Text | Leave as Text |
| Notes | Text | Leave as Text |
| Priority | Select (add options after import) | Convert to Select, add options: "Low", "Medium", "High", "Urgent" |
| Progress % | Number | Convert to Number |
| Project ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
| Project Manager | Text | Leave as Text |
| Project Type | Select (add options after import) | Convert to Select, add options: "Fixed Price", "Time and Material", "Retainer", "Internal" |
| Sprint | Text | Leave as Text |
| Start Date | Date | Convert to Date |
| Status | Select (add options after import) | Convert to Select, add options: "Planning", "Active", "On Hold", "Completed", "Cancelled" |
| Team Members | 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

#FieldTypeSQLJSON SchemaNotionCSV example
1Project NametextVARCHAR(255)stringTextWebsite Redesign
2Actual CostcurrencyNUMERIC(14,2)numberNumber (format: currency)98000.00
3BudgetcurrencyNUMERIC(14,2)numberNumber (format: currency)250000.00
4CurrencytextVARCHAR(255)stringTextINR
5InvoicesrelationVARCHAR(255)stringRelation (link to the target database)INV-1041, INV-1042
6Client / StakeholdertextVARCHAR(255)stringTextNorthwind Traders
7Client AccountrelationVARCHAR(255)stringRelation (link to the target database)Northwind Traders
8Client Satisfaction ScorenumberNUMERICnumberNumber4
9DeliverablestextVARCHAR(255)stringTextWireframes, Build, Launch
10DepartmenttextVARCHAR(255)stringTextDelivery
11End DatedateDATEstring, format: dateDate2026-04-30
12MilestonestextVARCHAR(255)stringTextWireframes, Build, Launch
13Noteslong_textTEXTstringTextClient check-in on 12 Feb; scope revisit agreed for March.
14PriorityselectVARCHAR(100)stringSelect (add options after import)Low
15Progress %numberNUMERICnumberNumber60
16Project IDidSERIAL PRIMARY KEYintegerText (preserve source ID)(blank)
17Project ManagertextVARCHAR(255)stringTextSneha Iyer
18Project TypeselectVARCHAR(100)stringSelect (add options after import)Fixed Price
19SprinttextVARCHAR(255)stringTextSprint 3
20Start DatedateDATEstring, format: dateDate2026-01-05
21StatusselectVARCHAR(100)stringSelect (add options after import)Active
22Team MemberstextVARCHAR(255)stringTextPriya Nair, Rohit Verma
Show full SKILL.md (498 more words)Show less

Select Options

Priority

Low | Medium | High | Urgent

Project Type

Fixed Price | Time and Material | Retainer | Internal

Status

Planning | Active | On Hold | Completed | Cancelled

Relations

Link fields: Invoices, Client Account

Examples

Prompt

Project status is asked for in chat every week.

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

Q: How many active? A: Six.

Q: Tool today? A: A task board, used inconsistently.

Q: Estimates? A: Rarely.

Recommended next step - offered, not built:

Use the project tool people already update for tasks, and keep this as the register of projects, owners, dates and health.

Workflow: Project created → Owner and dates → Tasks tracked → Status review → Closed

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 schedule people, replace a project tool or manage dependencies automatically.
  • 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.
  • Module Catalog - find the relevant module, then read its skill.
  • @people-directory - the employee master record most modules link to.
  • @notification-reminder-hub - turns due dates in this module into reminders.

Reusable Prompt

I want to set up work delivery 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/projects-work-management of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 1e53ce2

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

Projects Work Management 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.

Projects Work Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Projects Work Management this skillsickn33/agentic-awesome-skills47k1 repos~4.1kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Uvastral-sh/claude-code-plugins3142 repos~980Automated safety check: PassApache-2.0
Project Managementkunchenguid/firstmate7.6k—~2.1kAutomated safety check: PassMIT
Hivemind Goalsactiveloopai/hivemind1.6k—~1.7kAutomated safety check: NotesApache-2.0
Ichartjswanghetommy/ichartjs352—~3.4kAutomated safety check: PassApache-2.0

Similar skills

  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Uv

    astral-sh/claude-code-plugins

    Official

    Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.

    314 GitHub starsUsed in 2 repos~980 tokens
    Product & Project ManagementAuto-check passed
  • Project Management

    kunchenguid/firstmate

    Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.

    7.6k GitHub stars~2.1k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Hivemind Goals

    activeloopai/hivemind

    Create, track and update team goals via the Deeplake virtual filesystem at memory/goal/.

    1.6k GitHub stars~1.7k tokensUpdated 9 days ago
    Product & Project ManagementAuto-check: notes
  • Ichartjs

    wanghetommy/ichartjs

    Plan, validate, render, explain, and safely edit iChart.js visualizations from tabular, project, or diagram data.

    352 GitHub stars~3.4k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Hivemind Goals

    activeloopai/hivemind

    Create, track and update team goals in Hivemind via the hivemind CLI.

    1.6k GitHub stars~814 tokensUpdated 9 days ago
    Product & Project ManagementAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,394 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 Projects Work Management

What does Projects Work Management do?

Project register: owner, team, priority, progress percentage, milestones, deliverables and budget against actual cost. Projects Work Management is an agent skill from sickn33/agentic-awesome-skills. Project register: owner, team, priority, progress percentage, milestones, deliverables and budget against actual cost.

When should I use Projects Work Management?

Projects Work Management fits situations like: project tracking; tasks that involve Project management.

How do I install Projects Work Management in Claude Code?

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

How do I install Projects Work Management in Codex?

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

Can I use Projects Work Management 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 projects-work-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/projects-work-management, .gemini/skills/projects-work-management, .github/skills/projects-work-management and .opencode/skills/projects-work-management in your project.

What does Projects Work Management need to run?

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

Does Projects Work Management access the network?

SKILL.md names 1 domain. In commands or code: json-schema.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Projects Work Management 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 Projects Work Management use?

Projects Work Management 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 Projects Work Management use?

About 4.1k tokens (SKILL.md is roughly 16k 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 Projects Work Management?

Skills that share tags, products or a category with Projects Work Management: CCPM Project Management (automazeio/ccpm, 8.4k stars), Uv (astral-sh/claude-code-plugins, 314 stars), Project Management (kunchenguid/firstmate, 7.6k stars) and Hivemind Goals (activeloopai/hivemind, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Projects Work Management?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 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.