New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Staticphp Documentation Sync

by crazywhalecc in crazywhalecc/static-php-cli

Synchronize bilingual documentation when StaticPHP v3 user-facing or developer-facing documentation must change.

MITAuto-check passedDevelopment

Install Staticphp Documentation Sync

skills CLI
$ npx skills add crazywhalecc/static-php-cli --skill staticphp-documentation-sync -a claude-code

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

GitHub CLI
$ gh skill install crazywhalecc/static-php-cli staticphp-documentation-sync --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/crazywhalecc/static-php-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/staticphp-documentation-sync .claude/skills/staticphp-documentation-sync && 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
staticphp-documentation-sync
GitHub stars
1.9k
Token cost
~2.2k tokens
SKILL.md length
676 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Synchronize bilingual documentation when StaticPHP v3 user-facing or developer-facing documentation must change.

  • Works in 5 steps: Identify Impact Scope → Read Current Docs → Update English Docs First → …
  • Removing documented features
  • SKILL.md covers Overview, When to Use This Skill, Documentation Map and Workflow, plus 2 more sections
  • Calls npm

What it does

Staticphp Documentation Sync is an agent skill from crazywhalecc/static-php-cli. Synchronize bilingual documentation when StaticPHP v3 user-facing or developer-facing documentation must change. Use when adding, modifying, deprecating, or removing documented features, CLI commands/options, environment variables, configuration formats, public APIs/extension points, workflows, installation requirements, migration guidance, or user-visible behavior. Do not use solely for internal implementation changes, package/library additions, or build bug fixes unless they change documented behavior or…

Its SKILL.md is about 2.2k 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 Development, covering Translation, Debugging and Secrets management. It works with PHP. The repository describes itself as: Build standalone portable PHP binaries on Linux, macOS, Windows, with PHP project together, with popular extensions included. The licence is MIT.

When your agent uses it

  • Removing documented features
  • CLI commands/options
  • Environment variables
  • Configuration formats

Example prompts

  • “/staticphp-documentation-sync”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify Impact Scope
  2. Read Current Docs
  3. Update English Docs First
  4. Sync Chinese Docs
  5. Validate

What it can do on your machine

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

    Shell commands in SKILL.md call:

    • npm

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

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    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

Staticphp Documentation Sync loads about 2.2k tokens when it runs. Until then it costs about 143 tokens; SKILL.md has 676 words of instructions outside code blocks.

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

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 crazywhalecc/static-php-cli at commit f60c636, republished under its MIT licence (© crazywhalecc). 676 words, ~2,235 tokens.

Download SKILL.mdSave it as .claude/skills/staticphp-documentation-sync/SKILL.md (or your agent's skills folder).
name
staticphp-documentation-sync
description
Synchronize bilingual documentation when StaticPHP v3 user-facing or developer-facing documentation must change. Use when adding, modifying, deprecating, or removing documented features, CLI commands/options, environment variables, configuration formats, public APIs/extension points, workflows, installation requirements, migration guidance, or user-visible behavior. Do not use solely for internal implementation changes, package/library additions, or build bug fixes unless they change documented behavior or require updating existing docs.

StaticPHP Documentation Sync

Overview

StaticPHP maintains bilingual documentation under docs/en/ (English) and docs/zh/ (Chinese). User-facing or developer-facing documentation changes must be reflected in both languages. Use this skill to identify affected docs, update them in sync, and validate sidebar/config consistency.

When to Use This Skill

Invoke this skill when the change involves:

  • New or modified CLI commands, options, or arguments
  • New or changed environment variables
  • Package (extension/library/target/tool) additions, removals, or behavioral changes that affect documented support, dependencies, commands, or workflows
  • Configuration format changes (YAML fields, artifact definitions, registry)
  • Build lifecycle, doctor, or toolchain changes
  • API or extension point changes (attributes, hooks, DI, custom artifacts)
  • Workflow changes (installation, first build, migration)
  • Deprecation or removal of any documented feature

Do not update docs just because code changed. Internal refactors, new libraries used only as dependencies, package build fixes, CI-only changes, and bug fixes that preserve documented behavior usually do not need documentation changes. If existing docs mention the changed behavior, command, package support, dependency, caveat, or workaround, update them.

Documentation Map

docs/
├── en/                          # English docs (canonical source)
│   ├── index.md                 # Home page hero/features
│   ├── guide/                   # User-facing guides
│   │   ├── index.md             # Overview
│   │   ├── installation.md      # Installation instructions
│   │   ├── first-build.md       # First build walkthrough
│   │   ├── sapi-reference.md    # PHP SAPI options
│   │   ├── cli-reference.md     # CLI commands and options
│   │   ├── cli-generator.md     # Build command generator
│   │   ├── migrate-from-v2.md   # v2 → v3 migration
│   │   ├── extensions.md        # Supported extensions list
│   │   ├── extension-notes.md   # Per-extension notes
│   │   ├── env-vars.md          # Environment variables
│   │   ├── deps-map.md          # Dependency map
│   │   └── troubleshooting.md   # Troubleshooting guide
│   ├── develop/                 # Developer docs
│   │   ├── index.md             # Dev overview
│   │   ├── structure.md         # Project structure
│   │   ├── registry.md          # Registry model
│   │   ├── package-model.md     # Package YAML model
│   │   ├── artifact-model.md    # Artifact YAML model
│   │   ├── craft-yml.md         # craft.yml reference
│   │   ├── build-lifecycle.md   # Build stages/lifecycle
│   │   ├── system-build-tools.md # System tool requirements
│   │   ├── doctor-module.md     # Doctor module
│   │   ├── php-src-changes.md   # PHP source patches
│   │   └── extending/           # Extension authoring
│   │       ├── index.md
│   │       ├── package-classes.md
│   │       ├── annotations.md
│   │       ├── lifecycle-hooks.md
│   │       ├── dependency-injection.md
│   │       └── custom-artifact.md
│   ├── contributing/
│   │   └── index.md
│   └── faq/
│       └── index.md
├── zh/                          # Chinese docs (mirrors en/ structure)
│   └── (same structure as en/)
├── .vitepress/
│   ├── sidebar.en.ts            # English sidebar config
│   ├── sidebar.zh.ts            # Chinese sidebar config
│   └── config.ts                # VitePress site config
└── deps-craft-yml.md            # Shared craft.yml include used by both languages

Other documentation files outside this tree may also matter, especially root-level ext-support.md.

Key rule: docs/en/ and docs/zh/ have identical file trees. Every .md file under en/ must have a corresponding file under zh/.

Workflow

Step 1: Identify Impact Scope

Map the change to affected documentation:

Change TypeLikely Affected Docs
New/removed CLI commandguide/cli-reference.md, guide/cli-generator.md
New/removed CLI optionguide/cli-reference.md, guide/first-build.md
New env varguide/env-vars.md
New/removed documented extension packageguide/extensions.md, guide/extension-notes.md, guide/deps-map.md, root ext-support.md
Package config field changedevelop/package-model.md, develop/artifact-model.md
Build lifecycle changedevelop/build-lifecycle.md
Doctor changedevelop/doctor-module.md, develop/system-build-tools.md
New attribute/hook/DIdevelop/extending/annotations.md, develop/extending/lifecycle-hooks.md, develop/extending/dependency-injection.md
PHP source patchdevelop/php-src-changes.md
Registry changedevelop/registry.md
Install/setup changeguide/installation.md, guide/first-build.md
Deprecation/removalAll docs referencing the feature
New doc pagesidebar.en.ts, sidebar.zh.ts
Step 2: Read Current Docs

Before editing, read BOTH the English and Chinese versions of each affected file to understand the current content and existing translation patterns.

bash
# Example: check both language versions of the CLI reference
cat docs/en/guide/cli-reference.md
cat docs/zh/guide/cli-reference.md
Step 3: Update English Docs First
  1. Update docs/en/ files with accurate, complete English content.
  2. Follow existing formatting conventions (headings, code blocks, tables, admonitions).
  3. If adding a new page:
    • Create the file under docs/en/<category>/<name>.md
    • Add the corresponding entry in docs/.vitepress/sidebar.en.ts
    • Ensure the file has proper VitePress frontmatter if needed
Show full SKILL.md (315 more words)Show less
Step 4: Sync Chinese Docs
  1. Update docs/zh/ files to match the English changes.
  2. Translate all changed or added prose. Do not leave placeholder text or untranslated English in Chinese docs.
  3. Match the structure and formatting of the English version exactly.
  4. If a new page was added in English, create the corresponding docs/zh/ file and update docs/.vitepress/sidebar.zh.ts.
  5. Treat docs/deps-craft-yml.md as a special shared include for both languages. If it needs prose changes, either keep the shared content acceptable for both languages or split the included content before adding language-specific prose.
Step 5: Validate

Run these checks before considering the task complete:

bash
# Check that en/ and zh/ have matching file trees
diff <(find docs/en -name '*.md' | sed 's|docs/en/||' | sort) \
     <(find docs/zh -name '*.md' | sed 's|docs/zh/||' | sort)

# Check that all sidebar links point to existing files
# (manual check: every 'link' in sidebar.*.ts must resolve to an actual .md file)

# Build docs when Node dependencies are available; this catches many broken links/config issues
npm run docs:build

Translation Guidelines

  • Chinese docs must be complete: Every section, paragraph, and table in the English docs must have a Chinese equivalent. Never skip sections.
  • Code blocks and command examples: Keep executable code and commands identical in both languages. Translate surrounding prose; translate comments inside examples only when they are explanatory docs rather than copy-pasteable source/config.
  • Technical terms: Use consistent translations. Refer to existing Chinese docs for established term translations. When in doubt, prefer the term used elsewhere in docs/zh/.
  • Links: Internal links in Chinese docs should point to /zh/... paths (not /en/...).
  • YAML frontmatter: Keep frontmatter identical between languages (layout, etc.) unless the title/tagline field is translated.

Common Pitfalls

  • Don't update only one language: This is the most common mistake. Always update both en/ and zh/ in the same change.
  • Don't forget sidebar configs: When adding, renaming, or removing doc pages, update both sidebar.en.ts and sidebar.zh.ts.
  • Don't forget shared/root docs: root ext-support.md and docs/deps-craft-yml.md are also documentation. Update them if relevant.
  • Don't leave TODO markers: Do not commit TODO translation placeholders unless the user explicitly allows it or the task is blocked; if that happens, call it out in the final response.
  • Don't translate file paths or URLs: Only translate human-readable content, not paths, URLs, command names, or code identifiers.

© crazywhalecc, 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 .agents/skills/staticphp-documentation-sync of crazywhalecc/static-php-cli.

Open the folder on GitHubat commit f60c636

Compare with similar skills

Staticphp Documentation Sync 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.

Staticphp Documentation Sync compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Staticphp Documentation Sync this skillcrazywhalecc/static-php-cli1.9k—~2.2kAutomated safety check: PassMIT
Security Reviewgithub/awesome-copilot40k1 repos~2.3kAutomated safety check: NotesMIT
Wp Interactivity APIAutomattic/agent-skills2112 repos~1.5kAutomated safety check: PassNone
Extension Puppeteer Debuggingmengxi-ream/read-frog10k—~2kAutomated safety check: NotesGPL-3.0
I18n Lang FilesMes-Open/OpenMes150—~1.1kAutomated safety check: PassAGPL-3.0
Wp PlaygroundAutomattic/agent-skills2111 repos~1.2kAutomated safety check: PassNone

Similar skills

  • Security Review

    github/awesome-copilot

    Official

    AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching…

    40k GitHub starsUsed in 1 repo~2.3k tokens
    SecurityAuto-check: notes

  • Wp Interactivity API

    Automattic/agent-skills

    A skill your agent uses when building or debugging WordPress Interactivity API features (data-wp- directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration…

    211 GitHub starsUsed in 2 repos~1.5k tokens
    DevelopmentAuto-check passed

  • Extension Puppeteer Debugging

    mengxi-ream/read-frog

    Debug the built Read Frog extension in real Chrome. An agent skill from mengxi-ream/read-frog.

    10k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check: notes

  • I18n Lang Files

    Mes-Open/OpenMes

    Editing or merging backend/lang/en.json and pl.json. An agent skill from Mes-Open/OpenMes.

    150 GitHub stars~1.1k tokensUpdated 3 days ago
    Frontend & DesignAuto-check passed

  • Wp Playground

    Automattic/agent-skills

    A skill your agent uses for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting…

    211 GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed

  • Debugging Marchat

    Cod-e-Codes/marchat

    Diagnoses marchat client and server issues using -doctor, env configuration, and logs.

    137 GitHub stars~668 tokensUpdated 4 days ago
    DevelopmentAuto-check: notes

More from crazywhalecc/static-php-cli

  • Staticphp Build Troubleshooting

    crazywhalecc/static-php-cli

    Diagnose StaticPHP v3 failures. An agent skill from crazywhalecc/static-php-cli.

    1.9k GitHub stars~814 tokensUpdated today
    Auto-check passed

  • Staticphp Package Maintenance

    crazywhalecc/static-php-cli

    Maintain StaticPHP v3 packages and artifacts. An agent skill from crazywhalecc/static-php-cli.

    1.9k GitHub stars~1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Staticphp Documentation Sync

What does Staticphp Documentation Sync do?

Synchronize bilingual documentation when StaticPHP v3 user-facing or developer-facing documentation must change. Staticphp Documentation Sync is an agent skill from crazywhalecc/static-php-cli. Synchronize bilingual documentation when StaticPHP v3 user-facing or developer-facing documentation must change.

When should I use Staticphp Documentation Sync?

Staticphp Documentation Sync fits situations like: removing documented features; CLI commands/options; environment variables; configuration formats.

How do I install Staticphp Documentation Sync in Claude Code?

Run `npx skills add crazywhalecc/static-php-cli --skill staticphp-documentation-sync -a claude-code`. Or copy the skill folder (.agents/skills/staticphp-documentation-sync in crazywhalecc/static-php-cli) into .claude/skills/staticphp-documentation-sync in your project. Claude Code loads it when a task matches its description.

How do I install Staticphp Documentation Sync in Codex?

Run `npx skills add crazywhalecc/static-php-cli --skill staticphp-documentation-sync -a codex`. Or copy the skill folder (.agents/skills/staticphp-documentation-sync in crazywhalecc/static-php-cli) into .agents/skills/staticphp-documentation-sync in your project. Codex loads it when a task matches its description.

Can I use Staticphp Documentation Sync 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 crazywhalecc/static-php-cli --skill staticphp-documentation-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/staticphp-documentation-sync, .gemini/skills/staticphp-documentation-sync, .github/skills/staticphp-documentation-sync and .opencode/skills/staticphp-documentation-sync in your project.

What does Staticphp Documentation Sync need to run?

Going by SKILL.md and its folder, Staticphp Documentation Sync needs the command-line tools its instructions call (npm).

Does Staticphp Documentation Sync access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Staticphp Documentation Sync 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 Staticphp Documentation Sync use?

Staticphp Documentation Sync 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 Staticphp Documentation Sync use?

About 2.2k tokens (SKILL.md is roughly 8.9k 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 Staticphp Documentation Sync?

Skills that share tags, products or a category with Staticphp Documentation Sync: Security Review (github/awesome-copilot, 40k stars), Wp Interactivity API (Automattic/agent-skills, 211 stars), Extension Puppeteer Debugging (mengxi-ream/read-frog, 10k stars) and I18n Lang Files (Mes-Open/OpenMes, 150 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Staticphp Documentation Sync?

crazywhalecc (a GitHub user) maintains it in crazywhalecc/static-php-cli, which has 1,949 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

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