How do I install the Pre Publish Checker skill?

Run npx skillmds@latest add gemini-cli-extensions/pre-publish-checker 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 Pre Publish Checker 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 Pre Publish Checker?

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 Pre Publish Checker free to use?

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

Who published Pre Publish Checker?

gemini-cli-extensions (@gemini-cli-extensions) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pre Publish Checker by gemini-cli-extensions

Name: Pre Publish Checker
Author: gemini-cli-extensions

Pre Publish Checker

🐉 Thoroughly checks files for profanity, internal links, sensitive paths, and professionalism before publication. Use when preparing a codebase or extension for public release.

File contents

Pre-Publish Checker

This skill guides you through a thorough audit of your project to ensure it meets publication standards. It combines automated script-based checks with a manual review workflow.

Policies

Do Not Simply Remove TODOs: Do not delete TODO markers just to make the check pass. Instead:
- Action them: Resolve the task described.
- Move them: Transfer the TODO to a tracking system (e.g., GitHub Issues) and replace the marker with a link to the issue.
User Bypass: Any flagged issue can be bypassed if there is a valid reason. In PUBLICATION_CHECKLIST.md, mark the status as [Pass] and include the keyword USER_BYPASS: <explanation>.

Workflow

1. Initialization

List all relevant files: Markdown (.md), code files (.py, .js, .go, etc.), justfile, and READMEs.
Create a PUBLICATION_CHECKLIST.md in the project root by copying the template from references/checklist_template.md.
Populate the file list in the checklist.

2. Automated Audit

For each file in the checklist, run the automated check script:

uv run -s skills/pre-publish-checker/scripts/check_file.py <file_path>

Note: If uv is not available, use python3.

3. Iterative Review

Process files one by one (or in small batches).
Update the PUBLICATION_CHECKLIST.md with the status and any issues found.
Fix issues as they are identified.
For "long work", you can resume the process by reading the current state of PUBLICATION_CHECKLIST.md.
Get a Synopsis: At any point, you can generate a quick summary of remaining work by running:
```
uv run -s skills/pre-publish-checker/scripts/summarize_checklist.py
```
(Defaults to reading PUBLICATION_CHECKLIST.md)

4. Final Verification

Perform manual checks for "Google-bar professionalism" and overall quality.
Ensure all boxes in PUBLICATION_CHECKLIST.md are checked.

Check Categories

Profanity: Scans for common offensive language.
Internal Links: Finds internal shortlinks (e.g., go/ links) which are not accessible outside.
Internal Paths: Identifies local machine or company-specific paths that reveal internal infrastructure.
Professionalism: Checks for development markers (e.g., "to-do", "fix-me") that should be resolved before release.

---name: pre-publish-checkerdescription: 🐉 Thoroughly checks files for profanity, internal links, sensitive paths, and professionalism before publication. Use when preparing a codebase or extension for public release.---# Pre-Publish CheckerThis skill guides you through a thorough audit of your project to ensure it meets publication standards. It combines automated script-based checks with a manual review workflow.## Policies1. **Do Not Simply Remove TODOs**: Do not delete `TODO` markers just to make the check pass. Instead:  * **Action them**: Resolve the task described. * **Move them**: Transfer the `TODO` to a tracking system (e.g., GitHub Issues) and replace the marker with a link to the issue. 2. **User Bypass**: Any flagged issue can be bypassed if there is a valid reason. In `PUBLICATION_CHECKLIST.md`, mark the status as `[Pass]` and include the keyword `USER_BYPASS: <explanation>`.## Workflow### 1. Initialization- List all relevant files: Markdown (.md), code files (.py, .js, .go, etc.), `justfile`, and `README`s.- Create a `PUBLICATION_CHECKLIST.md` in the project root by copying the template from `references/checklist_template.md`.- Populate the file list in the checklist.### 2. Automated AuditFor each file in the checklist, run the automated check script:```bashuv run -s skills/pre-publish-checker/scripts/check_file.py <file_path>```*Note: If `uv` is not available, use `python3`.*### 3. Iterative Review- Process files one by one (or in small batches).- Update the `PUBLICATION_CHECKLIST.md` with the status and any issues found.- Fix issues as they are identified.- For "long work", you can resume the process by reading the current state of `PUBLICATION_CHECKLIST.md`.- **Get a Synopsis**: At any point, you can generate a quick summary of remaining work by running: ```bash uv run -s skills/pre-publish-checker/scripts/summarize_checklist.py ``` *(Defaults to reading `PUBLICATION_CHECKLIST.md`)*### 4. Final Verification- Perform manual checks for "Google-bar professionalism" and overall quality.- Ensure all boxes in `PUBLICATION_CHECKLIST.md` are checked.## Check Categories1. **Profanity**: Scans for common offensive language.2. **Internal Links**: Finds internal shortlinks (e.g., `go/` links) which are not accessible outside.3. **Internal Paths**: Identifies local machine or company-specific paths that reveal internal infrastructure.4. **Professionalism**: Checks for development markers (e.g., "to-do", "fix-me") that should be resolved before release.

Frequently asked questions