spip-skills

skill
Guvenlik Denetimi
Uyari
Health Uyari
  • No license — Repository has no license file
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 5 GitHub stars
Code Gecti
  • Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Gecti
  • Permissions — No dangerous permissions requested

Bu listing icin henuz AI raporu yok.

SUMMARY

Claude skills for SPIP

README.md

SPIP Skills

This folder contains local AI skills for SPIP work.

What is a skill?

A skill is a focused knowledge pack used by the coding agent.

  • SKILL.md: entry point loaded first (scope, routing, quick rules)
  • references/: deeper documentation used on demand

In this repository, skills are version-controlled in skills/ and installed to the agent runtime by copying them to ~/.claude/skills/.

Available skills

Skill names are prefixed by scope: spip-* for SPIP core (spip5-* for SPIP 5.0-only skills), plugin-* for one specific plugin.
plugin-escal is the first of that family; other reference plugins will follow.

  • spip-plugins: SPIP plugin development (paquet.xml, pipelines, SQL API, plugin architecture)
  • spip-squelettes: SPIP template work (BOUCLE, #BALISE, criteres, filtres, <INCLURE>)
  • spip-formulaires: SPIP CVT form structure and conventions (HTML wrappers, charger/verifier/traiter, errors)
  • spip-saisies: the Saisies plugin (field types, custom types in saisies/, pipelines, inc/saisies* PHP API)
  • spip-lang: SPIP language files (lang/prefix_XX.php, key naming conventions, _T(), <:module:key:>)
  • spip-logs: SPIP logging practices (spip_log(), journal files, debug workflow)
  • spip-testing: PHPUnit testing of plugins and squelettes (setup, unit tests with mocks, integration tests against a real SPIP)
  • spip-migration-5: migrating SPIP 4.x plugins and squelettes to SPIP 5.0 (listeners, #[AsCronTask], façade Spip::, config/metas, 4.4+5.0 dual compatibility, bin/spip) — requires spip5-plugins
  • spip5-plugins: writing SPIP 5.0 plugins (config/services.php, #[AsPipelineListener] and event classes, #[AsCronTask], injected logger/config, Guard rules, private pages and menus)
  • spip5-instance: running one SPIP 5.0 site (requirements, Composer install and web installer, 4.4 → 5.0 upgrade and rollback, .env* / config/custom.php / spip.* parameters, bin/spip, caches and logs, web server rules, diagnostics)
  • spip-mutualisation-maintenance: SPIP farm inventory, shared updates, backups/rollback, and incident investigation
  • plugin-escal: the Escal squelette (noisettes, escal/config settings, special pages, layouts, technical mots-clés, spip-cli install)

Tested SPIP versions

Skills are written against a tested release, not "the latest": each claim comes from a run or a source read recorded
in docs/tests/. On 2026-11-22 the 4.x skills were audited against the spip/ecrire changelog 4.4.23 → 4.4.31
(docs/tests/spip-4.4.31-audit.md, details in docs/tests/spip-4.4.31-verifications.md; latest 4.4 published that
day: 4.4.31, spip/spip 62485d649, spip/ecrire 5d7078d2).

Skill 4.x facts rechecked on 4.4.31 Earlier reference
spip-plugins autorisation chain, actions and redirects, job queue, cache, secrets, auth pipelines, traitements 4.4.22
spip-squelettes Ajax contexts, sorts, #CACHE, 404 4.4.22
spip-formulaires redirects, traiter() identification, autosave, formulaires/ display 4.4.22
spip-logs masking of sensitive values 4.4.22
spip-testing harness (tests/) and install script 4.4.15
spip-mutualisation-maintenance core upgrade routes, post-upgrade checks 4.4.x (2026-08)
spip-migration-5, spip5-instance 4.4 side (_T(), URL helpers, schema, upgrade rehearsal) 4.4.21–4.4.28
plugin-escal spip-cli install recipe (Escal 5.6.15) 4.4.14
spip-lang, spip-saisies not rechecked (no 4.4.23–4.4.31 change found for them) as recorded in their tests

Only the facts listed were re-run; the rest of each skill keeps its earlier reference.

Install (copy-based)

Run from the repository root.

Linux/macOS:

mkdir -p ~/.claude/skills
cp -R skills/spip* ~/.claude/skills/
cp -R skills/spip-mutualisation-maintenance ~/.claude/skills/

Windows PowerShell:

New-Item -ItemType Directory -Force "$HOME/.claude/skills" | Out-Null
Copy-Item -Recurse -Force "skills/spip*" "$HOME/.claude/skills/"
Copy-Item -Recurse -Force "skills/spip-mutualisation-maintenance" "$HOME/.claude/skills/"

Install (symlink-based)

Run from the repository root.

Linux/macOS:

mkdir -p ~/.claude/skills
for d in skills/spip*; do
	name="$(basename "$d")"
	rm -rf "$HOME/.claude/skills/$name"
	ln -s "$PWD/$d" "$HOME/.claude/skills/$name"
done

Install a plugin skill (plugin-*)

The commands above install the spip* skills, which are the SPIP core baseline and apply to any
site. Skills named plugin-* document one specific plugin and are useless unless that plugin is
installed on the site you work on, so they are installed on demand, one at a time.

Linux/macOS:

cp -R skills/plugin-escal ~/.claude/skills/

Windows PowerShell:

Copy-Item -Recurse -Force "skills/plugin-escal" "$HOME/.claude/skills/"

The symlink loop works the same way with an explicit folder name instead of the skills/spip* glob.

Installation on claude.ai

Custom skill installation is available in Customize > Skills.

  1. Zip your skill folder (the folder containing SKILL.md and any subfolders).
  2. Go to https://claude.ai/customize/skills.
  3. Click +, then + Create skill.
  4. Select Upload a skill.
  5. Upload the ZIP file.
  6. The skill appears in your list and can be enabled or disabled.

Dependencies: spip-migration-5 relies on spip5-plugins for the 5.0 target code, and spip5-plugins relies on
spip5-instance for the console, the environment (.env*, APP_ENV) and the log level. Upload and enable all
three, and update them together.

Important notes:

  • Prerequisite: Code execution and file creation must be enabled in Settings > Capabilities (Free/Pro/Max plans).
  • Privacy: uploaded custom skills are private to your individual account.
  • Supported plans: skills are available on all plans (Free, Pro, Max, Team, Enterprise) and via the API.

Verify installation

Linux/macOS:

ls -la ~/.claude/skills

Windows PowerShell:

Get-ChildItem "$HOME/.claude/skills"

You should see these folders:

  • ~/.claude/skills/spip-plugins
  • ~/.claude/skills/spip-squelettes
  • ~/.claude/skills/spip-formulaires
  • ~/.claude/skills/spip-saisies
  • ~/.claude/skills/spip-lang
  • ~/.claude/skills/spip-logs
  • ~/.claude/skills/spip-testing
  • ~/.claude/skills/spip-migration-5
  • ~/.claude/skills/spip5-plugins
  • ~/.claude/skills/spip5-instance
  • ~/.claude/skills/spip-mutualisation-maintenance

Plus one folder per plugin-* skill you chose to install, for example ~/.claude/skills/plugin-escal.

Optional deeper check (Linux/macOS):

test -f ~/.claude/skills/spip-plugins/SKILL.md && echo "spip-plugins OK"
test -f ~/.claude/skills/spip-squelettes/SKILL.md && echo "spip-squelettes OK"
test -f ~/.claude/skills/spip-formulaires/SKILL.md && echo "spip-formulaires OK"
test -f ~/.claude/skills/spip-saisies/SKILL.md && echo "spip-saisies OK"
test -f ~/.claude/skills/spip-lang/SKILL.md && echo "spip-lang OK"
test -f ~/.claude/skills/spip-logs/SKILL.md && echo "spip-logs OK"
test -f ~/.claude/skills/spip-testing/SKILL.md && echo "spip-testing OK"
test -f ~/.claude/skills/spip-migration-5/SKILL.md && echo "spip-migration-5 OK"
test -f ~/.claude/skills/spip5-plugins/SKILL.md && echo "spip5-plugins OK"
test -f ~/.claude/skills/spip5-instance/SKILL.md && echo "spip5-instance OK"
test -f ~/.claude/skills/spip-mutualisation-maintenance/SKILL.md && echo "spip-mutualisation-maintenance OK"

Optional deeper check (Windows PowerShell):

Test-Path "$HOME/.claude/skills/spip-plugins/SKILL.md"
Test-Path "$HOME/.claude/skills/spip-squelettes/SKILL.md"
Test-Path "$HOME/.claude/skills/spip-formulaires/SKILL.md"
Test-Path "$HOME/.claude/skills/spip-saisies/SKILL.md"
Test-Path "$HOME/.claude/skills/spip-lang/SKILL.md"
Test-Path "$HOME/.claude/skills/spip-logs/SKILL.md"
Test-Path "$HOME/.claude/skills/spip-testing/SKILL.md"
Test-Path "$HOME/.claude/skills/spip-migration-5/SKILL.md"
Test-Path "$HOME/.claude/skills/spip5-plugins/SKILL.md"
Test-Path "$HOME/.claude/skills/spip5-instance/SKILL.md"
Test-Path "$HOME/.claude/skills/spip-mutualisation-maintenance/SKILL.md"

Update workflow

If you used copy-based install

  1. Edit files in skills/<name>/.
  2. Re-copy updated folders to ~/.claude/skills/ (Linux/macOS: cp -R skills/spip* ~/.claude/skills/, PowerShell: Copy-Item -Recurse -Force "skills/spip*" "$HOME/.claude/skills/").
  3. Verify the skill locally.
  4. Commit changes in this repository.

If you used symlink-based install

  1. Edit files in skills/<name>/.
  2. No re-copy needed: symlinks point to your working tree, changes are already reflected.
  3. Verify symlinks and skill files:
ls -l ~/.claude/skills/spip*
test -L ~/.claude/skills/spip-plugins && echo "spip-plugins link OK"
  1. If a new skills/spip* folder was added, run the symlink install loop again to create its link.

Tests (Anthropic skill-creator)

Prerequisites:

  1. Install the plugin in Claude Code:
/plugin install skill-creator

Running evals in Claude Code:

  1. Open the repository (/src/spip) in Claude Code.
  2. Run a natural-language request, for example:
Run evals on my spip-formulaires skill
  1. Repeat the same command for other skills by changing the skill name.

Expected artifacts:

  • skills/<skill>-workspace/iteration-*/benchmark.json
  • skills/<skill>-workspace/iteration-*/benchmark.md
  • skills/<skill>-workspace/iteration-*/review.html

Quick interpretation:

  • benchmark.json: structured results by eval/assertion.
  • benchmark.md: readable summary (baseline vs with_skill, deltas, trends).
  • review.html: detailed report, useful for qualitative review.

Troubleshooting

  • No such file or directory: verify the source path exists in this repository.
  • Existing folder during install: overwrite with cp -R (Linux/macOS) or Copy-Item -Recurse -Force (PowerShell).
  • Skill not picked up: restart the agent session after installation.

Yorumlar (0)

Sonuc bulunamadi