How do I install the Cip Authoring skill?

Run npx skillmds@latest add celestiaorg/cip-authoring 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 Cip Authoring safe to use?

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

Which AI agents work with Cip Authoring?

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 Cip Authoring free to use?

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

Who published Cip Authoring?

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

Cip Authoring by celestiaorg — Agent Skill

Name: Cip Authoring
Author: celestiaorg

File contents

CIP authoring

Use this workflow when a task creates, restructures, or reviews a CIP.

Read the sources

Read cips/cip-001.md for the current CIP process.
Read cips/cip-template.md for the required metadata and sections.
Read one or two nearby CIPs of the same type.
Treat those repository files as authoritative when they differ from this workflow.

Create a proposal

Copy the structure from cips/cip-template.md.
Use XX as the CIP number until an editor assigns a number.
Name the file cip-draft_title_abbrev.md until it receives a number.
Complete each applicable metadata field.
Remove template comments and unused optional fields or sections.
Keep the title at 44 characters or fewer.
Include a substantive Security Considerations section.
Include the CC0 copyright statement.

Edit or review a proposal

Check that:

The metadata matches the document and uses an ISO 8601 creation date.
type and category use values allowed by the template.
requires lists each CIP referenced as a dependency in the specification.
The abstract summarizes the specification without adding requirements.
The motivation explains the problem, while the specification defines the solution precisely enough for interoperable implementations.
Normative key words follow RFC 2119 and RFC 8174 when used.
Parameter changes are summarized and account for CIP-13 when applicable.
Backward compatibility and security consequences are explicit.
Test cases do not introduce requirements absent from the specification.
External resources comply with the CIP process.

Do not silently change technical intent. Flag ambiguity for the author or editor when a safe correction is not clear.

Publish a numbered CIP

When an editor assigns a number:

Rename the file to cips/cip-###.md with three digits.
Replace the draft number in its metadata.
Add the CIP to cips/SUMMARY.md in numeric order.
Add the CIP to the table in cips/README.md.
Update relative references affected by the rename.

Validate

Run:

markdownlint --config .markdownlint.yaml '**/*.md'
mdbook build

Inspect the final diff for unrelated formatting changes and generated files.

---name: cip-authoringdescription: Create or review Celestia Improvement Proposals, including metadata, required sections, numbering, navigation, and repository validation.---# CIP authoringUse this workflow when a task creates, restructures, or reviews a CIP.## Read the sources1. Read `cips/cip-001.md` for the current CIP process.2. Read `cips/cip-template.md` for the required metadata and sections.3. Read one or two nearby CIPs of the same type.4. Treat those repository files as authoritative when they differ from this workflow.## Create a proposal1. Copy the structure from `cips/cip-template.md`.2. Use `XX` as the CIP number until an editor assigns a number.3. Name the file `cip-draft_title_abbrev.md` until it receives a number.4. Complete each applicable metadata field.5. Remove template comments and unused optional fields or sections.6. Keep the title at 44 characters or fewer.7. Include a substantive `Security Considerations` section.8. Include the CC0 copyright statement.## Edit or review a proposalCheck that:- The metadata matches the document and uses an ISO 8601 creation date.- `type` and `category` use values allowed by the template.- `requires` lists each CIP referenced as a dependency in the specification.- The abstract summarizes the specification without adding requirements.- The motivation explains the problem, while the specification defines the solution precisely enough for interoperable implementations.- Normative key words follow RFC 2119 and RFC 8174 when used.- Parameter changes are summarized and account for CIP-13 when applicable.- Backward compatibility and security consequences are explicit.- Test cases do not introduce requirements absent from the specification.- External resources comply with the CIP process.Do not silently change technical intent. Flag ambiguity for the author oreditor when a safe correction is not clear.## Publish a numbered CIPWhen an editor assigns a number:1. Rename the file to `cips/cip-###.md` with three digits.2. Replace the draft number in its metadata.3. Add the CIP to `cips/SUMMARY.md` in numeric order.4. Add the CIP to the table in `cips/README.md`.5. Update relative references affected by the rename.## ValidateRun:```shmarkdownlint --config .markdownlint.yaml '**/*.md'mdbook build```Inspect the final diff for unrelated formatting changes and generated files.

Frequently asked questions

Cip Authoring