「open channel」の検索結果

Feishuのファイルで共同編集者と共有権限を確認し、依頼に沿って追加・削除するスキル。対象と相手の識別情報を確かめ、必要な範囲の権限を設定します。

• ファイルの共有相手を確認したいとき
• 必要な権限で共同編集者を追加
• 特定の共同編集者のアクセスを削除

Agent-to-agent Slack rooms — a group DM (MPIM) holding a human plus two or more NanoClaw sibling bots, where each bot hears the room over its own Socket Mode connection. Registers the admission policy on the Slack channel's bot-inbound guard so bot-authored inbound is admitted only for rooms allowlisted in SLACK_A2A_ROOMS (re-attributed as slack:bot:<bot_id>, hop-limited via SLACK_A2A_MAX_HOPS), plus scripts/open-a2a-room.ts to open a room and register it.

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

Use only when the user asks to produce a finished multi-scene narrator-led video and explicitly requests a faceless channel, YouTube automation, narrated explainer/story/education, documentary, storybook or myth retelling, or kids song video. Topic alone is never enough: a generic video of/about something, including a historical topic, uses ordinary video generation. Do not use for planning or ideas, single clips, silent animation, image-to-video, footage edits, ads, product demos, or UGC. This workflow requires a consistent non-photoreal style, reusable assets, narrator voiceover, and burned subtitles.

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

Turns one-shot external recon into a continuous monitoring program. Covers the scheduled re-scan-and-diff loop (baseline snapshot -> interval sleep -> re-scan -> asset/finding delta -> threshold-gated webhook alert), the scan-to-scan diff engine (new/removed/changed assets by a tracked-attribute table, new/resolved findings by a stable cross-scan fingerprint), adversary CTI / chatter monitoring across six public feeds (ransomwatch, ransomware.live, HackerNews Algolia search, Reddit security-subreddit RSS, GitHub Gist code-search, public Telegram channel scraping) with a source-kind-aware severity engine (leak-site/forum/telegram/paste tiers, CRITICAL through INFO), literal/glob/regex watchlist pattern matching, full-corpus capture with retroactive rescan on new watchlist entries, infrastructure-tracking-over-time discipline (certificate-transparency, passive-DNS, port/service, and typosquat re-enumeration cadence, and what a genuine 'perimeter drift' event looks like in the diff output), a five-state finding-lifecycle state machine (open/triaged/risk_accepted/resolved/false_positive) with per-severity SLA and fingerprint-based cross-scan dedup and auto-resolve/reopen rules, the alert-fatigue trap where a lifecycle-unaware rule re-fires on an already-accepted finding, a durable retry/backoff alert-outbox pattern ('queued is not delivered'), and copy-paste bash-cron plus PowerShell-Scheduled-Task recipes for a re-scan+diff loop with the Slack-compatible webhook payload shape. Passive OSINT and analysis only -- no new active-intrusion technique. Use when setting up ongoing monitoring for a retainer or MSSP engagement, tuning alert thresholds to avoid fatigue, triaging a finding's lifecycle status, investigating adversary chatter about a brand, building a 'what changed on the perimeter since last week' report, or deciding whether a persisting finding should re-alert.

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

Configure and use EAS Update for over-the-air JavaScript and asset updates with expo-updates and EAS CLI. Use when setting up OTA updates, running eas update:configure or eas update, publishing to preview/staging/production channels, explaining branches/channels/runtime versions, testing updates, or debugging why an installed build still shows old code. Load for TestFlight, preview, or production updates that do not appear, including questions about cold launches or reopening the app. Not for update health metrics; use eas-update-insights for adoption, crashes, and rollout monitoring.

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

Lark/Feishu channel output rules. Always active in Lark conversations.

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

Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video. For a YouTube channel specifically — idea selection, retention teardowns, and channel-level strategy — use `youtube-producer`.

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

Toggle proactive messaging mode. When enabled, Agent proactively sends greetings, task reminders, and key recaps via IM channel. Use when user asks to enable/disable proactive messages.

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

Evaluate emerging channels such as voice or social commerce with pilot plans. "should we open a TikTok Shop"

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

Build and run a full email marketing channel — list building, deliverability, segmentation, newsletter strategy, campaign types, A/B testing, and email design. Use when the user says "email marketing", "email strategy", "email list", "newsletter", "email campaigns", "email list building", "email deliverability", "email open rates", "email segmentation", "email design", "email calendar", "grow my email list", "email marketing plan", "broadcast emails", "email engagement", or wants to use email as a primary owned marketing channel beyond just automated flows.

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

Pull GA4 reports, traffic data, and insights from the Google Analytics Data API. Use when asked about website traffic, user behavior, acquisition channels, conversions, or audience segments. Trigger phrases: "google analytics", "GA4", "traffic report", "analytics data", "user acquisition", "engagement metrics", "conversion tracking", "audience segments", "page views", "sessions".

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

Plan and execute product launches with week-by-week timelines and channel-specific playbooks. Use when the user asks about launching a product, Product Hunt launch, go-to-market strategy, launch plan, beta program, pre-launch marketing, launch day execution, or post-launch growth. Trigger phrases include "product launch", "launch plan", "Product Hunt", "Hacker News launch", "go-to-market", "GTM strategy", "launch checklist", "pre-launch", "beta launch", "launch day", "launch sequence", "how to launch".

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

Send messages, embeds, and marketing content to Discord channels via webhooks or bot API. Manage community engagement, announcements, and automated posting. Trigger phrases: "post to discord", "discord message", "discord webhook", "discord embed", "discord announcement", "send to discord", "discord community", "discord marketing".

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

Send messages and interactive cards to Feishu (飞书) and Lark channels via webhooks or Bot API. Create rich-text announcements, marketing updates, and team notifications. Trigger phrases: "post to feishu", "feishu message", "lark message", "feishu webhook", "lark webhook", "send to feishu", "send to lark", "feishu bot", "lark bot", "飞书", "飞书机器人".

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

Weekdays, browser only when the card needs one. Takes the next ready cards off the launch board and does the work each one names: stages copy into the dashboard, fills a directory or press form and leaves it open in its tab, verifies a setup, packages a handoff, or researches its own next targets. It ticks its own card the moment it has verified the file that closes it. It submits only where you released the channel, sends only where you released the channel, spends only where you released it, and never touches a credential.

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

Runs once by hand on the first day and once a month after that, light browser lane. On the first run it researches the business from its own published surfaces before asking anything, writes the strategy folder, creates the ledgers, seeds the opening cards, builds the single page dashboard, reconciles the schedule table, and registers the eight recurring jobs. On every monthly run it re-reads a month of the kit's own evidence, applies what changed, adds a tab for a channel that gained volume, rebuilds, and reconciles every registered job against the table. It holds every outbound action unless you released the channel, and it never enters a credential.

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

Weekdays, heavy browser lane. Opens the member's own signed in profile, post, and notification surfaces for every platform in the channel plan, confirms that everything published since the last run is genuinely live, reads the counts attached to each post, captures every comment, mention, quote, reply, and inbound message into a queue the member answers by hand, and drafts a suggested reply for each one. Read only everywhere and totally read only on LinkedIn. It sends only where you released the channel, never replies, spends only where you released it, and never touches a credential.

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

Brand-consistent asset sets from DESIGN.md — hero, section illustrations, icon sets, OG image — generated through whichever channel the user actually has (grok build image_gen, Codex $imagegen, Gemini, xAI/Recraft/OpenAI keys) as recorded by omd:setup, with a provenance and cost ledger. No channel → prompt pack + manual queue, never stock. Trigger: '이미지 세트 만들어', '에셋 생성', 'generate assets', 'hero image', '아이콘 세트', 'OG 이미지'.

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

Brand-consistent asset sets from DESIGN.md — hero, section illustrations, icon sets, OG image — generated through whichever channel the user actually has (grok build image_gen, Codex $imagegen, Gemini, xAI/Recraft/OpenAI keys) as recorded by omd:setup, with a provenance and cost ledger. No channel → prompt pack + manual queue, never stock. Trigger: '이미지 세트 만들어', '에셋 생성', 'generate assets', 'hero image', '아이콘 세트', 'OG 이미지'.

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

Use when a researcher, maintainer, or contributor found or suspects a malicious skill on ClawHub and needs a private reporting workflow: opening a GitHub private vulnerability report, preparing a proposal-only PR, creating `proposals/<GHSA-ID>/clawscan.yml`, running ClawScan against the malicious skill, and explaining what evidence belongs in private versus public channels.

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

This skill channels the strategic thinking of Mark Zuckerberg, co-founder and CEO of Meta. Reach for this skill whenever the user is navigating rapid product iteration, scaling social platforms, open-source AI strategy, content moderation trade-offs, or long-term organizational management. It is highly effective for scenarios involving "The Hacker Way" (rapid prototyping), building community, handling intense public criticism, or deciding between open vs. closed ecosystems. Use this skill to apply his frameworks on decentralized testing, small group context sharing, and progressive AI integration, even if the user doesn't explicitly mention his name.

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

Reconstruct an open-source project's growth channels, key content, and stage-by-stage attribution from GitHub history and public web evidence. Use this skill when asked to research GitHub star growth, identify launch and amplification channels, explain viral milestones, find representative posts or videos, compare Product Hunt/Show HN/Reddit/KOL impact, or produce an evidence-backed OSS growth attribution report.

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

OpenStack monitoring operations skill for deploying, configuring, and operating the cloud health monitoring stack. Covers Prometheus metric collection and scrape targets, Grafana dashboard provisioning and visualization, Alertmanager notification channels and routing, alerting rules for service health and resource exhaustion, service endpoint health checks, log aggregation strategies, SLA tracking with availability and response time percentiles, and capacity trend analysis from historical metrics. Use when deploying monitoring via Kolla-Ansible, configuring alert thresholds, troubleshooting blank dashboards, tuning noisy alerts, or analyzing cloud performance trends.

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

Turns a campaign idea, its objectives and the supporting notes (audience material, offer facts, budget and dates, channel list) into one DRAFT one-page campaign brief: objectives, audience, one single-minded message with sourced proof points, channels and timeline, success measures with baselines, mandatories, risks and numbered open questions for the campaign owner. Use when the user asks to "write a campaign brief", "draft a creative brief for this launch", "turn this idea into a one-page brief", "tighten this brief to one page" or "build the marketing brief from these notes". Do not use for a message house, messaging pillars or a launch narrative on its own, use message-house-builder instead; for laying the campaign onto dated slots, use content-calendar-planner. Drafts for human review; never approves, authorises or signs off.

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