Loading...
Loading...
Found 204 Skills
Supplies the approval rule another RHDH skill applies when it is already about to change something outside the session: how to state each operation, what approval binds to, what to report afterwards, and how to keep credentials out of a plan preview. Cited by name from the skill doing the work. Not an entry point — it performs no forge, Jira, or repository action itself, and a request to open, comment, transition, push, or post belongs to the skill that owns that target.
Read an academic paper together in three passes of increasing depth — a bird's-eye profile, an interactive close reading, and a line-by-line derivation or reproduction — using this directory as a reading workspace that remembers you and your papers across sessions. Give it PDF paths or a title, arXiv ID, or DOI.
Comprehensive citation management for academic research. Search Google Scholar and PubMed for papers, extract accurate metadata, validate citations, and generate properly formatted BibTeX entries. This skill should be used when you need to find papers, verify citation information, convert DOIs to BibTeX, or ensure reference accuracy in scientific writing.
Use when a startup is approached by a prospective partner and someone has to decide should we sign this partner, at what partner tier (referral / reseller / OEM / SI-consulting / strategic alliance), with what joint GTM commitment, and at what revshare. Classifies partner tier from independent-demand evidence vs. preferential-terms hunting, designs a 90-day joint GTM plan, models revshare against direct-sale margin, and surfaces kill criteria for unwinding under-performing partnerships. For Head of Partnerships, Head of BD, and Founder-CEOs doing reseller agreement, OEM deal, or strategic alliance review — not technical sale enablement, not channel cost economics, not M&A.
Facilitates the final step of a proven customer-interview method: distilling everything a round of interviews produced (GOALS.md, HYPOTHESES.md, QUESTIONS.md, and a directory of per-interview debriefs) into a single FINAL-REPORT.md the whole company can use. Top: a summary as brief as possible without losing salient information. Below: numbered findings (F1, F2, …) tagged validated / disproved / directional / watch / untested, every one citing debriefs and quoting customers verbatim, plus per-area briefs that marshal the evidence for ideal-customer definition, positioning, pricing, marketing & sales, and product priorities. Load when the user says 'write up what we found from the interviews,' 'summarize the interview results for the team,' or 'turn the interviews into a report.' Do NOT load for updating hypotheses from interviews (the synthesis step), for recording one conversation (the debrief step), or for actually doing the positioning, ideal-customer, or pricing work the report feeds.
Bun runtime API reference for TypeScript scripts. Covers Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite, Bun.sql() for PostgreSQL/MySQL via DATABASE_URL, Bun.s3 for S3-compatible storage, Bun.redis for Redis/Valkey, Bun.Archive for tarballs, Bun.Image image processing, Bun.WebView headless browser automation, Bun.cron in-process scheduler, JSONC/JSON5/JSONL/markdown (named imports), Bun.hash, Bun.password, compression, and scripting utilities. Use when writing scripts, automating tasks, querying databases, working with S3 storage, Redis caching, processing images, automating a headless browser, parsing markdown/JSON variants, or doing file processing in a Bun project. Signals: bun.lock, bunfig.toml, DATABASE_URL, REDIS_URL, AWS_ACCESS_KEY_ID, Bun.$ usage Not for bun CLI commands (bun-cli skill), non-Bun runtimes, or ORM CLI tooling
Use to ride a trend — a trending sound, format, meme, hashtag, news moment, or cultural conversation — to earn reach by attaching the brand to something already getting attention (a.k.a. trendjacking / newsjacking). Run when the user says "trend," "trending," "jump on this trend," "trendjack," "newsjack," "is this trend worth doing," "make this go viral," or wants to react to a current moment. Reads brand-profile, voice, and audience first, then runs three gates — FIT, SAFETY, and TIMING — before executing a fast, on-brand remix and handing to the right content skill (tiktok-script, reels-script, caption-writer) and scheduling-and-queue. Refuses to trendjack tragedies or divisive moments and won't force irrelevant trends; live trend discovery needs current scanning — this skill vets and executes. For meme-format craft, cultural fluency, and meme IP/likeness judgment ("make a meme," "is this meme safe"), route to meme-and-culture.
Social media analytics and reporting — read native platform data honestly and turn it into next actions. Use when someone wants to "check my analytics," "see how my posts are doing," "build a social media report," "which content is working," "what metrics/KPIs should I track," or to turn performance data into next steps. Measures goal-mapped SIGNAL metrics (saves, shares, watch time/retention, engagement-rate-by-reach, follower-growth-rate, CTR, conversions) — not vanity (followers/impressions/likes) — and closes the loop. Uses the METER framework. Reads brand-profile + social-strategy (goals) first. WoopSocial has NO analytics surface, so this reads NATIVE platform dashboards (+ GA4/UTM) and interprets numbers the human provides; it NEVER fabricates a metric. Feeds content-recycling, experimentation, competitor-analysis, and every growth skill. Distinct from goals-and-kpis (sets targets) and experimentation (runs tests).
Use when an agent is asked "what did I (or my team) work on yesterday / this week / today" across provider data in a relayfile mount (Linear, GitHub, Notion, Slack, Confluence, Jira, etc.). Tells the agent to consult the pre-computed `digests/yesterday.md` (and sibling digest files) at the workspace root BEFORE doing manual exploration with `ls`/`grep`/`find`. The digest is deterministic, exhaustive over the window, and costs one file read instead of dozens of provider queries.
Case Radar. Given a new thing (new tool/new concept/new ecosystem), scan the ecosystem to find interesting real-world cases, focusing on capturing "authentic assets" (screenshots/source code/demos) instead of GitHub homepage, and output a browsable HTML case collection. Triggered when users say "See what people are doing with X", "Scan the X ecosystem", "What new ways are there to use X in the market", "Show me authentic cases of X", or "/case-radar". Not suitable for: ① In-depth research with clear objectives (use long-research) ② Writing articles/creating PRDs (use writing-assistant / prd-doc-writer) ③ Pure knowledge-seeking without needing HTML (just ask directly).
Search, filter, and format entries from BibTeX or BibLaTeX .bib files for research workflows. Use when a user wants to find papers, search a bibliography, filter a library, or look up references by topic, author, year, venue, DOI, arXiv ID, keywords, annotation, abstract, or entry type. Handles Zotero-exported libraries. Supports compact search expressions such as author:, year-gte, type:, and has:, combined filters, research-oriented output fields, raw BibTeX export, and LaTeX/Typst citation snippet generation.
Check the consistency and authenticity risks of citations and references in NSFC proposal text (read-only): Verify the existence of bibkey, format issues such as BibTeX fields and DOI, and generate structured input for the host AI to evaluate item-by-item whether the text expression actually cites the literature; by default, only an audit report is output, and the proposal or .bib file is not directly modified (unless the user explicitly requests it).