# Generate Software Copyright Materials

Software copyright filings require consistent code, manual, and application materials. This skill guides Claude Code, Claude, or Codex through evidence-based Chinese filing drafts and final Word or TXT outputs.

## Install

```bash
npx skillstore add fokkyp/software-copyright-materials
```

## Metadata

- Status: approved
- Slug: fokkyp-software-copyright-materials
- Skillstore revision: r1
- Version status: missing
- Tree hash: 6566321e11d8d882fdc4091fade021981139c9319b38fdf255706c0d87d2f837
- Author: Fokkyp
- GitHub username: Fokkyp
- License: MIT
- Repository: https://github.com/Fokkyp/SoftwareCopyright-Skill/tree/main/software-copyright-materials
- Ref: 1ffa7643651792ccb4bd3b15d924d2c97edff755
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/fokkyp-software-copyright-materials
- Manifest: https://skillstore.pages.dev/api/skills/fokkyp-software-copyright-materials/manifest

## Capabilities

- Analyzes an imported project to identify source files, routes, pages, dependencies, and likely software metadata.
- Generates Chinese Markdown drafts for business understanding, application information, code materials, and an operation manual.
- Requires user confirmation at key stages before creating final filing materials.
- Extracts code materials from confirmed source files and keeps a traceable extraction manifest.
- Builds final Word and TXT materials using bundled DOCX tooling or a fallback generator.
- Supports screenshot planning, user-supplied screenshots, or visible screenshot placeholders when screenshots are skipped.

## Use Cases

- Prepare a first filing package: Generate draft application text, code materials, and an operation manual from a real project before formal review.
- Standardize client deliverables: Create consistent Chinese software copyright materials for multiple customer projects with confirmation gates.
- Review project evidence before submission: Trace selected code files, software names, version data, and manual content before generating final Word files.

## Prompt Templates

### Start a basic filing workflow

```
Use the software-copyright-materials skill to analyze this project and start generating Chinese software copyright application materials. Stop at each required confirmation step.
```

### Generate drafts for review

```
Analyze the project, build the business understanding evidence, and generate Markdown drafts for application information, code materials, and the operation manual. Do not create final Word files until I confirm the drafts.
```

### Control code material selection

```
Prepare the code file candidate list for software copyright materials. Recommend files and line ranges that best show the real product functions, then wait for my confirmation before extraction.
```

### Complete final materials with constraints

```
After confirming the business context, application fields, code selection, screenshot method, and Markdown drafts, generate final Word and TXT materials. Keep the software name and version consistent with the confirmed application information.
```

## Limitations

- The generated materials are not legal advice and still require human review before submission.
- The workflow is designed for Chinese software copyright materials and Chinese-language filing conventions.
- Full DOCX generation may require local tools such as .NET, pandoc, or LibreOffice.
- Project understanding depends on the available source code, documentation, and user-provided business context.

## Best Practices

- Review every Markdown draft before allowing final Word or TXT generation.
- Confirm the software full name and version once, then use the same values across all final materials.
- Provide clear business context and screenshots when the source code does not explain the product workflow.

## Anti Patterns

- Do not submit generated materials without legal, business, and technical review.
- Do not let the workflow invent product functions that are not supported by project evidence.
- Do not run bundled setup scripts without understanding their package installation and shell changes.

## Security Audit

- Audited at: 2026-07-21T07:29:41.775\+00:00
- Summary: Most static matches are false positives from Chinese prose, OOXML samples, documentation, and normal document-generation operations. The optional DOCX setup workflow is a real high-risk installer: it uses sudo, downloads and executes a remote installer, and changes user shell configuration. Do not run that setup workflow automatically or without user review. Static review was capped at 400/1023 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.

## Stats

- Views: 63
- Downloads: 7
- Favorites: 0
- Popularity score: 0