light-software-copyright
Prepare China software copyright registration material drafts from a real software project: application-field worksheet, source-code deposit material, user/operation manual, screenshots when needed, consistency checks and local formal-output evidence. Use for 软著, 软件著作权, 软件版权登记, source-code page extraction, operation manual drafts, version/name consistency, or pre-submit review. This off-DAG engineering/IP handoff skill does not provide legal advice, does not submit applications, does not guarantee registration, and never fabricates source code.
npx skills add Light0305/Light-skills --skill light-software-copyright --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Software copyright materials Prepare auditable China software copyright material drafts from a real project. The core job is not “write pretty documents”; it is to keep software name, version, source-code material, manual, screenshots, applicant fields and user confirmations consistent enough for the user or professional service provider to review. Read [`references/software-copyright-resource-map.md`](references/software-copyright-resource-map.md) before current-rule or material-format work. Read [`references/materials-workflow.md`](references/materials-workflow.md) before source-code selection, business-understanding, rights-basis, third-party-code or formal-output work. ## Non-negotiable boundaries 1. This skill is not legal advice and never submits applications or claims the material will pass. It prepares local drafts and review evidence only. 2. Code material must come from real project source files. Never invent, rewrite, pad, or AI-generate source code for deposit. 3. Do not expose secrets. Run or request a secret/privacy scan before exporting source-code material; if secrets are present, stop for redaction strategy. 4. Preserve official-rule uncertainty. If the current C
- Non-negotiable boundaries
- Workflow
- 1. Intake and scope
- 2. Bind to a real source snapshot and deposit plan
- 3. Confirm application fields and business understanding
- 4. Prepare code and document material
- 5. Generate local drafts, then formal outputs
- 6. Run the machine gate before saying “ready for review”
- ACT / ASK / NEVER
python scripts/source_deposit_plan.py --root <project-root> --out 软件著作权申请资料/草稿/source-deposit-plan.json --software-name "<软件全称>" --version "<版本号>" python scripts/source_deposit_plan.py --selftest python scripts/materials_gate.py --packet software-copyright-materials.json --base <project-root> --as-of 2026-07-05 python scripts/materials_gate.py --selftest
What does the light-software-copyright skill do?
Prepare China software copyright registration material drafts from a real software project: application-field worksheet, source-code deposit material, user/operation manual, screenshots when needed, consistency checks and local formal-output evidence. Use for 软著, 软件著作权, 软件版权登记, source-code page extraction, operation manual drafts, version/name consistency, or pre-submit review. This off-DAG engineering/IP handoff skill does not provide legal advice, does not submit applications, does not guarantee registration, and never fabricates source code.
How do I install it?
Run `npx skills add Light0305/Light-skills --skill light-software-copyright --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Light0305/Light-skills, a repository with 505 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.