Manage WeChat Official Account drafts and publication with explicit preview, confirmation, and post-publication status checks.
Source text: Chinese
Skills in this repository
SkillsMP has collected 91 skills from Devin-AXIS/iPolloWork. Open a skill to review its source and details.
Devin-AXIS/iPolloWorkShowing 40 of 91 collected skills.
Manage WeChat Official Account drafts and publication with explicit preview, confirmation, and post-publication status checks.
Source text: Chinese
Turn bounded draft, publication, and comment evidence into a concise WeChat Official Account operating review and next-step plan.
Source text: Chinese
Dispatch due Xiaohongshu browser jobs to locked account workers.
Source text: Chinese
Edit an image from the active iPolloWork Image Studio selection or mask without overwriting the source image.
Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.
Electron and Den, desktop plus cloud, two-sandbox e2e, cloud auth, marketplace, org policy, worker proxy, provider sync, desktop handoff. Validate Electron against a Daytona Den server with unified proof.
frame proof, HTML frames, screenshots, recording, PR proof, e2e evidence, validate visually. Daytona artifacts workflow for validated screenshots and optional videos.
create a fraimz, make fraimz, prove it works, frame proof, PR proof, validate experience, e2e evidence, fraimz.html. The full fraimz loop — frame the claim, drive the real app via CDP, validate/repair, output fraimz.html. Use whenever a task ends with "please…
do e2e tests, run e2e, validate feature, prove it works, PR proof, frame proof, pnpm evals. Launches iPolloWork on Daytona or local Electron and runs the coded eval flows via CDP. Launch + run mechanics; the proof loop itself is the fraimz skill.
Let the OpenCode host delegate code review, development, and research tasks to DeepSeek Harness.
Source text: Chinese
Search and summarize material from the Acme research service.
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
Creates and maintains Figma Code Connect template files that map Figma components to code snippets. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.ts or .figma.js files.
Use this skill when implementing a Figma design as code (design → code) — the read-FROM-Figma direction. Triggers: 'implement this Figma design', 'build this screen from Figma', 'turn this Figma into code', 'code this up from Figma', 'design to code', or a…
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma',…
Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, create individual components with proper variant sets and variable bindings, set up theming (light/dark…
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write…
This skill helps agents use Figma's use_figma MCP tool in the Slides context. Can be used alongside figma-use which has foundational context for using the use_figma tool.
Diagnose failing GitHub Actions runs from bounded run, job, and step evidence, propose a focused fix, and modify the local checkout only when the requested task includes implementation.
Publish intentional local changes by confirming scope, creating a branch when needed, staging selected files, committing, pushing, and creating a Draft Pull Request through the connected GitHub service.
Inspect unresolved GitHub pull request review threads, group actionable feedback, implement selected fixes locally, and only reply or resolve threads after explicit user intent.
Use the connected iPolloWork GitHub service to inspect repositories, pull requests, issues, reviews, and Actions, then route focused work to the review, CI, or publish skill.
Keep a Linear issue aligned with implementation evidence, acceptance criteria, code review, and deployment state while avoiding premature completion claims.
Produce concise Linear project updates from current milestones, completed and blocked issues, delivery risks, and next actions.
Build a realistic Linear cycle plan from current priorities, dependencies, estimates, carryover, and team capacity without silently rescheduling work.
Triage Linear issues using bounded searches, duplicate checks, explicit team and project scope, and evidence-backed priority recommendations.
Query and update Notion databases with explicit database identity, property-aware inputs, bounded reads, and confirmation before material writes.
Search connected Notion pages and databases, verify the relevant sources, and produce concise answers that preserve links and uncertainty.
Convert meeting material into decisions, action items, owners, dates, and open questions, then save it to an explicitly selected Notion destination.
Turn project evidence into maintainable Notion briefs, decision records, runbooks, and status documents without overwriting unrelated content.
Verify a production fix by linking the changed code and release to Sentry issue state and post-release event trends without resolving issues prematurely.
Investigate a Sentry issue from bounded event, stack, tag, environment, release, and timeline evidence before proposing a code change.
Compare bounded Sentry windows and releases to identify new issues, regressions, frequency changes, and user-impact changes.
Assess release health from Sentry errors, regressions, affected users, crash evidence, and comparison with the previous stable release.
Analyze Stripe customers, subscriptions, prices, invoices, payment status, and lifecycle transitions with explicit environment and object scope.
Investigate Stripe payment failures and unexpected outcomes from exact object IDs, lifecycle state, events, amounts, currency, refunds, and dispute evidence.
Reconcile bounded Stripe payment and payout records with supplied business records while preserving object IDs, currency, time zone, and discrepancy evidence.