Skills
99,719 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Use the Opper CLI (`opper` command, npm package `@opperai/cli`) for terminal work with Opper: signing in, calling functions, inspecting traces, tracking usage and costs, generating images and video, installing bundled skills, configuring AI code editors, and launching coding agents (Claude Code, OpenCode, Codex, Hermes, Pi) with their inference routed through Opper. Use this skill whenever the user mentions the `opper` command, the Opper CLI, opper-ai/cli, `@opperai/cli`, `opper launch`, or explicitly wants shell commands, editor configuration, private local key delivery, or agent launch workflows. Prefer opper-mcp for agent-assisted setup, platform management, and model tests. For exact arguments, always run `opper <subcommand> --help`; the help output is the authoritative reference.
Use only for offline/local OSMO service-config admin requests involving explicit config folders or values files, or to ask for one when a file-specific config request omits it. Do not inspect the workspace to infer a path. Do not use for live workflow support, resource capacity, pod/node diagnostics, or cluster operations, except live service-config paths that must be refused.
Use when a Datex Studio package (ComponentModule) has changed and its consumers must be updated and republished up the dependency graph. Recursively finds every package that references the changed one (directly or transitively), re-pins each to the new published version, and republishes — bottom-up, interactively, stopping at applications (which are reported as stale, never republished). Triggers: "propagate this package change", "update everything that references package X", "cascade republish", "bump and republish all dependents", "roll out the new version of <package> to its consumers", "who needs republishing after I published <package>".
The packaging workshop—the final step in the writing suite. Handles presentation after content is finalized: title polishing, opening hooks, layout optimization, punctuation cleanup (integrates with zan-punct-fix), image suggestions, and platform adaptation. Does not change the body text. Its six modules can be triggered independently. Triggers: “polish the title,” “this title isn’t good enough,” “how should I write the opening,” “check the layout,” “the paragraphs are too dense,” “check punctuation,” “review the images,” “which platform suits this article,” “I’m ready to publish—review the packaging,” “check the presentation,” “the content is fine but it’s tiring to read,” “pre-publish check.” EN: “polish the title,” “fix the opening hook,” “check layout,” “fix punctuation,” “review images,” “platform formatting,” “pre-publish checklist”. Not for: rewriting the body text (→ plainspoken-writing / editor-revisor); content quality diagnosis (→ chinese-write-checker); voice calibration (→ voice-dissolver).
H3 prompt writing for halftone paper-collage explainers: visual metaphors, the finished still state, stop-motion assembly movement and collage sound-design intent, producing still-image or video prompts. No BGM, voiceover or subtitles by default. Use for knowledge points, opinions and B-roll prompts.
Make paper cut-out / stop-motion style animated videos (MP4) with code — handmade construction paper, cardstock, kraft, felt and tissue pieces with scissor-cut or torn edges and soft drop shadows, photographed on a table under a warm lamp; jointed paper puppets with brass split-pin joints, moving in 12 fps steps. Canvas 2D rendered frame by frame in headless Chrome, encoded with ffmpeg. Use when a reference video or brief calls for paper craft, cut-paper, papercraft, stop-motion paper, kids' storybook collage, 剪紙 / 紙片 / 紙偶 / 定格動畫 looks, or when the video-clone router picks the paper-cutout style
Brainstorm a research idea and decide what a new paper should cover — generate candidate framings, pick the central contribution, and draw the in-scope vs. deferred boundary. Use whenever the user has a rough interest, preliminary results, or a problem and asks "what should this paper be about", "help me brainstorm an idea", "what should I include / cover", "is this one paper or two", "help me scope this", "what's the contribution here", or "I have an idea but don't know how to frame it". Default to running this upstream of research-idea-stress-test (which vets one chosen idea) and paper-argument-planner (which structures a paper once the contribution is fixed). Always check first whether the input is sufficient (a seed, the field, the motivation); if not, request the missing context before brainstorming rather than inventing a direction. Hands off per-claim evidence to benchmark-and-baseline-selector, novelty grounding to literature-triangulation, and section logic to paper-argument-planner.
H3 prompt writing for papercraft stop-motion explainers: learning objectives, papercraft art-style locks, layered sets and mechanisms, and a storyboard plus image/video prompt creation kit. Applies to paper-cut/pop-up book/miniature stop-motion explainer prompts. Not for ordinary cartoon scripts without papercraft texture.
Turns products, knowledge points, or copy into cinematic web demo animations in a "phone system UI style" — the audience watches what looks like a carefully choreographed screen recording of a real phone: lock screen notifications, chats, settings pages, control center, and app screens revealed shot by shot, with HyperOS/MIUI-level tactile motion effects plus a virtual clock player, recordable full-screen as a finished video. Use this skill whenever the user mentions phone UI demos, phone screen-recording style animations, app demo web pages, turning a product into a demo inside a phone, lock screen notification animations, system UI style demo pages, or asks to revamp and upgrade a batch of phone-style demo pages. Content is fully open with no limits: any product feature, course knowledge, or science narrative can be translated into "what happens inside a phone".
[Planning] Use when you need intelligent plan creation with prompt enhancement. Flag: --mode={ci|cro} (default none — standard planning); --mode=ci plans a fix from a GitHub Actions CI run/log, --mode=cro plans conversion-rate optimization (25-item CRO framework).
Use when writing or adapting short-form or sponsored video content for a specific platform, such as TikTok, Instagram Reels, YouTube, or YouTube Shorts, or repurposing one script across platforms. Keywords - optimal video length, hook timing, captions, platform-native style, algorithm signals, sponsorship disclosure, cross-platform repurposing.
Monetizes browser games with Play.fun by guiding game registration, rewards and leaderboard setup, SDK integration, and deployment. Use when the user says "monetize my game", "add Play.fun", "add token rewards", "add a leaderboard", "register my game", "deploy so players earn rewards", or "launch a Playcoin". Do NOT use for generic game design, unrelated Solana questions, or non-game web apps.
Help Portaly creators install Google Analytics 4 (GA4) on their websites, set up Portaly event tracking, and connect their GA4 account to Portaly for viewing analytics dashboards. Trigger when the user mentions Google Analytics, GA4, tracking, analytics, website traffic, event tracking, or wants to connect analytics to Portaly.
This skill should be used when handling issue intake rotation duties for the Positron repository. It provides workflows for reviewing and organizing new issues, responding to discussions, handling support tickets, and searching for related content. Use this skill when on intake rotation duty, when helping someone with intake tasks, or when learning the intake rotation process.
Full Windows post-exploitation workflow. Use after obtaining a Windows shell via RCE/webshell/RDP. Covers system information gathering, UAC bypass, local privilege escalation, credential extraction (SAM/LSASS/browsers), and domain reconnaissance. Applies to standalone hosts and domain environments.
Import and export TMDL/TMSL formats, manage model lifecycle with transactions, and version-control Power BI semantic models using pbi-cli. Invoke this skill whenever the user mentions "deploy", "export", "import", "TMDL", "TMSL", "version control", "git", "backup", "migrate", "transaction", "commit changes", "rollback", or wants to save/restore model state.
Add, remove, and manage page-level and visual-level filters on Power BI PBIR reports using pbi-cli. Invoke this skill whenever the user mentions "filter", "TopN filter", "top 10", "bottom 5", "relative date filter", "last 30 days", "categorical filter", "include values", "exclude values", "clear filters", "slicer filter", "page filter", "visual filter", or wants to restrict which data appears on a page or in a specific visual.
Scaffold, validate, preview, and manage Power BI PBIR report projects using pbi-cli. Invoke this skill whenever the user mentions "create report", "new report", "PBIR", "scaffold", "validate report", "report structure", "preview report", "report info", "reload Desktop", "convert report", ".pbip project", "report project", or wants to understand the PBIR folder format, set up a new report from scratch, or work with the report as a whole. For specific tasks, see also: power-bi-visuals (charts, binding), power-bi-pages (page management), power-bi-themes (themes, formatting), power-bi-filters (page/visual filters).
Configure row-level security (RLS) roles, object-level security, and perspectives for Power BI semantic models using pbi-cli. Invoke this skill whenever the user mentions "security", "RLS", "row-level security", "access control", "data restrictions", "who can see", "filter by user", "perspectives", "limit visibility", or wants to restrict data access by role.
The declassified UAP file archive in your terminal — browse, search, and download 162+ files from the PURSUE initiative Trigger phrases: `check UFO files`, `search declassified UAP`, `download PURSUE files`, `war.gov UFO`, `browse UFO archive`, `use ufo`.
Comprehensive pre-merge validation checklist for Python/React pull requests. Use before approving or merging any PR. Covers code quality checks (linting, formatting, type checking), test coverage requirements, documentation updates, migration safety, API contract compatibility, accessibility compliance, bundle size impact, and deployment readiness. Provides a systematic checklist that ensures nothing is missed before merge. Does NOT cover security review depth (use code-review-security).
ALWAYS load before starting any task. Maximizes token efficiency for all file operations, searches, and command execution. Covers extract modes (content, outline, symbols, ast, lines), verbosity tuning, multi-file batching, and discover tool orchestration. Ensures agents spend tokens on outcomes, not overhead.
Use when the user provides an original and rewritten version, asks whether a rewrite preserved protected content, or wants a deterministic check for code, frontmatter, quotes, tables, links, paths, numbers, headings, and residual AI-pattern regressions.
Principal-level architecture, system design, trade-off analysis, ADRs, Clean Architecture, GoF, production-ready microservices, Clean Code, algorithms, domain modeling/DDD, distributed data, API contracts, quality attributes/ATAM, SRE/resilience, secure architecture, legacy evolution, C4/arc42 documentation, and engineering ownership. Use for architecture/code reviews, tech strategy, pattern audits, coding standards, algorithm or data-structure choice, Big O/performance, databases, consistency, events, scalability, SLO/reliability, threat modeling, modernization/migration, bounded contexts, aggregates, context mapping, API versioning/deprecation, team topology, platform engineering, multi-service design, or /principal-software-architect. Produces evidence-based findings and only the specialized baselines material to the decision.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.
Writing, refining, or reviewing a PRD, feature spec, plan document, RFC, design doc, or issue description — the canonical tool-agnostic section structure such a document takes, and the craft behind each section. Includes the plan-writing or issue-drafting step of any delivery workflow. Triggers on "write a PRD", "draft a spec", "refine this issue", "structure this plan", "write acceptance criteria", "how do I verify this is done", "is this requirement testable". Not for writing the code, only the document that specifies it; UI markup, module placement, and test mechanics stay with the project's own conventions.
Project initialization tool. Reads the global protocol ~/.claude/CLAUDE.md, analyzes the project's actual situation, and generates project-specific CLAUDE.md and docs/ context. This skill should be used when the user says "initialize project", "project setup", "configure Claude Code", "new project configuration", or when entering a new project that needs quick configuration. Do not use for: Skill content development or acceptance (use skill-lint), one-off Skill installation (use skill-manager), or code generation.
Manages session state and context handoffs for multi-session projects using the Session Handoff Protocol. Creates and maintains SESSION.md to track phase progress, git checkpoints, and next actions across context clears. Integrates with project-planning skill to convert IMPLEMENTATION_PHASES.md into trackable session state. Use when starting new projects after planning, resuming work after context clear, or managing complex multi-phase implementations. Keywords: session management, SESSION.md, session handoff protocol, context handoff, multi-session projects, phase tracking, git checkpoints, session state tracking, resume work, context clear, phase progress tracking, implementation phases, verification stage, debugging stage, next action tracking, work continuity, session recovery, context management, phased implementation tracking
Track progress across work sessions using SESSION.md with git checkpoints and concrete next actions. Converts IMPLEMENTATION_PHASES.md into trackable session state with phase status, progress markers, and recovery points. Use when: starting projects after planning phase, resuming work after context clears, managing multi-phase implementations, or troubleshooting lost context, missing progress tracking, or unclear next steps.
Master prompt engineering for AI models: LLMs, image generators, video models. Techniques: chain-of-thought, few-shot, system prompts, negative prompts. Models: Claude, GPT-4, Gemini, FLUX, Veo, Stable Diffusion prompting. Use for: better AI outputs, consistent results, complex tasks, optimization. Triggers: prompt engineering, how to prompt, better prompts, prompt tips, prompting guide, llm prompting, image prompt, ai prompting, prompt optimization, prompt template, prompt structure, effective prompts, prompt techniques
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.