3,040 件 ・ 関連度順
概要と使いどころ
This skill should be used when the user asks to "write a comment for this LinkedIn post", "help me respond to this post", "what should I comment on this", "craft a LinkedIn comment", or when Genesis identifies high-value posts in the user's network worth engaging with. Also triggered by "how should I engage on LinkedIn" or "help me be more visible on LinkedIn".
日本語の概要は準備中です。原文の説明を表示しています。
Foundational voice authority and AI humanizer — writes content in the user's authentic voice with built-in AI detection, and supports stealth / anti- attribution writing (forum personas, anonymous posts, "write as not-me"). Use when asked to write/draft/generate content, invoke /voice, /write-as-me, or /humanize, run voice calibration, check "does this sound like me?", "make this sound human" / "de-AI this", "write a forum post as [persona]", or run AI detection ("does this sound like AI?", "check for AI patterns", "anti-slop check"). Do NOT use this skill for code, technical docs, or any output the user has not asked to be written in their voice — code styling defers to the separate code-voice skill.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "write a LinkedIn message", "draft a connection request", "help me reach out to someone on LinkedIn", "write an InMail", "message this person", or when the prospect-researcher skill identifies a high-value contact worth reaching out to. Also triggered by "how should I approach [person/company]" in a LinkedIn context.
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
ALWAYS start here when the user wants a page OR a doc: page, living page, doc, document, living doc, bongo or bongo doc (the old name; new ones are made here, not by a Bongo connector), shared or collaborative doc, write-up, one-pager, memo, brief, proposal, plan, spec, report, meeting notes, notes, checklist, tracker, or anything to read, edit, comment on and share together — 'write this up', 'put this in a doc', 'draft a brief', 'jot this down somewhere we can share and edit', 'turn this file into a page' — the DEFAULT for any of these when no file format is named; a Word/.docx, PDF, .pptx or .xlsx FILE asked for by name goes to that format's skill instead. Also whenever the pages connector is about to be used to create a page. Not for READMEs, code or docstrings. A lowercase /pages as its own word anywhere in the message (not in a URL, path or longer name) invokes this skill whatever else is asked — a summary, an answer, a comparison, a plan: the page is the reply.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain the slopus/happy open source project. Triage issues, manage the GitHub project board, draft closing comments, find duplicates, check if bugs are fixed on main, and engage with community contributors. NEVER posts comments or closes issues without showing exact text and getting approval first.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrating super-premium landing-page pipelines (Discover to Launch) across 6 craft axes with rubrics and quality gates. Not for a single LP section (Funnel) or design-only chains (Atelier).
日本語の概要は準備中です。原文の説明を表示しています。
Constructing landing pages from a focused section to a premium multi-stage studio pipeline: structure, copy, conversion, responsive build, craft gates, and launch handoffs. Use when building or optimizing an LP, CTA, conversion flow, or premium launch surface.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate a teacher-drafted central historical question for its capacity to drive genuine historical inquiry. Use when assessing whether a question will generate real evidence-weighing or produce shallow responses.
日本語の概要は準備中です。原文の説明を表示しています。
Draft launch or promotion copy for a shipped feature.
日本語の概要は準備中です。原文の説明を表示しています。
Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets. Also use when the user mentions 'AI image generation,' 'generate an image,' 'create a graphic,' 'product mockup,' 'hero image,' 'social media graphic,' 'banner image,' 'cover photo,' 'profile banner,' 'listing screenshot,' 'Flux,' 'Flux Kontext,' 'Midjourney,' 'DALL-E,' 'GPT Image,' 'ChatGPT Images,' 'Ideogram,' 'Gemini image,' 'Nano Banana,' 'Recraft,' 'Stable Diffusion,' 'Canva,' 'Figma,' 'image optimization,' 'compress images,' 'WebP,' or 'OG image.' Use this for general-purpose marketing image creation and optimization. For paid ad image creative and platform-specific ad specs, see ad-creative. For video production, see video.
日本語の概要は準備中です。原文の説明を表示しています。
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.
日本語の概要は準備中です。原文の説明を表示しています。
[BETA] Offload plan phase to Claude Code's ultraplan cloud — drafts remotely while terminal stays free, review in browser with inline comments, import back via /gsd:import. Claude Code only.
日本語の概要は準備中です。原文の説明を表示しています。
Medium-native long-form research, author-assistance, writing, editing, review, topic discovery, publication matching, and packaging workflow. Use when creating, outlining, researching, revising, auditing, or packaging Medium stories, essays, tutorials, reviews, explainers, comparisons, case studies, publication submissions, Medium 长文, Medium 选题, Medium Topics, or Medium publishing packs that need original author perspective, narrative craft, relevant topics, responsible AI disclosure, and reader-centered distribution readiness.
日本語の概要は準備中です。原文の説明を表示しています。
LinkedIn-native long-form article and newsletter writing workflow for LinkedIn and Google-to-LinkedIn topic discovery, business-depth research, professional thought leadership, evidence-led drafting, final humanization, discussion design, SEO settings, auditing, and publish-ready packaging. Use when creating, outlining, researching, enriching, rewriting, humanizing, auditing, or packaging LinkedIn Articles, LinkedIn newsletters, LinkedIn long-form posts, LinkedIn thought leadership, LinkedIn B2B articles, LinkedIn 长文, LinkedIn 专栏, LinkedIn 话题调研, LinkedIn 商务内容, 去 AI 化编辑, or LinkedIn 发布包.
日本語の概要は準備中です。原文の説明を表示しています。
Clarify research intent and produce draft readiness for human exit.
日本語の概要は準備中です。原文の説明を表示しています。
Clone, port, or convert features from any GitHub repo into your project. Use when stealing patterns from external repos or porting proven code. Understand before copy, challenge before implement. 4 modes: port (rewrite), compare (analysis), copy (transplant), improve (copy + optimize).
日本語の概要は準備中です。原文の説明を表示しています。
Create marketing assets and execute launch strategy. Use when crafting landing copy, social banners, SEO meta, blog posts, or video scripts — coordinates with launch (deploy + announce) and the @rune-pro/growth pack (research / content / CRO).
日本語の概要は準備中です。原文の説明を表示しています。
把小说写成"供修改的 Word 草稿"。当用户要把稿子导成 Word/docx、要分章节带目录、章标题左对齐、要标出可以改的地方让自己修改、或说"先写个大概我来筛选修改"时使用。产出 Word 草稿(目录+第X章左对齐+【修改】红色高亮建议)，命名《书名》修改N，绝不覆盖原文。
日本語の概要は準備中です。原文の説明を表示しています。
Build, critique, and refine academic posters from a paper, LaTeX project, reference draft image, HTML/CSS source, PPT/PDF outputs, or local figure assets. Use when Codex is asked to create or improve a research poster, convert a poster design to HTML/PDF/PPTX, fix poster layout/typography/overflow/blank-space issues, or preserve paper figures and result semantics in a poster.
日本語の概要は準備中です。原文の説明を表示しています。
Generate, critique, and iterate image-generation prompts for high-fidelity academic paper poster reference mockups before implementing HTML/PDF/PPTX. Use when Codex is asked to create a poster concept image, imagegen prompt, visual reference draft, layout mockup, or "生图" design for ACL/EMNLP/NeurIPS-style A0 posters from a paper, figures, metrics, logos, QR codes, or an existing poster screenshot.
日本語の概要は準備中です。原文の説明を表示しています。
Draft, confirm, and synchronize research status, evidence, blockers, and review-ready GitHub summaries using the Research Memory skill, GitHub conventions, and file templates.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to pressure-test a product, internal-tool, or OSS concept against Amazon's Working Backwards PRFAQ gauntlet before committing to a spec. Triggers on: "work backwards", "write a PRFAQ", "press release first", "is this idea worth building", "pressure-test this concept", "filter this before brainstorm", "is this a real product". Also catches solution-first pitches ("I want to build X that does Y") and technology-first pitches ("use AI to...") that need customer-first filtering. Produces a binary pass/fail verdict, not a polished doc. Hardcore coaching — direct, skeptical, concrete. On pass, hands off to brainstorm-beagle with a concept brief. Does NOT write code, plan implementation, scaffold projects, or draft specs.
日本語の概要は準備中です。原文の説明を表示しています。