mcncarl/yichen-skills

Yichen-skills is a skill collection for creators that streamlines writing, content distribution, and local workflows using Claude Code and Codex integration.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 2 minutes ago
Added to GitGenius on September 18th, 2026
Created on February 11th, 2026
Open Issues & Pull Requests: 7 (+0)
GitHub issues: Enabled
Number of forks: 1,720
Total Stargazers: 4,000 (+7)
Total Subscribers: 8 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 37.1 days
90th percentile: 74.2 days
Tracked items: 2

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 3
Closed in 7 days: 0
Avg open age: 37 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

Opened in 7 days: 3
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Yichen-skills is a skill collection for creators that streamlines writing, content distribution, and local workflows using Claude Code and Codex integration.

The tool addresses the fragmented workflow problem creators face when managing multiple content platforms and tasks. It provides skills designed to automate writing processes, slice content for X (formerly Twitter), draft and publish articles, capture WeChat digital assets, and integrate with local development environments through Claude Code and Codex. The approach bundles these capabilities into reusable skills that creators can invoke within their existing workflows.

Adoption suits individual creators and small teams managing multi-platform content strategies, particularly those already using Claude or Codex for development tasks. The tool is explicitly restricted to personal learning and non-commercial personal use without authorization. Commercial deployment—including client work, paid products, internal company use, or course bundling—requires explicit written permission from the maintainer, obtainable through direct contact or membership in the maintainer's paid community. This licensing model means the tool is not suitable for agencies, SaaS platforms, or businesses seeking to incorporate it into commercial offerings without negotiating separate terms.

Development activity shows a single maintainer maintaining the repository while actively building AI products and services. The maintainer maintains a public presence across multiple platforms and provides direct contact channels for inquiries. The project includes explicit commercial licensing terms and a paid community membership option, indicating active engagement with users around authorization and support. The repository includes localized documentation in both English and Chinese, reflecting attention to accessibility for different audiences.