「ost」の検索結果

End-to-end social content campaign pipeline. Takes a marketing goal and produces scheduled, on-brand social posts with visuals across postiz-supported platforms, while keeping Typefully for X/thread specialist flows and fallback coverage. Chains: CMO strategy, content writing with voice calibration, AI slop audit, selective Paper MCP visual design, and routed scheduling via postiz or Typefully. Each phase has a human gate. Use this skill whenever someone wants to plan and execute a batch of social posts — not just one-off tweets. Triggers include: "social campaign", "schedule posts", "pre-launch content", "content calendar", "social content pipeline", "build up content", "I need social media content for my launch", "help me build social presence", "plan a week of posts", "batch social content", "social media strategy", or any request involving multiple scheduled posts with optional visuals.

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

Plan a monthly content calendar across channels using the Content Marketing Matrix (Dave Chaffey, Smart Insights) - Entertain/Inspire/Educate/Convince. Every post gets a quadrant label. The monthly calendar must hit 40% Educate, 40% Inspire+Convince, 20% Entertain. Produces a week-by-week posting schedule with topics, formats, channels, and asset links. Use when the user says "content calendar", "social calendar", "plan next month's content", "what should we post", "content plan", "editorial calendar", "schedule posts for the month", or wants a structured posting plan for LinkedIn, Twitter, email, or blog. Reads brand voice, ICP, and past learnings from knowledge/. For writing the individual posts, see linkedin-post, newsletter-writer or content-writer. For the campaign this sits inside, see campaign-brief. For the end-of-month review, see retro.

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

Automating post-sandbox-refresh cleanup via the `SandboxPostCopy` interface — the Apex class that runs ONCE after a sandbox refresh or clone completes, before users can log in. Used to mask emails, deactivate users, scrub integration endpoints, disable scheduled jobs, and reapply per-environment configuration the metadata copy doesn't carry. Covers the interface contract (`runApexClass` setting, `SandboxContext` parameter, single-execution semantics), the email-masking pattern that stops sandbox tests emailing production addresses, and the refresh runbook checklist. NOT for choosing sandbox type or refresh cadence — use admin/sandbox-strategy. NOT for re-seeding reference data after a refresh — use data/sandbox-refresh-data-strategies. Trigger keywords: SandboxPostCopy, runApexClass, SandboxContext, Test.testSandboxPostCopyScript, RunAsAutoProcUser, Automated Process user, CronTrigger, System.abortJob, sandbox email masking, post-refresh runbook.

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

Warehouse cost reduction, auto-scaling, query optimization, and lifecycle policies for data infrastructure. Activate on: data cost, warehouse credits, cost reduction, auto-scaling, lifecycle policy, cold storage, cost monitoring, resource optimization. NOT for: query performance tuning (use data-warehouse-optimizer), batch job optimization (use batch-processing-optimizer).

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

Track real-time API cost accrual during LLM execution. Activate on 'cost tracking', 'token usage', 'API costs', 'budget monitoring', 'usage metrics'. NOT for cost estimation, pricing tiers, or billing systems.

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

Audit LLM token cost estimates against actual API usage. Activate on 'cost verification', 'token estimate accuracy', 'API cost audit', 'estimation variance'. NOT for pricing lookups, budget planning, or cost optimization strategies.

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

Use when the user wants a ready-to-paste social post kit for an app, tool, or project launch or update — "make social posts", "launch posts", "post kit", "prep socials", "promote this". Produces one Markdown file with finished posts for X, Reddit, Instagram, LinkedIn, Threads, and short-form video, plus a pre-post checklist. Pull real facts from the project (repo, release, what it does, OS, links).

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

Knowledge base from the GAO Cost Estimating and Assessment Guide (GAO-20-195G). Use for program cost estimating: the four characteristics of a reliable estimate (comprehensive, well documented, accurate, credible) and the 18 best practices; the 12-step cost estimating process (purpose, plan, technical baseline, WBS, ground rules and assumptions, data, point estimate, sensitivity, risk/uncertainty, document, present, update); estimating methods (analogy, parametric, engineering build-up, learning curves); Monte Carlo risk/uncertainty analysis, confidence levels and contingency; auditing and validating an estimate against the characteristics; earned value management (EIA-748, BCWS/BCWP/ACWP, CPI/SPI/TCPI, EAC, PMB, IBR); and specialized techniques (software cost estimating, learning curves, Analysis of Alternatives, WBS templates, the Green Book internal-control framework). This is the cost-estimating companion to the GAO Schedule and Technology Readiness Assessment guides. Does not cover schedule estimating/risk in depth (see the GAO Schedule Assessment Guide), agency-specific cost models, or the full text of referenced standards (EIA-748, MIL-STD-881D, the Green Book) — these are named, not reproduced.

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

Create a new PostgreSQL CDC capture from scratch using flowctl. Covers all Postgres variants (vanilla, Aurora, RDS, Cloud SQL, Supabase, Neon). Use when user says "capture Postgres", "stream from Postgres", "Postgres CDC", "set up replication slot", or "connect Postgres to Estuary".

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

Use when working with Aws Cost Optimization — aWS native cost optimization using Compute Optimizer, Trusted Advisor cost checks, Savings Plan analysis, Cost Explorer, and resource rightsizing. Covers EC2 rightsizing, idle resource detection, Savings Plan and Reserved Instance recommendations, and cost anomaly detection. Use when optimizing AWS infrastructure costs with native AWS tools.

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

Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.

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

Cost modeling and ROI analysis for specialized LLM development. Use when deciding whether to train a custom model, estimating total cost, or calculating break-even vs frontier APIs. Covers training costs, inference costs, and time-to-ROI projections.

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

Quality gates determinísticos para PostgreSQL. Use quando o usuário pedir "quality gate PostgreSQL", "quality gate Postgres", migrations ou schema drift PostgreSQL, constraints ou índices PostgreSQL, EXPLAIN, plano de consulta ou baseline para PostgreSQL.

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

Locate BotProfile::Cost in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "BotProfile::Cost" (symbol BotProfile_Cost). This is a VIRTUAL function - resolve the BotProfile::Cost vtable via RTTI and identify the slot, then emit the slot. Verify by xrefs from expected call sites. vtable slots commonly differ between platforms - never assume identical indices. Trigger: BotProfile_Cost, BotProfile::Cost

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

Warehouse cost reduction, auto-scaling, query optimization, and lifecycle policies for data infrastructure. Activate on: data cost, warehouse credits, cost reduction, auto-scaling, lifecycle policy, cold storage, cost monitoring, resource optimization. NOT for: query performance tuning (use data-warehouse-optimizer), batch job optimization (use batch-processing-optimizer).

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

Audit LLM token cost estimates against actual API usage. Activate on 'cost verification', 'token estimate accuracy', 'API cost audit', 'estimation variance'. NOT for pricing lookups, budget planning, or cost optimization strategies.

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

Track real-time API cost accrual during LLM execution. Activate on 'cost tracking', 'token usage', 'API costs', 'budget monitoring', 'usage metrics'. NOT for cost estimation, pricing tiers, or billing systems.

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

Discordのデスクトップアプリで、ログイン済みの本人アカウントから承認済みの告知などを投稿し、送信先・本文の確認から投稿結果の確認まで進めるスキル。

• 本人アカウントでリリース告知を投稿したいとき
• 指定チャンネルに承認済みの文面を送りたいとき
• 投稿前に送信先と本文を確認したいとき

CodexBarのローカル費用ログから、CodexやClaudeの利用費用をモデル別に集計し、直近の代表モデルや全モデルの内訳をテキスト・JSONで確認するスキル。

• 直近の代表モデルの費用確認
• 全モデルの利用費用を比較したいとき
• 書き出した費用ログの集計

複数のSNSへの投稿をSocialClawで予約・公開し、配信状況を確認します。画像などのアップロードや、複数媒体にまたがるキャンペーンの投稿予定の検証も扱います。

• 複数SNSのキャンペーン投稿予約
• 投稿用の画像などのアップロード
• 公開前に投稿予定を検証したいとき

Creates research posters in LaTeX using beamerposter, tikzposter, or baposter. Use for conference posters, academic presentations, multi-column scientific layouts, figure integration, typography, compilation, and PDF preflight.

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

Exploits privileged pods, host mounts, runC CVEs, and exposed Docker sockets to break out of a container and reach the underlying host during an authorized container-security assessment. Use when executing an approved breakout test, demonstrating the real impact of a privileged or hostPath workload, or validating that escape mitigations actually hold. Keywords: container breakout, privileged, hostPath, docker.sock, runC CVE-2019-5736, CVE-2024-21626, release_agent, nsenter. Do not use for defensive detection of these techniques - use detecting-container-escape-attempts.

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

Detect which gbrain engine is in use (PGLite vs Postgres), prefer Postgres for agent-harness installs, install/provision Postgres (Supabase discovery via SUPABASE_ACCESS_TOKEN, local Postgres, opt-in Docker), and move an existing PGLite brain to Postgres with its history (plan, ask, run). Detection is one engine-free command; the install ladder is one flag.

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

Beta desktop control through the connected A0 CLI host. Use for the user's host/local computer screenshots, screen inspection, menus, native app UI, OS-level clicking, scrolling, typing, or checking computer_use_remote status. Use instead of linux-desktop for host/local machine control. Do not use for ordinary browser navigation; host browser requests should use the browser tool.

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