Skip to content

Add public-social-account-analyzer skill - #2583

Open
Luckycat133 wants to merge 6 commits into
github:mainfrom
Luckycat133:add-public-social-account-analyzer
Open

Add public-social-account-analyzer skill#2583
Luckycat133 wants to merge 6 commits into
github:mainfrom
Luckycat133:add-public-social-account-analyzer

Conversation

@Luckycat133

Copy link
Copy Markdown

Summary

Add the public-social-account-analyzer skill: an Agent Skill for analyzing public Chinese social accounts on B站/哔哩哔哩、抖音、微博、小红书, and 公众号.

Capabilities:

  • Content strategy / topic pillars / direction (内容策略/选题方向/内容栏目)
  • Posting rhythm, frequency, schedule (发布节奏/频次/时间分布)
  • Public engagement efficiency (互动效率/互动率)
  • Top/bottom performer patterns (高低表现/爆款共同点)
  • Comment themes & audience demand (评论区需求/评论洞察)
  • Recent / time-windowed analysis (最近 N 条/最近 30 天/全量)

Compliance with CONTRIBUTING

  • Self-contained folder under skills/public-social-account-analyzer/ with SKILL.md (front matter name matches folder)
  • npm run skill:validate passes (all 395 skills valid, including this one)
  • npm run build ran to regenerate docs/README.skills.md
  • Bundled assets well under 5MB each (total skill ~1.6MB)
  • Only analyzes public data; stops on login walls / rate limits / verification requirements and emits auditable PARTIAL artifacts rather than silent failure

Source repo: https://github.com/Luckycat133/public-social-account-analyzer

Luckycat133 and others added 6 commits July 28, 2026 11:25
Migrate AI assistant context (MCP servers, rules, skills, slash commands,
agents, hooks, memory) between 54+ IDEs with safe, verified merging.
The 'Fetch GitHub traffic statistics' step used GH_TOKEN: $\{\{ secrets.REPORTING_TOKEN \}\},
but that secret is not defined in the repository, so the variable resolved empty and
'gh api' failed with: "To use GitHub CLI in a GitHub Actions workflow, set the GH_TOKEN
environment variable."

Switch to the built-in GITHUB_TOKEN. Reading traffic stats requires push access to the
repo, so the job permission for contents is also raised from 'read' to 'write'.
The traffic API (GET /repos/{repo}/traffic/views) requires the classic 'repo' scope;
the fine-grained GITHUB_TOKEN has no associated permission for this endpoint and
always returns HTTP 403 ('Resource not accessible by integration'). So github.token
cannot work here. Restore the original secret-based design now that the missing
REPORTING_TOKEN secret has been created (classic PAT with repo scope).
The 'Send traffic data to reporting endpoint' step hard-failed because
vars.REPORTING_POST_URL is not set in this repo. Make the upload optional:
when REPORTING_URL is empty, log a warning and exit 0 instead of failing the
whole workflow. The upload still runs normally once the variable is configured.
@github-actions github-actions Bot added new-submission PR adds at least one new contribution skills PR touches skills workflow PR touches workflow automation labels Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-submission PR adds at least one new contribution skills PR touches skills workflow PR touches workflow automation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant