「gt」の検索結果

Sales, GTM & Marketing Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.

日本語の概要は準備中です。原文の説明を表示しています。

低信息量过滤工具。读取结构化数据文件，对指定文本列同时校验字符总数与行数是否落在阈值区间内，输出过滤后的合规行。 当用户提到低信息量过滤、字符数筛选、短文本过滤、超长文本过滤、行数过滤、信息量阈值等需求时使用此skill。 即使用户没有明确说出"低信息量"，只要任务涉及同时按字符数和行数两个维度过滤文本行，就应该使用此skill。 不负责按单词数过滤（用words_num_filter）、按token数过滤（用token_num_filter）、按最长单行长度过滤（用maximum_line_length_filter）或按平均行长度过滤（用average_line_length_filter）。与这些skill的关键区别在于：本skill同时校验字符总数与行数两个维度，且原生支持CSV/TSV/Excel多列输入、不依赖data_juicer。

日本語の概要は準備中です。原文の説明を表示しています。

Generate an energy-optimized, time-blocked daily plan based on circadian rhythm research and GTD principles

日本語の概要は準備中です。原文の説明を表示しています。

Counts RNA-seq reads overlapping GTF gene features. Takes sorted STAR BAMs plus GTF; outputs a per-gene tab-delimited matrix across samples. Handles strandedness (0/1/2), paired-end, multi-sample batch counting in one command, and outputs assignment statistics. Use Salmon for alignment-free quantification; use featureCounts when STAR BAMs already exist.

日本語の概要は準備中です。原文の説明を表示しています。

Query IUPHAR/BPS Guide to Pharmacology (GtoPdb) for receptor-ligand interactions, target/ligand metadata, families, and approved drugs. Affinities (pKi/pIC50/pKd), action (Agonist/Antagonist/etc.), species, structures (SMILES/InChI). No auth. Always resolve targets via geneSymbol/accession; most metadata lives in sub-resources (/databaseLinks, /structure, /synonyms).

日本語の概要は準備中です。原文の説明を表示しています。

アナリティクスのトラッキング設定・改善・監査を支援するスキル。 「トラッキングを設定」「GA4を導入」「コンバージョン計測」「イベントトラッキング」「UTMパラメータ」「GTMの設定」等のリクエストで発動。 A/Bテスト計測は ab-test-setup を参照。

Align phases with GTM strategy, persona tiers, and KPI targets

日本語の概要は準備中です。原文の説明を表示しています。

Get the first 50 real users through channels the user's ICP already uses. Use when the product shipped and nobody came, the user is "posting more" with no result, or is reaching for paid ads before product-market fit.

日本語の概要は準備中です。原文の説明を表示しています。

Build authority by teaching the problem space, not announcing features. Use when the user finds "marketing" distasteful and does none, publishes only product updates, or wants a sustainable content and GitHub-README strategy that developers actually respect.

日本語の概要は準備中です。原文の説明を表示しています。

Coach the user through actually selling: finding the champion and the buyer, running the first sales conversations, demoing their use case, handling "let me think about it," and closing the first paying customers yourself. Use when developers love it but nobody pays, you've never sold anything and freeze on the conversation, or deals keep stalling on "we'll think about it."

日本語の概要は準備中です。原文の説明を表示しています。

Help the user decide what to charge and how to package it: the value metric, the tiers, the free-to-paid line, and finding the actual number. Use when the user is guessing at a price, priced too cheap and can't change it, is stuck on free vs paid, or believes "developers won't pay" so never charges.

日本語の概要は準備中です。原文の説明を表示しています。

Run developer customer discovery via a Technical Advisory Board (TAB). Use when the user has never interviewed a user who isn't a friend, is inventing messaging from a conference room, or is guessing at the roadmap instead of hearing the pain firsthand.

日本語の概要は準備中です。原文の説明を表示しています。

Position an AI product when everyone claims AI and skeptics call it "just a wrapper." Find the real wedge (data, workflow, trust, domain), make reliability the differentiator, answer "won't the big labs just build this," and stop leading with "AI-powered." Use when your AI or dev tool blends into a sea of similar demos, buyers doubt the accuracy, or you can't say why you win when the model is a commodity.

日本語の概要は準備中です。原文の説明を表示しています。

Write a developer value proposition that is specific, provable, and free of puffery. Use when the messaging leans on "powerful," "better," "seamless," or "best-in-class," when claims have no proof, or when the same line is supposed to reach both the developer and the buyer.

日本語の概要は準備中です。原文の説明を表示しています。

Define a real ICP and the developer personas in the sale. Use when the user says the product is "for developers," can't name who would say no, or is marketing to whoever holds the budget instead of who actually adopts.

日本語の概要は準備中です。原文の説明を表示しています。

Build a positioning and narrative where the developer is the hero and a real trend is the villain. Use when the messaging describes the product instead of the problem, sounds like every competitor, or has no urgency because nothing is at stake.

日本語の概要は準備中です。原文の説明を表示しています。

Turn hand-made first-50 traction into self-reinforcing acquisition loops, so the next 5,000 users come from usage, not founder hours. Use when growth stalls the moment the user stops pushing, every signup traces back to a DM or one launch spike, or they're reaching for "more channels" when the real gap is that using the product creates no new users.

日本語の概要は準備中です。原文の説明を表示しています。

Structure a dev-tool homepage that converts developers into champions. Use when the landing page is written for the buyer instead of the developer, reads as salesy, buries what the product does, or makes it hard to start. Pairs with the ShipReady homepage audit.

日本語の概要は準備中です。原文の説明を表示しています。

Plan a developer launch (Show HN, Reddit, Product Hunt) that earns goodwill instead of a flaming. Use when the user is sitting on a launch out of fear, wants to "go viral," or is about to post a press-release-style announcement to a developer community.

日本語の概要は準備中です。原文の説明を表示しています。

Turn a curious developer into an activated one: the docs, the quickstart, and the first-run experience that gets them to their first real win fast, and back again. Use when people sign up or star the repo but never get it working, come once and never return, or you're about to pour traffic into a first-run that leaks.

日本語の概要は準備中です。原文の説明を表示しています。

Product marketing, positioning, GTM strategy, and competitive intelligence. Includes ICP definition, April Dunford positioning methodology, launch playbooks, competitive battlecards, and international market entry guides. Use when developing positioning, planning product launches, creating messaging, analyzing competitors, entering new markets, enabling sales, or when user mentions product marketing, positioning, GTM, go-to-market, competitive analysis, market entry, or sales enablement.

日本語の概要は準備中です。原文の説明を表示しています。

Preprocess CLIP-seq reads (eCLIP, iCLIP, iCLIP2, iCLIP3, irCLIP, PAR-CLIP, FLASH) with protocol-specific UMI extraction, adapter trimming, length filtering, and post-alignment PCR-duplicate collapse. Use when raw CLIP FASTQ must be turned into deduplicated, crosslink-preserving BAM input for peak calling; choosing between two-pass and single-pass adapter trimming; deciding minimum read length; or mapping UMI patterns to specific eCLIP/iCLIP/iCLIP2/iCLIP3 library preps.

日本語の概要は準備中です。原文の説明を表示しています。

Build Tier 1/2/3 cold outreach sequences differentiated by personalization depth and research signal strength during PRD v0.9 Go-to-Market. Triggers on requests to plan cold outreach, founder-led sales, or when user asks "cold email sequence", "outbound campaign", "founder outreach", "LinkedIn outreach", "Tier 1 personalization", "predictable revenue", "sales cadence", "BDR sequence". Outputs GTM-OUT-* sequence entries and lead-list references.

日本語の概要は準備中です。原文の説明を表示しています。

Define lifecycle stages and marketing → sales / CSM handoff rules for leads captured by GTM channels during PRD v0.8 Deployment & Ops. Triggers on requests to set up lead lifecycle, define MQL/SQL criteria, build handoff process, or when user asks "what's an MQL?", "marketing to sales handoff", "lead lifecycle", "lead routing", "RevOps", "MOPS", "marketing operations". Outputs BR-MOPS-* lifecycle rules and GTM-MOPS-* handoff flow entries.

日本語の概要は準備中です。原文の説明を表示しています。