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

Add Platform Source

by whiteguo233 in whiteguo233/OpenBiliClaw

Add, repair, or validate an OpenBiliClaw platform source across fetching, account signals, discovery, and user surfaces.

MITAuto-check passed

Install Add Platform Source

skills CLI
$ npx skills add whiteguo233/OpenBiliClaw --skill add-platform-source -a claude-code

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

GitHub CLI
$ gh skill install whiteguo233/OpenBiliClaw add-platform-source --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/whiteguo233/OpenBiliClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/add-platform-source .claude/skills/add-platform-source && 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
add-platform-source
GitHub stars
3.4k
Token cost
~1.9k tokens
SKILL.md length
914 words
Files
2
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Add, repair, or validate an OpenBiliClaw platform source across fetching, account signals, discovery, and user surfaces.

  • Works in 7 steps: Preserve existing changes and use the… → Start with the relevant history-index… → For a new source, copy the contract and… → …
  • Source-specific integration work and its acceptance
  • SKILL.md covers Select the scope and reading, Execute with evidence and Preserve these boundaries
  • Calls git

What it does

Add Platform Source is an agent skill from whiteguo233/OpenBiliClaw. Add, repair, or validate an OpenBiliClaw platform source across fetching, account signals, discovery, and user surfaces. Use for source-specific integration work and its acceptance; exclude unrelated UI, recommendation-algorithm, or release-only work.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It works with Python. The repository describes itself as: 本地私有、开源的自进化跨平台 AI 内容发现 Agent：先理解你，再主动从 B站、小红书、抖音、YouTube、X、知乎、Reddit、微博等平台与开放 Web 寻找内容。（支持 deepseek harness 插件） | Local-first open-source cross-platform AI content discovery…. The licence is MIT.

When your agent uses it

  • Source-specific integration work and its acceptance
  • Exclude unrelated UI
  • Recommendation-algorithm
  • Release-only work

Example prompts

  • “/add-platform-source”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Preserve existing changes and use the repository's worktree rule for implementation. Record the baseline. Before tests or E2E, prove…
  2. Start with the relevant history-index rows, then inspect first integration and follow-up repairs in git log --all and current tests. Read…
  3. For a new source, copy the contract and acceptance templates. For an increment, reuse/update its contract and record the changed gates…
  4. Probe the changed upstream path read-only before inventing fixtures. Preserve redacted success, pagination/termination and…
  5. Implement vertical slices: registry/contract → transport/normalization → event/bootstrap → formal discover/eval → config/status/init →…
  6. For source wiring, run the audit with the repository Python 3.11+ interpreter: PYTHONPATH="$PWD/src" "$SOURCE_SKILL_PYTHON"…
  7. Record commands, exits and evidence levels in an acceptance copy. Only all-required PASS earns complete for the declared scope. Report…

What it can do on your machine

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

    Shell commands in SKILL.md call:

    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

Add Platform Source loads about 1.9k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 914 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from whiteguo233/OpenBiliClaw at commit 2d8fe41, republished under its MIT licence (© whiteguo233). 914 words, ~1,904 tokens.

Download SKILL.mdSave it as .claude/skills/add-platform-source/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
add-platform-source
description
Add, repair, or validate an OpenBiliClaw platform source across fetching, account signals, discovery, and user surfaces. Use for source-specific integration work and its acceptance; exclude unrelated UI, recommendation-algorithm, or release-only work.

Add Platform Source

Deliver the requested source capability through the actual product path. Use docs/platform-source-integration.md as the shared guide and docs/platform-source-history-lessons.md to find failure precedents. Paths below are relative to the repository root. Historical sessions and plans are evidence, not current instructions or proof that a missing capability is still missing.

Select the scope and reading

Declare full, discovery-only, capability-increment, or audit-only. Plain “add a source” means full; a repair stays within the affected capability. Research/audit does not authorize implementation. Updating this skill requires documentation and skill validation, not a new platform contract or live account E2E.

Read the guide's execution protocol and completion criteria, then select the relevant sections:

WorkGuide sections and useful precedents
New source§0 contract, §1 upstream spike, registration map; select the remaining sections by capability
Auth / identity / settings§0.1–0.7, §4–5; Bangumi/GitHub optional credentials, V2EX/Linux.do/Weibo capability readiness
Browser tasks / account signals§2–3, §5; staged completion, MV3 recovery, incremental opt-in and task isolation
API / Feed / discovery§1, §6–6.5; GitHub pagination/cooldown, keyword dual-track, shared admission
Cards / native save§7–9; DTO-to-renderer evidence, exact identity and persisted save confirmation
Validation / delivery§8–11; scoped tests, installed artifact provenance, separate E2E chains and documentation

For full integration, scan the whole guide's capability headings for omissions. For a narrow repair, expand to adjacent sections only when the diff crosses those boundaries; do not reopen unrelated platform implementations.

Execute with evidence

  1. Preserve existing changes and use the repository's worktree rule for implementation. Record the baseline. Before tests or E2E, prove Python imports, CLI, backend config/data roots and any installed extension resolve to the intended checkout; reload alone does not deploy a worktree build.
  2. Start with the relevant history-index rows, then inspect first integration and follow-up repairs in git log --all and current tests. Read available project sessions/PRs only to fill a concrete evidence gap. Distinguish root user requests from delegated reviews, and merged fixes from in-flight branches. Never copy credentials, private account data, raw transcripts, or historical authorization into the task.
  3. For a new source, copy the contract and acceptance templates. For an increment, reuse/update its contract and record the changed gates. Keep applicability (required or N/A, with evidence) separate from execution (PASS, FAIL, NOT_RUN, or BLOCKED). Capability exclusions need executable proof where enforceable; out-of-scope mutations need scope evidence. deferred and missing E2E are never N/A.
  4. Probe the changed upstream path read-only before inventing fixtures. Preserve redacted success, pagination/termination and counterexamples. Anonymous success does not prove authenticated pagination, current-account ownership, private bootstrap, or the installed dispatcher. If one route is unavailable, record that boundary and continue independent work within the requested contract.
  5. Implement vertical slices: registry/contract → transport/normalization → event/bootstrap → formal discover/eval → config/status/init → surfaces. Reuse shared backend contracts and choose precedents per capability. Validate behavior at each affected boundary.
  6. For source wiring, run the audit with the repository Python 3.11+ interpreter: PYTHONPATH="$PWD/src" "$SOURCE_SKILL_PYTHON" scripts/audit_platform_source.py --contract <contract> --check --json. Audit PASS proves registration evidence only. Review omissions against the raw contract, diff and artifacts; use an independent reviewer when requested or when the integration's risk warrants an authorized review, not as a mandatory extra process for every repair.
  7. Record commands, exits and evidence levels in an acceptance copy. Only all-required PASS earns complete for the declared scope. Report incremental only for usable work with missing required proof, or blocked for work that cannot proceed. An audit/repair being complete does not certify the entire source. Report implemented, tested, merged, installed and released states separately.
Show full SKILL.md (340 more words)Show less

Preserve these boundaries

  • Auth is per capability when needed. Reuse SourceCapabilityAuth and SourceAuthContract.capabilities for capability-specific sources; check source-specific status/setup/init projections before declaring a prerequisite missing. Backend code owns account resolution. Observed identity is not verified identity; current authoritative failure overrides stale hints. Preserve omitted/clear/masked credential semantics, fingerprint-scoped evidence and 2xx warnings even when disabled.
  • Content and transport evidence stay honest. Namespaced stable IDs, canonical URLs, typed author_name, authoritative publication times and declared engagement availability must survive storage, DTOs and actual renderers. Follow only validated pagination destinations, including observed authenticated variants. Preserve accepted partial rows; no response, challenge HTML, parse failure and rate limit are not affirmative empty.
  • Browser execution is a lifecycle. Capability/online checks and local mutex precede atomic backend claim. Retain staged first-final-wins results, bounded durable replay and backend scope caps. Prove task isolation through SPA/full navigation and verify installed assets for the browsers claimed by the contract.
  • Periodic sync is opt-in. source_incremental_enabled defaults to false, including old configs without the key. Supporting incremental refresh must not enable it. Keep manual init, formal discovery, periodic bootstrap and native save distinct; test disabled scheduling and queued-task claim cancellation. Foreground task support is not permission to steal focus unattended.
  • Discovery must produce usable supply. Search sources need both keyword-generation tracks, KeywordFetchCoordinator.claim(<slug>), keyword identity/rollback, shared admission and shared cooldown across formal/inspiration paths. Show fetched → retained → evaluated → admitted counts; scheduler activity alone is insufficient.
  • E2E proves one chain at a time. Separate public transport, current-account → event → init/profile, discover → real configured LLM/embedding → recommendation, and installed UI evidence. Static markup/build success is not rendered UI or account E2E. Use isolated storage, check all declared smoke sinks and ordinary event deltas, and preserve the user's configured provider/model/route.
  • Side effects follow the current request. Carry forward authorization already given in this task; do not ask again at each gate or import permission from historical sessions. Upstream writes, production service changes and publication follow their actual scope. An uncertain native-save result permits read-only persisted-state verification, not another toggle. Complete independent authorized work before reporting a remaining external prerequisite.

© whiteguo233, 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 1 other file in .codex/skills/add-platform-source of whiteguo233/OpenBiliClaw.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 2d8fe41

Compare with similar skills

Add Platform Source 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.

Add Platform Source compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Add Platform Source this skillwhiteguo233/OpenBiliClaw3.4k—~1.9kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
PDF Processinganthropics/skills180k48 repos~2kAutomated safety check: PassProprietary
NotebookLM Research AssistantPleasePrompto/notebooklm-skill7.8k14 repos~2.4kAutomated safety check: NotesMIT
Manim Video Productionbrowser-use/video-use28k6 repos~3kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • PDF Processing

    anthropics/skills

    Official

    Handles everyday PDF jobs in Python and on the command line: extract text and tables, merge, split, rotate, watermark, fill forms, encrypt and OCR.

    180k GitHub starsUsed in 48 repos~2k tokens
    Documents & OfficeAuto-check passed

  • NotebookLM Research Assistant

    PleasePrompto/notebooklm-skill

    Lets Claude Code ask questions of your Google NotebookLM notebooks through browser automation and return answers grounded in your uploaded sources.

    7.8k GitHub starsUsed in 14 repos~2.4k tokens
    Knowledge ManagementAuto-check: notes

  • Manim Video Production

    browser-use/video-use

    Produces math and technical explainer videos with Manim Community Edition: concept animations, equation derivations, algorithm walkthroughs and data stories.

    28k GitHub starsUsed in 6 repos~3k tokens
    Media & CreativeAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • PPT Master

    hugohe3/ppt-master

    Generates editable PowerPoint decks, rebuilds slides from images, fills .pptx templates and polishes existing presentations through routed workflows.

    58k GitHub starsUsed in 1 repo~2.5k tokens
    Documents & OfficeAuto-check passed

More from whiteguo233/OpenBiliClaw

All 9 skills in this repo

  • Release

    whiteguo233/OpenBiliClaw

    A skill your agent uses when releasing a version, bumping project versions, or pushing release tags.

    3.4k GitHub stars~680 tokensUpdated today
    Auto-check passed

  • Openbiliclaw Adapter

    whiteguo233/OpenBiliClaw

    Use OpenBiliClaw's versioned Agent Bridge CLI to read multi-source recommendations, profile state, dialogue, probes, saved lists, and submit explicit feedback.

    3.4k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Writing Specs

    whiteguo233/OpenBiliClaw

    A skill your agent uses when authoring a spec or implementation plan, or planning multi-task work.

    3.4k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Verify

    whiteguo233/OpenBiliClaw

    Drive a real serve-api process against isolated project roots to verify backend/web changes end-to-end

    3.4k GitHub stars~539 tokensUpdated today
    Auto-check passed

  • System Steward

    whiteguo233/OpenBiliClaw

    管理订阅源与系统配置，所有改动逐项向用户说明并等待批准

    3.4k GitHub stars~238 tokensUpdated today
    Auto-check passed

  • Taste Companion

    whiteguo233/OpenBiliClaw

    默认对话伙伴，陪聊口味与推荐，可读写记忆、查询推荐与观看数据

    3.4k GitHub stars~296 tokensUpdated today
    Auto-check passed

Works with

Questions about Add Platform Source

What does Add Platform Source do?

Add, repair, or validate an OpenBiliClaw platform source across fetching, account signals, discovery, and user surfaces. Add Platform Source is an agent skill from whiteguo233/OpenBiliClaw. Add, repair, or validate an OpenBiliClaw platform source across fetching, account signals, discovery, and user surfaces.

When should I use Add Platform Source?

Add Platform Source fits situations like: source-specific integration work and its acceptance; exclude unrelated UI; recommendation-algorithm; release-only work.

How do I install Add Platform Source in Claude Code?

Run `npx skills add whiteguo233/OpenBiliClaw --skill add-platform-source -a claude-code`. Or copy the skill folder (.codex/skills/add-platform-source in whiteguo233/OpenBiliClaw) into .claude/skills/add-platform-source in your project. Claude Code loads it when a task matches its description.

How do I install Add Platform Source in Codex?

Run `npx skills add whiteguo233/OpenBiliClaw --skill add-platform-source -a codex`. Or copy the skill folder (.codex/skills/add-platform-source in whiteguo233/OpenBiliClaw) into .agents/skills/add-platform-source in your project. Codex loads it when a task matches its description.

Can I use Add Platform Source 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 whiteguo233/OpenBiliClaw --skill add-platform-source -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-platform-source, .gemini/skills/add-platform-source, .github/skills/add-platform-source and .opencode/skills/add-platform-source in your project.

What does Add Platform Source need to run?

Going by SKILL.md and its folder, Add Platform Source needs the command-line tools its instructions call (git). Our summary lists: Python 3.

Does Add Platform Source access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Add Platform Source 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. Review the folder before installing.

What licence does Add Platform Source use?

Add Platform Source 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 Add Platform Source use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Add Platform Source?

Skills that share tags, products or a category with Add Platform Source: MCP Server Builder (anthropics/skills, 180k stars), PDF Processing (anthropics/skills, 180k stars), NotebookLM Research Assistant (PleasePrompto/notebooklm-skill, 7.8k stars) and Manim Video Production (browser-use/video-use, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add Platform Source?

whiteguo233 (a GitHub user) maintains it in whiteguo233/OpenBiliClaw, which has 3,401 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 8, 2026.

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