「community」の検索結果

Route product-growth requests to one Gingiris specialist skill. Use when broad or explicit requests about launch, Product Hunt, GitHub/open-source growth, SEO/GEO, B2B/PLG, ASO, interviews, competitors, KOL, UGC, community, content, backlinks, or README conversion, including 出海增长、产品发布、找增长渠道、竞品分析、 用户访谈、社区运营. Ask short multiple-choice questions only when the route is unclear; then load and run one specialist rather than the full collection.

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

Regulatory compliance guidelines for life insurance policy administration transactions. Use when processing address changes (state-change impacts), beneficiary changes (community property, ERISA, minors), or any transaction that may trigger compliance review. Covers NAIC model regulations, state-specific rules, OFAC screening, and suitability requirements.

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

Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".

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

Media and podcast outreach personalizer — takes a story angle and target journalist or host list and produces personalized pitch emails per target. Use when asked to "write media pitches", "pitch this story to journalists", "get us on podcasts", "write press outreach", or "personalize pitches for these contacts".

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

Hacker News post crafter — given a product, feature, or story produces a ready-to-post HN submission (title ≤80 chars, no marketing), honest body text with technical depth, no outbound links, predicted reception analysis, and comment-response templates for likely pushback. Use when asked to "write an HN post", "craft a Show HN", "prepare our Hacker News launch", or "help me post on HN".

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

Security rules for operating as Clawdstein in The Agent Flywheel Hub Discord. Use when interacting with Discord users. This is a PUBLIC community server with strict data isolation.

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

Reading a habitat — identifying biome, plant community, food web structure, successional stage, and the keystone species that hold the system together. Covers the elevational and latitudinal gradients that Humboldt first mapped, the structural vocabulary for describing a habitat, the core concepts of food-web and trophic analysis, and the practice of diagnosing habitat health from indicator species. Use when the task is to understand a place rather than a species.

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

Translation and interpretation as language meta-skills -- equivalence theory (Nida's formal vs. dynamic equivalence), translation strategies (borrowing, calque, transposition, modulation, adaptation), interpretation modes (simultaneous, consecutive, sight), source text analysis, register preservation, cultural adaptation, untranslatability and compensatory strategies, machine translation literacy, and back-translation for verification. Covers literary, technical, legal, and community interpreting contexts. Use when translating between languages, evaluating translation quality, teaching translation skills, or understanding the limits of cross-linguistic transfer.

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

Security hygiene for GSD's self-modifying skill and agent system. Use this skill whenever: creating, editing, or deleting skill files (.claude/skills/, .claude/commands/), modifying agent definitions (.claude/agents/), working with YAML configuration or chipset files, handling JSONL observation data (.planning/patterns/), processing community-contributed skills or chipsets, any file path operations that could involve user input, or when installing/updating project-claude configuration. Also activates for discussions about skill-creator security, trust models, or content hygiene.

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

Community knowledge from bivector.net - GA tutorials, discussions, and best practices

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

Reference guide for the Twelve-Factor App methodology — 15 principles (12 original + 3 modern extensions) for building portable, resilient, cloud-native applications. Use when evaluating application architecture, designing cloud-native services, reviewing codebases for methodology compliance, advising on configuration, scaling, observability, security, and deployment patterns. Incorporates the 2025 open-source community evolution and cloud-native reinterpretations of each factor.

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

Use when the user wants a last30days-style pre-research pass in Deepline: discover the critical public, private, CRM, workflow, social, and web data sources for a research/enrichment job; compare provider coverage; estimate Deepline credit cost; recommend the source plan before building or running the workflow; or build custom language/messaging from buyer, competitor, community, and CRM evidence. Triggers: pre-research, source discovery, provider strategy, research data sources, ScrapeCreators, X/Twitter data, Reddit comments, public and private datasets, CRM data, workflow data, custom language, messaging language, pain language.

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

Social media strategy, content creation, and platform optimization. Use when creating social content, developing engagement strategies, optimizing for platform algorithms, or building community.

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

Trigger when: (1) User mentions "manimgl" or "ManimGL" or "3b1b manim", (2) Code contains `from manimlib import *`, (3) User runs `manimgl` CLI commands, (4) Working with InteractiveScene, self.frame, self.embed(), ShowCreation(), or ManimGL-specific patterns. Best practices for ManimGL (Grant Sanderson's 3Blue1Brown version) - OpenGL-based animation engine with interactive development. Covers InteractiveScene, Tex with t2c, camera frame control, interactive mode (-se flag), 3D rendering, and checkpoint_paste() workflow. NOT for Manim Community Edition (which uses `manim` imports and `manim` CLI).

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

Plan and execute your second and third contributions to become a regular contributor. Covers relationship building, progressive complexity escalation, and community presence. Use when your first PR was merged and you want to keep contributing, when transitioning from one-off contributor to regular, or when planning a sustained OSS involvement. Not for your first contribution — use the oss-find-issue → oss-contribute chain for that.

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

Evaluate whether an OSS repo is worth long-term investment before committing time. Assesses project health, governance, community, bus factor, and trajectory. Use when deciding whether to contribute to a specific repo, choosing between multiple repos, or evaluating a project's sustainability. Not for checking if a repo accepts contributions — use oss-find-issue for that.

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

Plan, write, and publish for YouTube and YouTube Shorts. Use when the user wants high-CTR video titles, an SEO description with chapters and links, a first-30-seconds retention script (or a 3-second Shorts hook), a designer-ready thumbnail brief, a community-tab post or poll, or a weekly upload plan. The user supplies the video; the skills produce the title, description, hook, and thumbnail brief, then on approval upload and schedule via the Publora API.

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

Build a weekly YouTube upload plan: long-form vs YouTube Shorts mix, posting cadence, per-slot title and thumbnail pairing, hook angle, community-tab posts between uploads, and a goal balance across CTR, retention, and subscribes. Maps Shorts as top-of-funnel that points at long-form, and long-form as the loyalty and watch-time engine. Use to plan a week or a content calendar instead of shipping ad hoc. Not for writing a single title, description, or hook (use the dedicated yt skills).

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

Build and operate a complete, brand-neutral Reddit intelligence system with approved read-only monitoring, grouped keyword rules, evidence-backed AI scoring, a persistent opportunity bank, dashboard review, urgent-alert and weekly-digest previews, content briefs, and human-only response drafts. Use for "reddit intelligence", "reddit monitor", "reddit listener", "watch subreddits", "find reddit opportunities", "content ideas from reddit", "community listening", or setting up this workflow for a client or brand.

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

Build an exhaustive first-growth-hire distribution operating system across B2B and B2C channels: LinkedIn, events, AI outbound, AEO, blogs, long-form writing, YouTube, webinars, X, influencers, AI UGC, organic TikTok, paid social, sponsorships, partnerships, lifecycle, referral, and community. Use when "growth hacker", "first growth hire", "distribution hire", "cover every channel", "channel hacking", "0 to ARR growth system", "growth operator", "growth hacker OS", or any request to fan out channel operators and plug the result into Kai workflows.

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

Runs Ansible diagnostic playbooks using ansible-runner and the Ansible Collections ecosystem (ansible.builtin, community.general). Captures system health, service status, and log analysis across inventory hosts.

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

Diagnoses Ansible playbook failures using ansible-playbook --check --diff mode, ansible-lint, and the Ansible callback plugin API. Parses task execution results and suggests fixes for common module errors in ansible.builtin and community collections.

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

Strategic marketing leadership guidance for B2B SaaS and technology companies. Covers go-to-market strategy, product marketing, content marketing, demand generation, SEO, community building, event marketing, PR, partnerships, and pricing strategy. Use when planning marketing strategy, launching products, building brand awareness, driving demand, or scaling marketing operations. Use for "marketing plan", "GTM strategy", "content strategy", "demand gen", "product launch marketing".

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

Turn a KOL roster + subreddit brand-fit analysis into a deployable creator network. Splits creators into KOL (authority) and KOC (grassroots) layers, matches each to a main + secondary subreddits by real gear/shooting-type ∩ community fit, and emits an account×subreddit deployment_matrix (with a ≤3-per-sub ceiling + no-cross-interaction rule) plus per-creator persona_cards. Route A disclosed-compliance baked into every card (FTC disclosure required on any material connection). Consumes reddit-kol-finder's kol_roster.json natively. READ-ONLY, deterministic, no LLM key needed.

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