「post」の検索結果

Repurpose blog posts for social media, email, video, podcast, and community channels. Generates Twitter/X threads, LinkedIn posts and articles, Threads, Bluesky, TikTok, Instagram, YouTube Shorts and long-form scripts, Reddit, newsletter, podcast, Discord, and Slack variants. Adapts tone for each platform. Use when user says "repurpose", "blog repurpose", "share blog", "social media", "twitter thread", "linkedin post", "youtube script", "reddit post".

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

Use when admins are reducing Chatter signal-to-noise across an org — covers org-level Chatter Email Settings, per-user Email Settings preferences, group-level email digest frequency (Daily / Weekly / Every post / Never), bell-icon Custom Notifications vs Chatter feed-post tradeoffs, automated-feed suppression on record types via Feed Tracking config, and the Chatter Settings org defaults that control whether new users start with everything-on. Triggers: 'chatter feed full of automated posts nobody reads', 'users complain about chatter email volume', 'turn off chatter notifications for a specific group', 'change default chatter digest frequency', 'stop process builder posts from filling the feed', 'NotificationFrequency invalid value', 'ChatterEmailsMD.settings will not deploy', 'custom notification recipient limit'. NOT for Custom Notifications API design (use apex/apex-custom-notifications-from-apex), NOT for Connect API / Chatter REST API integration patterns (use apex/apex-connect-api-chatter), NOT for Chatter group lifecycle, archiving, ownership and unlisted-group governance (use admin/chatter-group-governance).

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

Use when writing, reviewing, or deciding what to post on Threads. Also triggers when planning post-viral strategy or checking posting timing. Runs pre-publish checks based on Meta algorithm patents.

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

Reddit content publishing skill. Submit text posts, link posts, and image posts to subreddits. Triggered when user asks to post, submit, or share content on Reddit.

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

This skill recommends measuring serum sodium several times during the first 5–14 days after transsphenoidal surgery to detect and manage electrolyte disturbances such as postoperative hyponatremia and diabetes insipidus. Use when managing a post-TSS Cushing’s syndrome patient in the early recovery phase; triggers include postoperative day 5–10 hyponatremia, polyuria, fluid intake‑output imbalance, or suspected diabetes insipidus.

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

Interprets the postural stimulation test to detect angiotensin II‑unresponsive aldosterone‑producing adenoma (APA) or familial hyperaldosteronism type I (FH‑I) when aldosterone fails to rise with upright posture. Triggered by clinical cues such as “postural stimulation test shows no aldosterone increase”, “suspected APA with non‑responsive aldosterone”, or “evaluating FH‑I in young patients with early‑onset hypertension and hypokalemia”.

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

Post findings from the most recent review output as inline GitHub PR comments and record them in today's daily note. Use when invoked as `$pr-post-review-findings` or when the user asks to post review findings to the current PR.

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

INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by create-issue, create-issue-from-issue-number, and update-issue. It formats an implementation-ready GitHub Issue body, runs the pre-posting checklist, executes `gh issue create` or `gh issue edit`, and optionally posts a 確認事項 follow-up comment. Invoke this skill ONLY from one of the three parent skills via the Skill tool, after the parent has completed analysis. If a user asks to 'format an issue body' or similar, route them to the appropriate parent skill (/create-issue, /create-issue-from-issue-number, or /update-issue) rather than invoking this one directly.

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

使用 AACT (Aggregate Analysis of ClinicalTrials.gov) PostgreSQL 数据仓库进行批量、历史、聚合性临床试验数据挖掘。Use this skill when the user requests bulk SQL analysis over the full clinical trials data warehouse — historical trial trends, disease landscapes, similar-design matching, or multi-year aggregations across hundreds of thousands of NCT records. 触发场景包括：AACT 查询、临床试验批量分析、PostgreSQL 试验数据、全量 NCT 检索、试验数据挖掘、历史试验分析、clinical trials data warehouse、SQL trials、bulk trial analysis、disease landscape、试验设计相似性匹配、跨年度聚合、sponsor/phase/country 多维统计。**与 clinical-trials-v2 差异**：本 skill 走批量 SQL · 离线大数据（PostgreSQL）；v2 走实时 API · 单查询。两者互补：单条 NCT 实时状态用 v2，百万级历史挖掘用本 skill。支持云端公共 PostgreSQL（aact-db.ctti-clinicaltrials.org · 零部署）和每日 dump 本地还原（高性能 · 离线）两种连接方式，自动检测优先用本地。跨平台（macOS/Linux/Windows）参数化 SQL 防注入，read-only 强制保护。

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

At the close of an epic (or a difficult issue), post a postmortem roundup comment — what went well, what was hard (backed by evidence), and 1–3 concrete proposals to improve the skills/flows — then offer to turn accepted proposals into their own `workflow`-labeled tasks, and end with a `🔭 Next` handoff (a paste-ready next-session prompt + the next epic to start). Use at epic close, after the "verify the whole thing" rollup, or when asked to "do a retro", "postmortem this epic", "what did we learn", "how do we improve the workflow".

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

システムログを分析してエラーの根本原因を特定し、段階的に深堀りしていくデバッグ専門家スキル。 アプリケーションログ、システムログ、クラウドサービスログなど様々な形式に対応。 5 Whys、タイムライン分析、Fishbone分析などのRCA（根本原因分析）手法を用いて 問題の本質を突き止め、再発防止策まで提案する。 Use when analyzing system logs to find error root causes, debugging application issues, or performing technical post-mortem analysis with log data. For organizational incident management processes (post-incident review, corrective action plans, incident reports without log data), use incident-rca-specialist instead. Triggers: "analyze this log", "find the root cause", "debug this error", "why is this failing", "log analysis", "what caused this crash", "troubleshoot this issue"

M&Aアドバイザリー支援スキル。デューデリジェンス（DD）実施、企業価値評価（バリュエーション）、 シナジー分析、PMI（Post Merger Integration）計画策定を包括的に支援。 Use when conducting M&A due diligence (Financial, Legal, IT, HR), company valuation (DCF, Comparable Companies, Precedent Transactions), synergy analysis, or post-merger integration planning. Triggers: "M&A", "デューデリジェンス", "DD", "バリュエーション", "企業価値評価", "DCF", "comparable", "類似企業", "先行取引", "PMI", "統合計画", "シナジー分析", "買収", "合併"

インシデント発生後の振り返りと根本原因分析を体系的に実施するスキル。 ログファイル解析や技術デバッグが必要な場合は log-debugger を使用すること。 本スキルはインシデント管理プロセス（タイムライン構築、影響評価、 是正措置計画、再発防止策）に特化する。ログデータの分析ではなく、 組織的な振り返りプロセスと是正措置の策定が主目的である。 Use when conducting post-incident reviews without log analysis, creating corrective action plans, or performing organizational root cause analysis focused on process improvement. NOT for log file debugging. Triggers: "post-incident review", "corrective action plan", "incident report作成", "再発防止策", "RCAレポート", "是正措置", "インシデント振り返り"

Drafts a blameless incident postmortem (summary, impact, timeline, detection and response, contributing factors as candidates for review, action items) from an incident channel export, ticket notes and any alert or change records, with UNKNOWN for every fact the inputs do not contain. Never assigns blame, names a root cause or re-rates severity. Use when the user asks to "write the postmortem for this incident", "build the incident timeline from the chat export", "draft the post-incident review" or "turn this ticket and channel log into an incident report". Do not use for a knowledge article from the resolved ticket, use knowledge-article-drafter instead; for project retrospectives, use lessons-learned-synthesis; for data-breach impact and notification questions, use data-incident-impact-brief. Drafts for human review; never approves, authorises or signs off.

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

Query PostHog product analytics via REST API — event analytics, HogQL SQL queries, feature flags, experiments, session recordings, insights, persons, cohorts. Use when the user wants to answer an analytics question, toggle/inspect a flag, or pull event data programmatically without opening the PostHog UI or installing the PostHog MCP.

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

Publish a vetted post to an X (Twitter) account through the owner's real logged-in Chrome tab, rate-guarded and draft-first. Counts length the way X does, treating every link as 23 characters, and refuses over-limit text instead of silently truncating. Triggers: "/x-post", "tweet this", "post to X".

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

Publish a vetted post to one of your own Telegram channels or supergroups over the MCP connector rather than a browser, with the channel resolved strictly by id from a registry, rate-guarded and draft-first. It never posts to a chat matched by name similarity. Triggers: "/tg-post", "publish to the telegram channel".

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

Publish an already-vetted post to a personal Facebook wall through the owner's real logged-in Chrome tab (a low-ban-risk path), rate-limit-guarded and draft-first: paste, verify what is actually in the composer, confirm after reload. Triggers: "/fb-post", "publish to facebook", "post this to my wall".

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

Produces structured content calendars with platform-specific posting schedules, content pillars, and batch publishing plans. Use when the task asks to "plan content", "schedule posts", "create a content calendar", "editorial calendar", "posting schedule", or "content strategy". Covers content pillars, posting cadence, multi-site calendars, seasonal hooks, and content repurposing matrices.

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

Publish and schedule content to social media platforms (Twitter/X, Facebook, Instagram, LinkedIn) via the MCP bridge schedule_social_post tool as primary. The Design Stack media worker API is the fallback for advanced platform management. Covers platform-specific formatting, media attachment, scheduling, and WordPress-to-social publishing workflows. Use when posting to social platforms, scheduling future posts, attaching media to posts, checking optimal timing, or debugging API delivery failures.

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

Assesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203/204/205 standards. Performs cryptographic inventory scanning to identify quantum-vulnerable algorithms (RSA, ECDH, ECDSA), evaluates hybrid TLS configurations with X25519MLKEM768, and validates CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium (ML-DSA) readiness. Implements crypto-agility assessment using oqs-provider for OpenSSL. Use planning yaparken or executing the transition from classical to post-quantu...

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

Read, answer and post on the Sandock community forum at community.sandock.ai through its /api/v1/community REST API. Lists categories and posts, reads a thread with its replies, searches, and publishes posts and replies behind an explicit confirmation. Use when the user invokes $sandock-community or /sandock-community, asks what is happening in the Sandock community, wants an unanswered question triaged or answered, or wants something posted or announced there.

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

Read, answer and post on the Buda community forum at community.buda.im through its /api/v1/community REST API. Lists categories and posts, reads a thread with its replies, searches, and publishes posts and replies behind an explicit confirmation. Use when the user invokes $buda-community or /buda-community, asks what is happening in the Buda community, wants an unanswered question triaged or answered, or wants something posted or announced there.

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

Read, answer and post on the Busabase community forum at community.busabase.com through its /api/v1/community REST API. Lists categories and posts, reads a thread with its replies, searches, and publishes posts and replies behind an explicit confirmation. Use when the user invokes $busabase-community or /busabase-community, asks what is happening in the Busabase community, wants an unanswered question triaged or answered, or wants something posted or announced there.

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