「channel」の検索結果

Image segmentation is the process of identifying the borders of individual objects (in this case cells) within an image. This allows for the features of cells such as marker expression and morphology to be extracted, stored and analysed. simpleSeg provides functionality for user friendly, watershed based segmentation on multiplexed cellular images in R based on the intensity of user specified protein marker channels. simpleSeg can also be used for the normalization of single cell data obtained f

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

Expert knowledge for Azure Health Bot development including best practices, security, configuration, and integrations & coding patterns. Use when wiring Teams/SMS/WhatsApp channels, embedding web chat, calling external APIs, configuring handoff, or enforcing consent, and other Azure Health Bot related development tasks. Not for Azure AI Bot Service (use azure-bot-service), Azure Communication Services (use azure-communication-services), Azure Functions (use azure-functions).

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

Expert knowledge for Azure AI Bot Service development including troubleshooting, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Direct Line 3.0, configuring Teams/Web Chat channels, setting App Service bots, CI/CD, or App Insights, and other Azure AI Bot Service related development tasks. Not for Azure Health Bot (use azure-health-bot), Azure Functions (use azure-functions), Azure App Service (use azure-app-service).

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

Escalate blocked runs to a human via configured channel or fallback to BLOCKED.md and exit the loop. Use when the loop hits an ambiguous spec, a missing credential, a destructive action needing approval, or 3+ consecutive verify failures on the same task.

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

Applies the SUCCESs Framework from Made to Stick by Chip Heath and Dan Heath. Use when crafting messages that need to be remembered, writing pitches, creating presentations, designing training materials, telling stories that drive action, or diagnosing why a message isn't landing. The six principles (Simple, Unexpected, Concrete, Credible, Emotional, Stories) diagnose and fix communication failures. Triggers include 'how do I make this memorable', 'my pitch isn't landing', 'people forget what we told them', 'how do I tell a better story', 'our training materials are boring', 'how do I present data compellingly', 'nobody remembers our message', 'how do I get people to care about this', 'my writing is too abstract'. NOT for channel selection (use Traction), not for brand messaging structure (use StoryBrand), not for positioning (use Obviously Awesome).

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

Builds lead generation systems using Alex Hormozi's Core Four framework (warm outreach, content, cold outreach, paid ads), lead magnets, and Rule of 100. Use when designing customer acquisition, scaling advertising, choosing marketing channels for revenue stage, building referral programs, or fixing low lead flow. Covers lead magnets, LTGP:CAC math, More Better New scaling, and Lead Getters (referrals, employees, agencies, affiliates).

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

Applies the StoryBrand SB7 Framework from Building a StoryBrand by Donald Miller. Use when writing website copy, crafting brand messaging, creating marketing materials, building sales funnels, or designing email campaigns. The SB7 Framework positions the customer as the hero and the brand as the guide across 7 story elements. Triggers include 'how should we write our website', 'our messaging is confusing', 'customers don't understand what we do', 'how do I write a tagline', 'what should our homepage say', 'nobody reads our emails', 'how do I create a lead generator', 'our marketing isn't working but our product is good'. NOT for growth channel selection (use Traction), not for product positioning against competitors (use Obviously Awesome), not for pricing (use Monetizing Innovation).

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

Build a brand's messaging hierarchy — taglines, value propositions, key messages, and proof points for each audience. Use when the user says "brand messaging", "messaging framework", "value proposition", "tagline", "brand tagline", "key messages", "messaging hierarchy", "what should we say about our brand", "brand copy foundation", "messaging architecture", "elevator pitch", "one-liner", "brand statement", or needs consistent language across all communications. Also use when messaging feels inconsistent across channels or teams.

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

Build a WhatsApp marketing strategy — WhatsApp Business setup, broadcast campaigns, automated flows, customer service, drip sequences, and conversational marketing. Use when the user says "WhatsApp marketing", "WhatsApp Business", "WhatsApp campaigns", "WhatsApp broadcasts", "WhatsApp automation", "WhatsApp drip", "market on WhatsApp", "WhatsApp for business", "WhatsApp chatbot", "WhatsApp customer service", "WhatsApp API", "messaging marketing India", or wants to use WhatsApp as a marketing and customer communication channel. Especially relevant for brands in India, the Middle East, Southeast Asia, Brazil, and Africa.

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

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", "飞书", "飞书机器人".

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

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".

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

Repurpose one piece of affiliate content into multiple formats. Triggers on: "repurpose my content", "turn my blog into tweets", "cross-post this", "content recycling", "convert to newsletter", "make a tweet thread from this", "adapt for TikTok", "omnichannel content", "scale my content", "turn this into a LinkedIn post", "repurpose for email", "content multiplication".

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

Download or open videos and recover platform captions, audio transcripts, keyframes, screen text, visual facts, and editing observations as a plain multimodal_transcript.md. Use for Douyin, Bilibili, YouTube, Xiaohongshu, experimental WeChat Channels links, or local video files when preparing complete source material for analysis or downstream Skill distillation.

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

Weekdays, heavy browser lane. Captures the dated raw material tomorrow's drafts are built from, out of the member's own shipped work, their own site and changelog, their own signed in saved searches, and the places their audience already is. Every line carries a source URL read this run, a date, a verbatim quote, and an expiry. It invents nothing, it is read only everywhere and totally read only on LinkedIn, and it sends only where you released the channel, spends only where you released it, and never touches a credential.

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

Weekly, on a Friday, read only everywhere. Scores the week from the kit's own ledgers with a source path beside every number, cuts it by platform, framework, pillar, slot time, and post length, rewrites the drafting standards from that evidence and from nothing else, replays the browser flows the other routines depend on, and files exactly one thing to stop and one to do more of. It publishes only where you released the channel, never replies, spends only where you released it, never touches a credential, and never writes a number it did not measure.

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

Weekdays, file work only, no browser at all. Reads every run record since it last ran, folds the published, draft, indexing, and rank ledgers, folds the card inbox into the work board, marks the single card the draft run works today, and writes the short morning brief the member opens first. It holds publishing and spending unless you released the channel, and it never touches a credential.

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

Weekdays, file work only, no browser at all. Walks every AI Employee installed on this machine, reads each one's own run log strictly read only, classifies every routine as running, stopped loudly, stopped silently, or paused, ages the faults, folds the decision register, and writes the one short brief the member opens first. It never writes into another Employee's folder, sends only where you released the channel, spends only where you released it, and never touches a credential.

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

Weekly, heavy browser lane, read only toward the world with no exception. Works the surfaces on its own watchlist through one contiguous browser phase, captures one dated observation per real change with a verbatim quote and the exact URL, refuses to report any change against a surface it has no baseline for, and writes one capped weekly page. It types nothing that changes anything, takes no action on LinkedIn ever, sends only where you released the channel, spends only where you released it, and never touches a credential.

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

Weekly, conditional browser lane, read only everywhere. Scores the fleet and the business for the week with a source beside every single number and no number anywhere without one, cites the Employee that owns a metric rather than recomputing it, refuses a rate below the floor, and writes one capped weekly page. It opens a browser only where the metric map names a live screen, never writes into another Employee's folder, sends only where you released the channel, spends only where you released it, and never touches a credential.

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

Weekdays, browser only where a link genuinely needs verifying. Writes tomorrow's slots, one draft per due slot per destination, from the voice file, the drafting standards, and the dated material captured this morning. It rotates the post framework so no skeleton repeats, enforces the plain text and character budget rules the platforms actually impose, and judges every candidate before it lands. It publishes only where you released the channel, never schedules, never replies, spends only where you released it, and never touches a credential.

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

Weekdays, file work only, no browser at all. Takes the single highest ranked open fault on the fleet and turns it into something the member can act on in a minute: the fault in one sentence, the first record that shows it, what changed around that date, three ranked causes each with its evidence line, what the failure has cost, and one paste ready correction line with the exact path it belongs in. It reads other Employees strictly read only, writes nothing outside its own folder, sends only where you released the channel, spends only where you released it, and never touches a credential.

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

Monthly, on the last weekday, file work only, no browser at all. Folds the decision ledger, scores this Employee's own judgement against the metric files that measured it rather than against its own predictions, appends one outcome line per closed decision, retires a move proposed three times and never accepted, and rewrites the priorities where the evidence disagrees with them. It refuses to publish a calibration figure on too few closed decisions, changes nothing outside its own folder, proposes nothing to anybody, sends only where you released the channel, spends only where you released it, and never touches a credential.

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