Loading...
Loading...
Found 960 Skills
How to work in a Knowledge Base project (the `knowledge-base` starter pack). Read when the project has the three-layer source-grounded layout — `external-sources/` → `research/` → `articles/` — or when asked how this project is organized. Carries the layer model, per-folder rules, status flows, and log discipline so this guidance does NOT live inside template bodies or log.md. The three procedures live elsewhere: ingest in the platform `open-knowledge` skill, research and consolidate as their own sibling skills in this pack. Complements the platform `open-knowledge` skill; does not replace it.
Use when the user wants to mine comments and replies for audience reactions, customer language, questions, objections, complaints, product ideas, buying intent, sentiment, or voice-of-customer insights from public social posts and videos.
Creates a DTO (Data Transfer Object) class for an entity. Use this skill when a DTO class needs to be created, either standalone or as part of a larger task (e.g. REST controller, service layer, replacing entity usage with a DTO).
Collect comments from Douyin — text, author, timestamp, likes, replies. Use when the user wants to mine audience feedback, questions, or sentiment.
Collect comments from Reddit — text, author, timestamp, likes, replies. Use when the user wants to mine audience feedback, questions, or sentiment.
Review and triage pull requests on GitHub and Forgejo, including Codeberg, with first-class replies inside GitHub inline review threads. Use when asked to review a PR, inspect a GitHub PR with gh, respond to code-line feedback in its existing thread, inspect a Forgejo PR with fj or its REST API, analyze CI failures, classify unresolved reviewer feedback, prepare fixes, submit an overall review, or resolve review threads.
Provides instructions and architectural patterns for migrating Android TV applications from legacy Leanback UI Toolkit, Android Views, or Support Fragments to Jetpack Compose for TV (androidx.tv). Use this skill for Leanback to Compose migrations, including browse screen, settings screen, authentication screen, login screen, or video playback screen migrations, or when replacing BrowseSupportFragment, LeanbackSettingsFragment, PreferenceFragment, BaseLeanbackPreferenceFragmentCompat, VideoSupportFragment, GuidedStepSupportFragment, SearchSupportFragment, VerticalGridSupportFragment, Presenter, ArrayObjectAdapter, or CursorMapper with modern Compose equivalents, implementing immersive carousels with focus memory, Media3 video playback with PlayerSurface, or custom 10-foot hero layouts.
Clean-room rethink of existing functionality — trace what the code really does, restate it as a problem and a goal, design a solution behind a context wall where the code is unseen (web research for libraries and best practices), then judge the current implementation against that design and propose replace, graft, or keep-as-is. Use when asked whether some code is the best way to solve its problem, to rethink or redesign a module, for a second opinion on an approach, or to find a simpler, more robust, or more testable way to build something that already exists.
Collect comments from Kuaishou — text, author, timestamp, likes, replies. Use when the user wants to mine audience feedback, questions, or sentiment.
Collect comments from TikTok — text, author, timestamp, likes, replies. Use when the user wants to mine audience feedback, questions, or sentiment.
Use when the user asks to "is my ad fatiguing", "why is CTR dropping at scale", or "should I rotate creative / widen the audience"; reads frequency, CTR and CVR decay against an early-flight baseline and returns Rotate-creative / Widen-audience / Hold triggers with a per-ad-set fatigue read. Not for building the replacement creative — use ad-creative-builder; not for the RQS score or vetoes — use ad-account-auditor. 广告疲劳检测/频次管理/换素材还是扩人群
How to work in an OKF starter project (the `okf` starter pack): a knowledge base that is conformant with Google's Open Knowledge Format (OKF) from commit one — `concepts/`, `references/`, `notes/`, a reserved `index.md` navigation hub, and a reserved `log.md` change history. Read when the project has these folders plus reserved files, OR when asked whether a document is OKF-conformant, or to add a document to an OKF knowledge base. Carries the OKF conventions (non-empty `type` on every non-reserved doc; reserved files carry no frontmatter) as guidance, not enforcement. Complements the platform `open-knowledge` skill; does not replace it.