搜索
搜索结果
46 results for "public relations"
public-relations
当用户需要公关、付费媒体、新闻报道、记者外联或媒体策略方面的帮助时使用（非拉取请求）。当用户提及“PR”、“公关”、“新闻”、“新闻稿”、“媒体报道”、“媒体外联”、“向记者推销”、“获得报道”、“媒体列表”、“媒体资料包”、“新闻劫持”、“HARO”、“Qwoted”、“Featured”、“Help A Reporter”、“记者请求”、“科技媒体”、“TechCrunch”、“付费媒体”、“思想领导力投放”、“专栏文章”、“客座文章”、“媒体联系人”或“如何获得媒体报道”时也适用。用于付费媒体工作——寻找记者、推销故事、新闻劫持和回应新闻请求。对于初创公司/SaaS/AI目录提交，请参见 directory-submissions。对于产品发布，请参见 launch。对于社交媒体互动，请参见 social。对于面向潜在客户的冷邮件外联，请参见 cold-email。
coreyhaines31
build-in-public
Designs a sustainable build-in-public practice for an open-source project or developer tool: how far up the disclosure ladder to go (shipping log, decisions, failures, metrics, revenue), a cadence the maintainer can hold, the platform mix, and the boundaries that keep security, customer and roadmap detail off the public record. Use whenever someone mentions building in public, a devlog, weekly updates, an open-startup or transparency dashboard, sharing metrics or revenue openly, fear of copycats, oversharing, wanting to stop publishing numbers, or a stalled practice they want to restart, even if they never say "build in public". Covers solo maintainers, bootstrapped and funded devtools teams. Not for a one-time launch; use samber/developer-relations-skills@oss-launch.
samber
ncats-arax
Queries the NCATS Translator ARAX production API for bounded, typed, provenance-rich one-hop and endpoint-pinned two-hop biomedical knowledge-graph relationships. Use for Biolink-constrained RTX-KG2 lookup, explicit selected-provider ARAX federation, separate entity normalization, qualifier-aware graph traversal, and inspection of TRAPI edge bindings, publications, and knowledge-source provenance. Do not use for inference, ranking, open-ended pathfinding, clinical guidance, or sensitive queries.
k-dense-aievents
When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences. Also use when the user mentions 'event marketing,' 'field marketing,' 'run a webinar,' 'webinar funnel,' 'show-up rate,' 'should we sponsor,' 'sponsor a conference,' 'trade show booth,' 'booth strategy,' 'event ROI,' 'badge scans,' 'event follow-up,' 'speaking slot,' 'CFP,' 'conference talk,' 'host a dinner,' 'user conference,' or 'virtual summit.' Covers all four roles: hosting, sponsoring/exhibiting, speaking, and attending. For product launch moments, see launch. For the partnership side of joint webinars, see co-marketing. For ongoing community programs, see community-marketing. For podcast appearances, see public-relations. For the email sequences themselves, see emails.
coreyhaines31seaborn
与 pandas 集成的统计可视化。用于快速探索分布、关系和分类比较，具有吸引人的默认设置。最适合箱线图、小提琴图、成对图和热力图。基于 matplotlib 构建。对于交互式绘图使用 plotly；对于出版样式使用 scientific-visualization。
k-dense-aisocial
当用户希望为LinkedIn、Twitter/X、Instagram、TikTok、Facebook或其他平台创建、安排或优化社交媒体内容，或需要进行社交聆听和互动分类时使用。当用户提及'LinkedIn帖子'、'Twitter话题'、'社交媒体'、'内容日历'、'社交排期'、'互动'、'病毒式内容'、'我应该发什么'、'重新利用此内容'、'推文创意'、'LinkedIn轮播'、'社交媒体策略'、'增加粉丝'、'TikTok视频'、'Reels'、'Shorts'、'视频脚本'、'视频钩子'、'短视频'、'创建Reel'、'社交聆听'、'品牌提及'、'竞品监控'、'值得评论的热门帖子'或'寻找提问的人'时也使用。用于社交媒体内容创作、重新利用、排期、短视频脚本和社交聆听。对于更广泛的内容策略，请参见content-strategy。对于付费广告，请参见ad-creative。对于赢得媒体，请参见public-relations。
coreyhaines31
academic-plotting
Generates publication-quality figures for ML papers from research context. Given a paper section or description, extracts system components and relationships to generate architecture diagrams via Gemini. Given experiment results or data, auto-selects chart type and generates data-driven figures via matplotlib/seaborn. Use when creating any figure for a conference paper.
orchestra-research
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
get-convexoss-launch
Plans and runs an open-source project launch end to end - name and license clearance, the readiness gate, positioning and one-liner, channel sequencing, the launch-day war room, star-velocity and GitHub Trending mechanics, and post-launch measurement. Use whenever someone is about to release, announce, open-source or "Show HN" a repository, asks how to reach GitHub Trending, wants the first real users or stars for a new library, is planning a Product Hunt post or a multi-day launch week, or asks why a launch fell flat (even if they only say they are pushing a repo public). Covers individual-developer and company adoption. Not ongoing distribution afterwards - use samber/developer-relations-skills@oss-distribution-strategy instead.
sambeross-distribution-strategy
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. Use whenever a maintainer asks how people will keep finding the project, which registries or awesome lists to target, why adoption flattened after launch, how often to release for visibility, or how to spend limited maintainer hours on distribution - even if they only say nobody is using it. Not the launch itself - use samber/developer-relations-skills@oss-launch. Not the build-in-public practice.
samberopen-source-company-strategy
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. Use whenever someone asks "should we open source this?", "what should we open source", "where do we draw the open-core line", "which features stay paid", "who signs off on open sourcing this", or wants a company-level open source strategy rather than a plan for one project - even if they frame it as a licensing question. Produces an asset-by-asset open/closed verdict, a value-capture and irreversibility check, a public non-reversal commitment and a re-evaluation trigger. Not license selection - use samber/developer-relations-skills@oss-license-strategy.
samberdeveloper-case-study
Turns a customer's real production deployment into a technical case study engineers believe - measured numbers tied to how they were measured, before-and-after architecture, published limitations, and cleared naming and quote approval. Use whenever the user mentions a customer case study, a technical case study, a developer adoption or success story, a reference customer, or wants to turn a user interview, migration or production rollout into published proof - even if they only say "a post about how Acme uses us". Do NOT use for a post about your own system - use samber/developer-relations-skills@engineering-blog-post; for your own project's ongoing progress use samber/developer-relations-skills@build-in-public.
samberdevrel-competitor-analysis
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. Use whenever the user asks for a devrel competitive benchmark, a developer experience comparison, "how do we compare to <competitor> for developers", "what is <competitor> doing in devrel", a community size or content cadence comparison, or a docs comparison against rivals - even if they only say "why do they get more developers". Not for measuring your own program alone - use samber/developer-relations-skills@devrel-metrics.
sambertech-podcast-interview-prep
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. Use whenever someone says "podcast guest prep", "I'm going on a podcast next week", "youtube interview prep", "devrel media training", "prep my talking points", "sound bites", "I'm on a panel", or "what do I say when they ask about competitors" - even if they only mention an upcoming recording. Not running your own show - use samber/dev-event-organizer-skills@tech-podcast-youtube-channel.
samberengineering-blog-post
Writes or edits a technical blog post a skeptical developer audience will believe - the right post pattern, evidence behind every claim, published trade-offs and limitations, runnable snippets, and no marketing voice. Use whenever the user wants an engineering blog post, a technical article, a "how we built it" or "we rewrote it in X" story, a debugging write-up, a public postmortem, a benchmark post, or a product post that must not read as marketing, and when they ask to review, edit, de-jargon or de-market an existing technical draft - even if they only call it "the article". Not a teaching tutorial - use samber/developer-relations-skills@developer-tutorial. Not release notes, a migration guide, a case study or a talk.
samberdeveloper-platform-career
Plans a developer-platform career from the candidate side - API Product Manager, Platform Engineer/Architect, Partner/Integration Engineer. Disambiguates "platform engineer" first - the term overwhelmingly means internal developer platforms (Kubernetes, Backstage, golden paths) elsewhere in the industry; this skill covers only the external/public-API-platform track. States the key finding that splits this track from DevRel's - platform compensation rides the general engineering/PM ladder, not a separate undersurveyed one. Covers GitLab's real Partner Engineer ladder, the API-design-vs-system-design interview split, and RFC/design-doc portfolio signals. Use when the user asks how to break into platform/API product work, prep for a platform or API-PM interview, or evaluate an offer. Do NOT use for hiring (samber/developer-platform-skills@developer-platform-hiring) or advocate/community/educator roles (samber/developer-relations-skills@devrel-career).
samberdeveloper-platform-hiring
Employer-side hiring for developer-platform roles - API Product Manager, Platform Engineer/Architect, Partner/Integration Engineer. Disambiguates "platform engineer" first, since the term overwhelmingly means internal developer platforms elsewhere in the industry. Calibrates the scorecard to company archetype (infra/API-first, bolt-on public API, enterprise partner ecosystem), flags a scope-collapse pattern distinct from DevRel's gatekeeper/pit-trap taxonomy, sources from apidays, not PlatformCon's internal-IDP audience, builds the loop from the API-design-vs-system-design interview split, and benchmarks compensation against the general engineering/PM ladder rather than a bespoke platform title. Use when the user asks how to hire a platform engineer, API product manager, or partner/integration engineer, write a posting, or design a loop. Do NOT use for candidate prep (samber/developer-platform-skills@developer-platform-career) or DevRel hiring (samber/developer-relations-skills@devrel-hiring).
samber
press-media-relations
Use when the user asks to "build a media list for my launch", "write a launch press release", or "pitch press under embargo"; produces a three-tier media and analyst list (Tier 1 exclusive candidates, Tier 2 vertical press, Tier 3 communities and newsletters), an embargo pitch timing skeleton keyed to the launch-registry date, a press-release draft in standard structure with no fabricated quotes or numbers, and an analyst briefing outline. Not for press-kit assets — use launch-asset-packager; not for follow-up sequence mechanics — use outreach-manager; not for post-launch news-echo monitoring — use launch-monitor. 媒体名单/禁运期pitch/新闻稿/分析师简报
aaron-he-zhu
thought-leadership-ads
Plan a campaign that promotes an executive's or founder's existing organic posts as paid person-fronted ads - post selection, sequencing, audience and exclusions, permission and governance, budget, and measurement. Use whenever the user mentions thought leader ads, promoting a founder's or CEO's post, sponsoring an employee's or a creator's post, executive content amplification, running ads from a personal profile, or B2B trust ads - even if they never say 'thought leadership'. Covers B2B trust-layer campaigns on professional networks with pipeline-lens measurement, and B2C founder-led brands with direct-response measurement. Plans the campaign only, never the featured person's content: ad copy is mbfinotti/advertising-skills@ad-copy-variants.
mbfinotti
llm-public-opinion-analytics
Multi-platform public opinion analysis assistant with web scraping, LLM-powered analytics, topic clustering, sentiment analysis, and multi-channel alerts
aradotsoadvertising-radar
Build a personalised, time-budgeted watch list of paid-advertising information sources - PPC and paid-social podcasts, newsletters, ad-platform release notes, communities, industry events, and media buyers worth following - with a verification method that keeps it fresh and a disclosure of what each source is selling. Use whenever a media buyer, PPC specialist, or growth marketer asks how to stay current on Google Ads, Meta, LinkedIn, TikTok, or Microsoft Ads changes, which PPC newsletters or paid-social podcasts to follow, which communities or conferences deserve their time, or who to follow in performance marketing - even if they never say 'radar'. Do NOT use for career planning - use mbfinotti/advertising-skills@advertising-career instead.
mbfinottiads
当用户需要关于Google Ads、Meta（Facebook/Instagram）、LinkedIn、Twitter/X或其他广告平台的付费广告活动帮助时使用。当用户提到'PPC'、'付费媒体'、'ROAS'、'CPA'、'广告活动'、'再营销'、'受众定位'、'Google Ads'、'Facebook广告'、'LinkedIn广告'、'广告预算'、'每次点击费用'、'广告支出'或'我应该投放广告吗'时也使用。用于活动策略、受众定位、出价和优化。如需批量广告创意生成和迭代，请参见ad-creative。如需着陆页优化，请参见cro。
coreyhaines31
om-followup-issue-from-pr
Turn a PR into tracked follow-up work — paste a PR or PR-comment link to extract the actionable ask and open a follow-up issue assigned to the @-mention or PR author; for a PR adding a design doc, it opens the missing `Implement:` tracking issue instead. Use for "make a follow-up issue", "create an issue for this", or a pasted PR/comment link with that intent.
open-mercatopaid-ads
当用户需要关于 Google Ads、Meta（Facebook/Instagram）、LinkedIn、Twitter/X 或其他广告平台的付费广告活动帮助时使用。也适用于用户提及 'PPC'、'付费媒体'、'ROAS'、'CPA'、'广告活动'、'重定向'、'受众定向'、'Google Ads'、'Facebook 广告'、'LinkedIn 广告'、'广告预算'、'每次点击费用'、'广告支出'或'我应该投放广告吗'。用于活动策略、受众定向、出价和优化。对于批量广告创意生成和迭代，请参见 ad-creative。对于着陆页优化，请参见 page-cro。
coreyhaines31