How do I install the Project Profile skill?

Run npx skillmds@latest add telum-ai/project-profile in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Project Profile safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Project Profile?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Project Profile free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Project Profile?

telum-ai (@telum-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Project Profile by telum-ai — Agent Skill

Name: Project Profile
Rating: 4.2 (5 reviews)
Author: telum-ai

File contents

project-profile

Input: $ARGUMENTS (--claim <state> when proving readiness). Registry: [PROJECT_DIR]/project.md → ## PROFILE surfaces.

1. Read before mutation

Read .speck/templates/project/readme-template.md, the active project.md PROFILE table, product-contract.md §1, and the existing root README.md. Every retained registry row is binding; delete a non-applicable row instead of leaving a decorative placeholder.

2. Refresh safe managed surfaces

Run .speck/scripts/regenerate-project-readme.sh to refresh the README footer, placeholders, and explicit AUTO-SYNC blocks while preserving user prose.
For a declared package adapter, run .speck/scripts/regenerate-project-readme.sh --surface=package. It may fill only an empty or placeholder description; user-owned drift remains a finding.
Do not rewrite file surfaces or the remote github description. Route product-surface copy changes through the owning story or project adjustment; remote mutation remains an owner/external gesture.

3. Prove every declared surface

bash .speck/scripts/profile-drift-check.sh [--claim <state>]

The checker reads the registry rather than a fixed surface list. It must emit one result per retained row plus PROFILE_DRIFT_SUMMARY. A required missing, unreachable, or severely divergent surface is PROFILE_DRIFT.P1; do not collapse it into README green.

At SHIP-RC+, also run:

bash .speck/scripts/validation/validators/validate-readme.sh --strict

4. Continue

Surface blocking drift and its exact readiness cap. Then resume the canonical flow in root AGENTS.md at the first incomplete applicable slot.

Rules

Treat README as PROFILE's center of gravity, never its full extent.
Never overwrite user prose, a landing surface, package prose already owned by the user, or remote metadata to manufacture alignment.
Never pass a readiness claim while any registry row required by that state has PROFILE_DRIFT.P1.

---name: project-profiledescription: Refreshes declared PROFILE surfaces. Use after product-contract changes before evidence-contract or when drift appears.---# project-profileInput: `$ARGUMENTS` (`--claim <state>` when proving readiness).Registry: `[PROJECT_DIR]/project.md` → `## PROFILE surfaces`.## 1. Read before mutationRead `.speck/templates/project/readme-template.md`, the active `project.md` PROFILE table, `product-contract.md` §1, and the existing root `README.md`. Every retained registry row is binding; delete a non-applicable row instead of leaving a decorative placeholder.## 2. Refresh safe managed surfaces1. Run `.speck/scripts/regenerate-project-readme.sh` to refresh the README footer, placeholders, and explicit AUTO-SYNC blocks while preserving user prose.2. For a declared `package` adapter, run `.speck/scripts/regenerate-project-readme.sh --surface=package`. It may fill only an empty or placeholder description; user-owned drift remains a finding.3. Do not rewrite `file` surfaces or the remote `github` description. Route product-surface copy changes through the owning story or project adjustment; remote mutation remains an owner/external gesture.## 3. Prove every declared surface```bashbash .speck/scripts/profile-drift-check.sh [--claim <state>]```The checker reads the registry rather than a fixed surface list. It must emit one result per retained row plus `PROFILE_DRIFT_SUMMARY`. A required missing, unreachable, or severely divergent surface is `PROFILE_DRIFT.P1`; do not collapse it into README green.At SHIP-RC+, also run:```bashbash .speck/scripts/validation/validators/validate-readme.sh --strict```## 4. ContinueSurface blocking drift and its exact readiness cap. Then resume the canonical flow in root `AGENTS.md` at the first incomplete applicable slot.## Rules- Treat README as PROFILE's center of gravity, never its full extent.- Never overwrite user prose, a landing surface, package prose already owned by the user, or remote metadata to manufacture alignment.- Never pass a readiness claim while any registry row required by that state has `PROFILE_DRIFT.P1`.

Frequently asked questions

Project Profile