Trendende Agent Skills

Overlay doctrine for the embedded-captions workflow — the caption model (drop / rail / embed) and the rule that captions are an overlay composited on top of the film, never a reserved bottom band.

Decides whether, where and when to launch a developer community, then plans its seeding and first 90 days - venue selection, founding-member seeding, go/no-go criteria, the cheaper no-community alternatives, and shutdown criteria.

Helps SaaS products reduce both voluntary and involuntary churn through well-designed cancel flows, dynamic save offers, proactive retention, and failed payment recovery strategies.

Submit products to startup, SaaS, AI, agent, MCP, no-code, and review directories for backlinks, domain rating, and discovery.

Relentless design-tree interview until the frontier is empty.

Set up, audit, verify, or fix website conversion tracking.

Chart multi-session fog as a plan-file map of decision tickets.

House-style oversized macOS cursor technique for HyperFrames launch videos, using off-screen entry, tip-targeting, and click-ignition to carry the viewer's eye and activate scenes.

Writes or reviews a shooting-ready script for a technical video or screencast - a two-column visual/narration beat sheet with a 30-second hook, code-on-screen pacing, chapters, a runtime budget, accessible narration, a cut list and a YouTube description with one CTA.

Designs an open-source project's ongoing distribution mix after the launch window - registry metadata, code-host discovery surfaces, curated lists, downstream packaging, extension and connector marketplaces, the release stream, dependency-graph position, creator seeding, and procurement trust signals - ranked against real maintainer capacity.

Master the render-correctness prerequisites for scene-to-scene transitions in HyperFrames launch videos, including the opaque stage-ground white-flash guard and the injector's overlap, hold, ping-pong, and template-stamping mechanics on the master timeline.

Decides whether and how to invest in structured developer education, such as learning paths, a developer academy, hands-on labs, or a badge or certification rung on top - instead of more ad-hoc content, then designs its operating model, staffing, refresh cadence, measurement and kill rules.

Design, optimize, and analyze referral, affiliate, or word-of-mouth programs to turn customers into growth engines.

Plans, lands and advances a developer relations career from the candidate side - developer advocate, developer evangelist, DevRel engineer, community manager, developer educator, DX engineer.

Plan, evaluate, and build free marketing tools to attract leads, boost SEO, and increase brand awareness.

Build, modify, debug, migrate, review, or verify TypeScript MCP servers and MCP Apps with mcp-use.

Audit and optimize App Store and Google Play listings with ASO best practices, providing scores and a prioritized action plan.

The canvas-design skill creates beautiful visual art in .png and .pdf documents using design philosophy, suitable for posters, art, and other static designs.

Designs and runs a recurring developer meetup or user group - purpose and host model, format menu, cadence, a standing speaker pipeline, in-kind venue and food sponsors with their conduct limits, no-show planning, the attendee-to-co-organizer ladder, and a health scorecard.

Designs a company's developer relations program from the top - the business driver that funds it, the two goals it is allowed to serve, the pillar mix (advocacy, marketing, enablement, community) for its stage, audience priority, build-vs-buy per bet, staffing sequence, and a written refused list.

Designs and verifies the path a stranger walks to their first merged contribution on an open-source project - the CONTRIBUTING file, the good-first-issue queue, a clone-to-passing-tests command that works cold, and the first-pull-request review and recognition loop, scored against a blocking-plus-weighted rubric.

Decides how a company engages a named open standard or protocol - ignore it, consume it, certify conformance, extend it, contribute upstream, co-found a spec with peers, or drive its own as a de facto standard - plus the venue (Git-based spec, foundation, consortium, IETF/W3C/OASIS, ISO transposition), the patent-licensing mode, the conformance plan and the kill rule.

Build verified, scored, ready-to-outreach prospect lists across B2B SaaS, general B2B, local small businesses, and early-stage demand-signal discovery.

Decides whether, when and how far a developer product should open into a platform other companies build on - extension points, partner-built integrations, third-party apps, a complement ecosystem - and what that permanently obliges you to.

Writes or audits a developer quickstart that carries a reader from zero to one verified success - minimal path, copy-paste commands, expected output at every step, fail branches, and a cold-run time budget.

Plans a quarter of developer-relations content as a dated slot plan with named owners and reviewers - fixed anchors (releases, launches, CFP deadlines, conferences), a surface, pillar, journey and shelf-life mix, and sizing against real writing and review capacity.

Designs the go-to-market motion for a developer-facing product - bottom-up self-serve adoption, developer-influenced sales, top-down with developer proof, or ecosystem-mediated distribution - plus the self-serve entry, the developer-to-buyer handoff rule and the land-and-expand path.

Before starting any developer-relations work - and again at the start of each new session on an existing DevRel project - routes the current task to the right skill of the samber/developer-relations-skills collection, or says plainly that none fits, then bootstraps or resumes the project's shared devrel-context.md artifact.

Builds a developer relations measurement framework - a handful of metrics tiered from reach to product and business impact, each with a written attribution rule, a baseline-derived target, an owner and an action, and vanity metrics cut.

Decides what a company open-sources and what stays proprietary, names the strategic motive for each side of the line, says who owns the decision, and states what the company commits never to close.

>-

Builds a prioritized keyword list for technical search queries (error strings, "how to X in Y" tasks, integration intents, comparisons, migrations) mined from docs search logs, support tickets, issue trackers and first-party query data rather than keyword-tool volume.

Build and leverage online communities to drive product growth and brand loyalty, covering community strategy, platform selection, member journey, ambassador programs, and health metrics.

Chooses and documents an open-source project's governance model - decision rights, maintainer roles and promotion, voting and consensus rules, conflict escalation, succession, trademark and asset control, and whether to join a foundation or fiscal host.

Designs an issue and pull-request triage system a maintainer team can sustain - response targets sized against real capacity, the label taxonomy, intake cuts through structured forms and off-tracker routing, a separate security-report path, triage duty assignment, and the closing, staleness and volume-gating policy.

Determine which marketing efforts truly drive conversions and revenue, choose or interpret attribution models, and reconcile conflicting numbers across tools.

>-

Builds a developer-event sponsorship plan - which conferences, meetups and hackathons to sponsor, at which tier, with which on-site activation, and how to prove the money worked.

[FINANCIAL EXECUTION] Create and launch meme coins and crypto tokens on launchpads (Pump.fun, FourMeme, Bonk, BAGS, Flap, Klik, Clanker, etc.) via bonding curve fair launch, or query token creation stats by launchpad via GMGN API.

>-

Herdr is a terminal multiplexer for coding agents, managing workspaces, tabs, and panes, and controlling agents within them.

Builds a company's open-source sponsorship portfolio - which projects and maintainers to fund, through which allocation model, at what amount each, and how to prove it worked.

Prepares a guest for someone else's technical podcast, YouTube interview, livestream or panel - show reconnaissance, the angle, an ABT message spine backed by evidence and stories, a self-contained opening answer, clip-safe sound bites, depth calibration, recording-day mechanics, and the post-publication promotion loop.

Independently research and write an AI-narrative / due-diligence card for a crypto token — the kind of "叙事分析" card that covers what story a token is telling and what's independently verifiable about its social spread.

Optimize signup, registration, or trial activation flows to reduce friction and increase completion rates.

>-

Chooses an open-source project's license and contribution policy as one decision - permissive vs weak, strong or network copyleft, dependency-driven compatibility constraints, DCO vs CLA vs nothing, dual licensing and open core, source-available options (BUSL, FSL, Elastic License, SSPL), and the fork risk of relicensing.

Benchmarks a competitor's developer relations motion from publicly observable signals - documentation and quickstart quality, open-source repository health, community size and responsiveness, Q&A tag activity, content cadence by format, event presence, hiring signals - and returns a gap plan with a close, ignore or counter verdict per row.