New: 98,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

China Software Copyright Materials

by Light0305 in Light0305/Light-skills

Prepares draft materials for a China software copyright registration from a real project: application worksheet, source deposit plan, operation manual and consistency checks.

MITAuto-check passedLegal & Compliance

Install China Software Copyright Materials

skills CLI
$ npx skills add Light0305/Light-skills --skill light-software-copyright -a claude-code

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

GitHub CLI
$ gh skill install Light0305/Light-skills light-software-copyright --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/Light0305/Light-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/light-software-copyright .claude/skills/light-software-copyright && 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
light-software-copyright
GitHub stars
641
Token cost
~1.9k tokens
SKILL.md length
863 words
Files
6 (incl. scripts, references)
Skills in repo
23
Repo updated
First seen
Licence
MIT

At a glance

Prepares draft materials for a China software copyright registration from a real project: application worksheet, source deposit plan, operation manual and consistency checks.

  • Works in 6 steps: Intake and scope → Bind to a real source snapshot and… → Confirm application fields and business… → …
  • Assembling source-code deposit pages from a project for copyright registration
  • SKILL.md covers Non-negotiable boundaries, Workflow and ACT / ASK / NEVER
  • Runs Python scripts from its folder; calls python

What it does

The skill drafts auditable registration materials and keeps the software name, version, source-code material, manual, screenshots and applicant fields consistent, so you or a service provider can review them. It begins with intake, marking unknowns, and stops for your confirmation before formal documents are produced. Source material is bound to a real snapshot: each selected file is recorded with its relative path, SHA-256 and reason, and build artifacts, minified bundles, vendored dependencies and lock files are excluded by default.

Firm limits apply. It is not legal advice, never submits an application or promises approval, never invents or pads source code, and requires a secret and privacy scan before exporting code, stopping for a redaction plan if secrets appear. When the current rules of the China Copyright Protection Center are not verified that day, it records UNKNOWN or PLANNED. Helpers include scripts/materials_gate.py and scripts/source_deposit_plan.py, a JSON template for the materials, and two reference files on workflow and rules.

When your agent uses it

  • Assembling source-code deposit pages from a project for copyright registration
  • Drafting the user or operation manual that accompanies an application
  • Checking name and version consistency across all registration documents
  • Reviewing the material set before submission

Example prompts

  • “Prepare the software copyright worksheet and source deposit plan for this repository.”
  • “Draft the operation manual and tell me which screenshots I still need to capture.”
  • “Run the consistency check on the software name and version across all the materials.”

Requirements

  • Python for the bundled scripts
  • The real project source files, scanned for secrets before export

Workflow steps

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

  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”

What it can do on your machine

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

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

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

  • Network

    No URLs in SKILL.md.

    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

China Software Copyright Materials loads about 1.9k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 144 tokens; SKILL.md has 863 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~144
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.3k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from Light0305/Light-skills at commit 6b44f57, republished under its MIT licence (© Light0305). 863 words, ~1,918 tokens.

Download SKILL.mdSave it as .claude/skills/light-software-copyright/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
light-software-copyright
description
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.

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 before current-rule or material-format work. Read 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 China Copyright Protection Center workflow, form, fee, page format or exception rule is not verified that day, write UNKNOWN or PLANNED.
  5. Keep every formal material version and software name consistent with the application worksheet.
  6. Keep this skill off the research DAG. It emits no light.findings.v1, has no stage, no checkpoint gate and no reroute.

Workflow

1. Intake and scope

Capture or mark UNKNOWN:

  • jurisdiction: default CN; do not silently reuse CN rules for US/EU work;
  • software full name, abbreviation if any, version, owner/applicant, developer, completion date, publication status and development mode;
  • whether the project is independent, commissioned, cooperative, inherited, derivative or based on licensed third-party code;
  • target output language, local folder for drafts, and whether screenshots are needed.

Stop for user confirmation before formal documents are generated.

2. Bind to a real source snapshot and deposit plan

Inventory source files from the project the user placed in scope. Record relative path, SHA-256 and why selected. Exclude:

  • generated build artifacts, minified bundles, vendored dependencies and lock files unless the user explicitly says they are the software expression to deposit;
  • secrets, tokens, keys, credentials, private data and unrelated third-party code;
  • arbitrary middle snippets chosen only to make the material look longer.

If the project is too small, submit all real source rather than padding.

Run the lightweight planner before extraction:

bash
python scripts/source_deposit_plan.py --root <project-root> --out 软件著作权申请资料/草稿/source-deposit-plan.json --software-name "<软件全称>" --version "<版本号>"
python scripts/source_deposit_plan.py --selftest

Use the plan to confirm candidate files, page mode, selected file count, secret-scan status and the plan SHA. If secret-like content is found, stop for redaction before exporting code material.

3. Confirm application fields and business understanding

Generate a worksheet for the user to verify:

  • software name and version;
  • owner/applicant and contributor facts;
  • development environment and operating environment;
  • main functions, technical characteristics and use scenario;
  • source program quantity and document material quantity;
  • publication status and dates.

The manual must describe how a reviewer/user operates the software. It should not be a generic feature list disconnected from screens, commands or workflows. Record rights basis and third-party/open-source/generated-code review before formal export. Do not assume independent ownership when the project may be commissioned, cooperative, inherited, derivative or license-constrained.

Show full SKILL.md (374 more words)Show less
4. Prepare code and document material

For normal China material logic, follow the official first/last rule:

  • source program and one documentation material use front/back continuous 30 pages when the whole material is at least 60 pages;
  • if the whole material is fewer than 60 pages, include the whole source or whole document;
  • full source pages normally need at least 50 lines, and full document pages at least 30 lines, unless a documented official exception applies.

Keep extraction manifests and page counts. If exceptional deposit is requested, mark it explicitly and ask the user to verify the current official rule.

5. Generate local drafts, then formal outputs

Use a local folder such as 软件著作权申请资料/:

  • 草稿/: application worksheet, manual draft, code-selection notes;
  • 正式资料/: final DOCX/TXT/PDF-like outputs only after confirmation;
  • manifest/report JSON: file paths, SHA-256, source snapshot, confirmation basis and rule status.

Screenshots are optional; if not used, record why. If used, bind each screenshot to a real running UI or user-provided image and hash it.

6. Run the machine gate before saying “ready for review”

Create a packet following templates/software-copyright-materials.example.json, then run:

bash
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

The gate must pass before calling the package ready for user/professional review. A failed gate means repair the source plan, source binding, rights basis, third-party review, confirmation, page rule, version consistency, secret handling or output hashes.

ACT / ASK / NEVER

ACT:

  • use real source files and record SHA-256;
  • ask the user to confirm application fields, business context, code selection, drafts and final export;
  • keep source-code and documentation page counts explicit;
  • make software name and version identical across all materials;
  • scan for secrets/private data before exporting source-code material.
  • record rights basis and third-party/open-source/generated-code exclusions.

ASK:

  • owner/applicant and development-mode facts;
  • whether third-party/commissioned/inherited/derivative code is present;
  • whether screenshots should be included;
  • whether exceptional deposit or redaction is needed;
  • whether the software is independently developed, commissioned, cooperative, inherited, derivative, or includes third-party/generated code;
  • whether to stop at drafts or generate formal local files.

NEVER:

  • submit materials or interact with the registration system for the user;
  • promise approval, certificate timing, or “包过”;
  • fabricate source code, pad line counts, or select arbitrary snippets;
  • leak credentials, private data or unrelated third-party code;
  • silently include vendored, generated or license-constrained code without a third-party review note;
  • route this skill into the Light research DAG.

© Light0305, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in skills/light-software-copyright of Light0305/Light-skills.

  • SKILL.md
  • references/materials-workflow.md
  • references/software-copyright-resource-map.md
  • scripts/materials_gate.py
  • scripts/source_deposit_plan.py
  • templates/software-copyright-materials.example.json

Open the folder on GitHubat commit 6b44f57

Compare with similar skills

China Software Copyright Materials 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.

China Software Copyright Materials compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
China Software Copyright Materials this skillLight0305/Light-skills641—~1.9kAutomated safety check: PassMIT
MCP Documentation Standardpatsnap/mcp112—~1.2kAutomated safety check: PassApache-2.0
Write Readmecdiggins/plato106—~1.6kAutomated safety check: PassMIT
License Header Adderrominirani/antigravity-skills5921 repos~294Automated safety check: PassNone
Index ManagerRobThePCGuy/Claude-Patent-Creator196—~994Automated safety check: PassMIT
Researchalirezarezvani/claude-skills28k—~4.3kAutomated safety check: PassMIT

Similar skills

  • MCP Documentation Standard

    patsnap/mcp

    Create or update Patsnap MCP catalog documentation in this repository.

    112 GitHub stars~1.2k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • Write Readme

    cdiggins/plato

    Write or review a project README.md in plain technical-writer prose — problem it solves and doesn't, honest assessment of tested vs untested, trade-offs, prior art, organization, and usage.

    106 GitHub stars~1.6k tokensUpdated 12 days ago
    DevelopmentAuto-check passed

  • License Header Adder

    rominirani/antigravity-skills

    Adds the standard open-source license header to new source files. Use involves creating new code files that require copyright attribution.

    592 GitHub starsUsed in 1 repo~294 tokens
    Legal & ComplianceAuto-check passed

  • Index Manager

    RobThePCGuy/Claude-Patent-Creator

    Manages MPEP index lifecycle including downloads, building, maintenance, and optimization.

    196 GitHub stars~994 tokensUpdated 2 days ago
    Legal & ComplianceAuto-check passed

  • Research

    alirezarezvani/claude-skills

    Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants…

    28k GitHub stars~4.3k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed

  • Linkfox Zhihuiya PDF Data

    linkfox-ai/linkfox-skills

    通过专利ID或公开号从智慧芽专利数据库下载专利PDF全文文档。当用户提到专利PDF下载、专利全文、专利文件获取、公开号查询、专利家族PDF替代、批量专利PDF导出、patent PDF download, patent full-text document, patent file download, PatSnap, patent…

    106 GitHub starsUsed in 1 repo~1.8k tokens
    Legal & ComplianceAuto-check passed

More from Light0305/Light-skills

All 23 skills in this repo

  • Citation Verification

    Light0305/Light-skills

    Verifies that every reference in a manuscript is real, correctly identified and actually supports its claim, and produces a citation registry for typesetting.

    641 GitHub stars~3.4k tokensUpdated 3 mo ago
    Auto-check passed

  • Light Research Orchestrator

    Light0305/Light-skills

    Coordinates and recovers multi-stage Light research projects from a single passport file, with checkpoints, stale-work tracking and rerouting only when you approve.

    641 GitHub stars~3.8k tokensUpdated 3 mo ago
    Auto-check passed

  • Patent Disclosure Handoff

    Light0305/Light-skills

    Builds an evidence-backed invention disclosure packet from a project or research result for attorney or patent-agent review, without giving legal advice.

    641 GitHub stars~2k tokensUpdated 3 mo ago
    Auto-check passed

  • Light Project Structure

    Light0305/Light-skills

    Audits, scaffolds and safely migrates research project folder structures, keeping existing repositories read-only until you approve exact moves from a plan.

    641 GitHub stars~3k tokensUpdated 3 mo ago
    Auto-check: notes

  • Light System Design

    Light0305/Light-skills

    Evidence-based workflow for designing or modernizing a software system: current-state inventory, options, API and schema contracts, migration plans, ADRs and verification.

    641 GitHub stars~3.6k tokensUpdated 3 mo ago
    Auto-check passed

  • Light Typesetting

    Light0305/Light-skills

    Build and preflight submission-ready LaTeX/PDF artifacts for Light stage 11.

    641 GitHub stars~3.3k tokensUpdated 3 mo ago
    Auto-check passed

Categories

Questions about China Software Copyright Materials

What does China Software Copyright Materials do?

Prepares draft materials for a China software copyright registration from a real project: application worksheet, source deposit plan, operation manual and consistency checks. The skill drafts auditable registration materials and keeps the software name, version, source-code material, manual, screenshots and applicant fields consistent, so you or a service provider can review them. It begins with intake, marking unknowns, and stops for your confirmation before formal documents are produced.

When should I use China Software Copyright Materials?

China Software Copyright Materials fits situations like: assembling source-code deposit pages from a project for copyright registration; drafting the user or operation manual that accompanies an application; checking name and version consistency across all registration documents; reviewing the material set before submission.

How do I install China Software Copyright Materials in Claude Code?

Run `npx skills add Light0305/Light-skills --skill light-software-copyright -a claude-code`. Or copy the skill folder (skills/light-software-copyright in Light0305/Light-skills) into .claude/skills/light-software-copyright in your project. Claude Code loads it when a task matches its description.

How do I install China Software Copyright Materials in Codex?

Run `npx skills add Light0305/Light-skills --skill light-software-copyright -a codex`. Or copy the skill folder (skills/light-software-copyright in Light0305/Light-skills) into .agents/skills/light-software-copyright in your project. Codex loads it when a task matches its description.

Can I use China Software Copyright Materials 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 Light0305/Light-skills --skill light-software-copyright -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/light-software-copyright, .gemini/skills/light-software-copyright, .github/skills/light-software-copyright and .opencode/skills/light-software-copyright in your project.

What does China Software Copyright Materials need to run?

Going by SKILL.md and its folder, China Software Copyright Materials needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python for the bundled scripts; The real project source files, scanned for secrets before export.

Does China Software Copyright Materials access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is China Software Copyright Materials 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does China Software Copyright Materials use?

China Software Copyright Materials 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 China Software Copyright Materials use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.

What are the alternatives to China Software Copyright Materials?

Skills that share tags, products or a category with China Software Copyright Materials: MCP Documentation Standard (patsnap/mcp, 112 stars), Write Readme (cdiggins/plato, 106 stars), License Header Adder (rominirani/antigravity-skills, 592 stars) and Index Manager (RobThePCGuy/Claude-Patent-Creator, 196 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains China Software Copyright Materials?

Light0305 (a GitHub user) maintains it in Light0305/Light-skills, which has 641 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on July 6, 2026.

Source: Light0305/Light-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.