Cpn Documentation
A Claude skill from shikanime-labs/skills.
Install
$ agentstack add skill-shikanime-labs-skills-cpn-documentation ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
cloud-pi-native Documentation
Conventions
- Documentation is written in French.
- VitePress admonition syntax:
:::tip,:::warning,:::dangerblocks. - Role mapping tables use the Console → GitLab correspondence format (see
references/role-mappings.md).
Admonition Usage
| Severity | Syntax | When to use | | -------- | ------------ | ---------------------------------------------------------------- | | Info | :::tip | Helpful but non-critical guidance | | Warning | :::warning | Temporary limitations, retrocompat phases, upcoming deprecations | | Danger | :::danger | Breaking changes, data loss risk, irreversible behavior |
Framing Rules
- Retrocompat / legacy phases: frame as intentional temporary behavior for
compatibility, not as a bug to fix. Use wording like "Phase de rétrocompatibilité" or "conservé temporairement pour compatibilité".
- Breaking changes: state the concrete impact (what gets deleted,
overwritten, or stops working) and the mechanism (trigger, sync cycle, etc.).
- Always note the version scope (e.g.,
9.16.x) and the intended future
evolution.
Key Locations
| File | Content | | ------------------------------ | -------------------------------------------------------------- | | docs/guide/roles.md | Project roles — user-facing role management and GitLab mapping | | docs/administration/roles.md | Platform roles — admin reference, plugin config keys |
Pitfalls
- Do not frame retrocompat behavior as a "bug" or "defect". The user corrected
this: use "phase de rétrocompatibilité" — it is intentional and temporary.
- When adding admonitions near examples or screenshots, place them before
the example so readers see the warning before encountering the illustration.
See also
references/role-mappings.md— Console → GitLab role correspondence tables
and version-scoped notes
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: shikanime-labs
- Source: shikanime-labs/skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.