Agent skill

Generate Project Skill

by skilld-dev in skilld-dev/skilld

Generate or update an Agent Skill from the observed workflows, boundaries, and conventions of one software project.

MITAuto-check: notesDevelopment

Install Generate Project Skill

skills CLI
$ npx skills add skilld-dev/skilld --skill generate-project-skill -a claude-code

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

GitHub CLI
$ gh skill install skilld-dev/skilld generate-project-skill --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/skilld-dev/skilld.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/generate-project-skill .claude/skills/generate-project-skill && 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
generate-project-skill
GitHub stars
319
Token cost
~1.1k tokens
SKILL.md length
656 words
Files
2 (incl. assets)
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Generate or update an Agent Skill from the observed workflows, boundaries, and conventions of one software project.

  • Works in 6 steps: Read project instructions and decision… → Read manifests, exported entry points,… → Find the test, lint, typecheck, build,… → …
  • Tasks that involve Project scaffolding
  • SKILL.md covers Inputs, Inspect, Project navigation and Output, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Generate Project Skill is an agent skill from skilld-dev/skilld. Generate or update an Agent Skill from the observed workflows, boundaries, and conventions of one software project.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including assets (for example `assets/harness-request.md`).

It sits in Development, covering Project scaffolding. The repository describes itself as: Open-source, privacy friendly skills.sh alternative for humans and agents. The licence is MIT.

When your agent uses it

  • Tasks that involve Project scaffolding

Example prompts

  • “/generate-project-skill”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Read project instructions and decision records first.
  2. Read manifests, exported entry points, and build configuration.
  3. Find the test, lint, typecheck, build, and release commands.
  4. Trace the main public workflows through their real entry points.
  5. Note generated directories and files an Agent must not edit.
  6. Check recent changes when they explain current conventions.

What it can do on your machine

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

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

  • Network

    Links to these hosts (documentation or services it may open):

    • agentskills.io

    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

Generate Project Skill loads about 1.1k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 656 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~1.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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:46
    - credential files, such as `.env` and any private key

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 skilld-dev/skilld at commit 1ef8101, republished under its MIT licence (© skilld-dev). 656 words, ~1,150 tokens.

Download SKILL.mdSave it as .claude/skills/generate-project-skill/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
generate-project-skill
description
Generate or update an Agent Skill from the observed workflows, boundaries, and conventions of one software project.

Generate a project Skill

Create a compact, searchable Skill from the project itself. This Skill is for maintainers who author a draft Skill they own.

Inputs

Use the project directory or prepared project source. Ask for the destination only when the request does not provide one.

Inspect

  1. Read project instructions and decision records first.
  2. Read manifests, exported entry points, and build configuration.
  3. Find the test, lint, typecheck, build, and release commands.
  4. Trace the main public workflows through their real entry points.
  5. Note generated directories and files an Agent must not edit.
  6. Check recent changes when they explain current conventions.

Project navigation

The Skill must let an Agent find any part of the project without a prior index.

  1. Name the project from its manifest. Use the directory name when no manifest names it.
  2. List the entry points the manifest declares, such as main, module, types, exports, and bin.
  3. List the source and documentation directories an Agent reads most.
  4. Use project-relative paths for every file pointer.
  5. Never add a generated directory prefix to a project-relative path.
  6. Give search commands the Agent can repeat, scoped to those directories.
  7. Prefer rg for search. Name the directories to skip in the command.
  8. Tell the Agent when project changes require a new Skill run.

Write the search commands so their results point at real project files.

Skip these paths while collecting project files:

  • version-control data, such as .git
  • dependency directories, such as node_modules and vendor
  • generated output, such as dist, build, target, .output, .nuxt, and .next
  • caches and reports, such as coverage
  • credential files, such as .env and any private key

Skip any file larger than 512 KB. Do not follow symbolic links while collecting project files.

Output

Write one directory whose name matches the Skill name. The directory must contain SKILL.md. Use references/ for architecture details and command guides. Use scripts/ only for reusable automation.

The SKILL.md frontmatter must contain only name and description. Use lowercase letters, numbers, and single hyphens in the name. Keep the name at 64 characters or fewer.

Show full SKILL.md (305 more words)Show less

Cross-Agent portability

Keep one source Skill for Claude Code, Codex, Gemini CLI, and other compatible Agents. Their discovery paths differ. Keep installation instructions outside the generated Skill. The Agent Skills specification defines the shared format.

  • Describe capabilities, such as reading files or running a command, instead of provider-specific tool names.
  • Ask for inputs explicitly. Do not require $ARGUMENTS, dynamic context injection, hooks, or a specific subagent API.
  • State the project root as the working directory for project commands. Resolve bundled references and scripts from the Skill directory instead.
  • Name required runtimes, binaries, network access, and credentials beside the step that needs them.
  • If a required capability is unavailable, report the missing capability and stop that dependent step. Never invent evidence or silently skip a required check.

Check one matching task, one unrelated task, and one missing-input task. Use a fresh session for each Agent the user asks to support when those Agents are available. Record the Agent version, model, task, observed output, and any required permission. Separate format validation, discovery, activation, and task completion in the report. If an Agent is unavailable, report that path untested. Valid frontmatter alone does not prove portability.

Quality checks

  • Describe when the Skill applies.
  • Do not explain the language, framework, or tools. The reader already knows them.
  • Use project terms exactly.
  • Point to source files instead of copying them.
  • Run project commands only when they add useful evidence.
  • Record the observed command and outcome.
  • Include repeatable search commands for project source and documentation.
  • Keep file pointers rooted at the real project directory.
  • Separate rules from optional guidance.
  • Remove stale, inferred, or duplicated instructions.
  • Link each reference from SKILL.md.

For a direct run, show the generated files for user review. Do not replace an existing Skill until the user approves it. Do not claim that the Skill passed Harness checks.

© skilld-dev, 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 1 other file (assets) in skills/generate-project-skill of skilld-dev/skilld.

  • SKILL.md
  • assets/harness-request.md

Open the folder on GitHubat commit 1ef8101

Compare with similar skills

Generate Project Skill 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.

Generate Project Skill compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Generate Project Skill this skillskilld-dev/skilld319—~1.1kAutomated safety check: NotesMIT
Nx Generatenomcopter/react-mosaic4.8k7 repos~1.9kAutomated safety check: PassCustom licence
PonytailDavidObando/gsharp5658 repos~1.7kAutomated safety check: PassMIT
Run Nx Generatornrwl/nx29k2 repos~592Automated safety check: NotesMIT
Conductor Setupgemini-cli-extensions/conductor3.8k—~4.2kAutomated safety check: PassApache-2.0
Mirage VFS Adapter Authoringstrukto-ai/mirage3.7k—~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • Nx Generate

    nomcopter/react-mosaic

    Generate code using nx generators. An agent skill from nomcopter/react-mosaic.

    4.8k GitHub starsUsed in 7 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Ponytail

    DavidObando/gsharp

    Forces the laziest solution that actually works, simplest, shortest, most minimal.

    565 GitHub starsUsed in 8 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Run Nx generators with prioritization for workspace-plugin generators.

    29k GitHub starsUsed in 2 repos~592 tokens
    DevelopmentAuto-check: notes
  • Conductor Setup

    gemini-cli-extensions/conductor

    Scaffolds the project and sets up the Conductor environment.

    3.8k GitHub stars~4.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Builds or extends a custom Mirage virtual filesystem adapter for an API, database, object store or app data, with a working mount configuration and filesystem tests.

    3.7k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Enforces this repository's TypeScript backend module architecture under server/: feature folders, barrel exports, and where shared types and utilities belong.

    14k GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

More from skilld-dev/skilld

  • Generate Package Skill

    skilld-dev/skilld

    Generate or update an Agent Skill that teaches consumers one npm or local package the user maintains, including framework modules and wrappers.

    319 GitHub stars~3.2k tokensUpdated today
    Auto-check passed
  • Update Package Skill

    skilld-dev/skilld

    Updates an existing package Skill for a new release of its npm or local package by testing only what changed since the version the Skill names.

    319 GitHub stars~992 tokensUpdated today
    Auto-check passed
  • Skilld

    skilld-dev/skilld

    Operate skilld CLI for Skill discovery, use, installation, inspection, updates, authentication, configuration, restoration, and removal, including Repository, curator, and collection refs.

    319 GitHub stars~5.3k tokensUpdated today
    Auto-check passed
  • Review Skill

    skilld-dev/skilld

    Review an Agent Skill for valid structure, clear triggers, usable instructions, current evidence, and risky or unclear actions.

    319 GitHub stars~648 tokensUpdated today
    Auto-check passed

Categories

Questions about Generate Project Skill

What does Generate Project Skill do?

Generate or update an Agent Skill from the observed workflows, boundaries, and conventions of one software project. Generate Project Skill is an agent skill from skilld-dev/skilld. Generate or update an Agent Skill from the observed workflows, boundaries, and conventions of one software project.

When should I use Generate Project Skill?

Generate Project Skill fits situations like: tasks that involve Project scaffolding.

How do I install Generate Project Skill in Claude Code?

Run `npx skills add skilld-dev/skilld --skill generate-project-skill -a claude-code`. Or copy the skill folder (skills/generate-project-skill in skilld-dev/skilld) into .claude/skills/generate-project-skill in your project. Claude Code loads it when a task matches its description.

How do I install Generate Project Skill in Codex?

Run `npx skills add skilld-dev/skilld --skill generate-project-skill -a codex`. Or copy the skill folder (skills/generate-project-skill in skilld-dev/skilld) into .agents/skills/generate-project-skill in your project. Codex loads it when a task matches its description.

Can I use Generate Project Skill 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 skilld-dev/skilld --skill generate-project-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/generate-project-skill, .gemini/skills/generate-project-skill, .github/skills/generate-project-skill and .opencode/skills/generate-project-skill in your project.

What does Generate Project Skill need to run?

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

Does Generate Project Skill access the network?

SKILL.md names 1 domain. As links in the text: agentskills.io. This is read from the text; nothing was executed.

Is Generate Project Skill safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Generate Project Skill use?

Generate Project Skill 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 Generate Project Skill use?

About 1.1k tokens (SKILL.md is roughly 4.6k 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 Generate Project Skill?

Skills that share tags, products or a category with Generate Project Skill: Nx Generate (nomcopter/react-mosaic, 4.8k stars), Ponytail (DavidObando/gsharp, 565 stars), Run Nx Generator (nrwl/nx, 29k stars) and Conductor Setup (gemini-cli-extensions/conductor, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Generate Project Skill?

skilld-dev (a GitHub organization) maintains it in skilld-dev/skilld, which has 319 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

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