「publish」の検索結果

[Internal] claude-code-plugin リポジトリの marketplace 構造を検証し、 エラーを自動修正するスキル。CI バリデーション (validate-marketplace.sh) と 同等のチェックをローカルで実行し、missing plugin.json、未登録スキル、 frontmatter 不備、不正キーなどを検出・修正する。 Use when: marketplace を検証したい、CI が失敗した、バリデーションしたい、 プラグイン構造をチェックしたい、plugin.json がない、publish 後の確認。 Triggers: "validate", "バリデーション", "検証", "CI失敗", "CI fix", "marketplace check", "構造チェック", "plugin.json missing", "CI エラー"

Use when asked to publish the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch; when the request excludes the default branch, use commit-push-current.

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

Publish one prepared Agent evidence packet as an additive Issue comment, including historical or closed Issues, under exact current authorization. Use after read-only Issue inspection and separately authorized evidence preparation. Do not reproduce, select work, upload assets, edit human text, claim, review, close, or change Issue metadata.

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

Grafema release procedure for publishing new versions to npm. Covers happy path, pitfalls, rfdb binary lifecycle, and rollback. Use when user says "release", "publish", "bump version".

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

Cut a versioned LoreWeave release — draft the CHANGELOG.md entry from what shipped since the last tag, confirm the SemVer bump and pre-release/release decision with the user, then tag and push to trigger the automated build + GitHub Release. Use when the user says "cut a release", "publish v...", "ship v0.1.0", "make a release", or asks what's changed since the last version.

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

Detect and fix AI-generated writing patterns (slop). Comprehensive detection with 50+ patterns across 3 severity tiers, structure weighted above lexical tells, scoring system, and editor mode that directly fixes problems. Use when scanning any content for AI tells, auditing drafts before publishing, checking if writing "sounds like AI", humanizing AI-generated text, or verifying content authenticity. Trigger on "check for slop", "does this sound like AI", "humanize this", "AI audit", "slop check", "clean up AI writing", or any request to detect/remove artificial-sounding patterns. Also use proactively before publishing any AI-assisted content.

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

Publish NowStack Mobile production surfaces. Use for Convex prod, web deploy, production env sync, and coordinating iOS/Android release skills.

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

Drive the terum-skills CLI from a Claude Code or Codex session: run any verb with --format md and show its board — inspect the Library or the team Marketplace, search, fetch with sync, validate or fix a local skill, install the latest version into Global or an added project, publish a local skill as an immutable version, manage the eval queue — and prepare the verbs that belong in a terminal (project setup, skill move/copy/rename/delete, prune, reconcile, machine uninstall, team administration). Use when the user wants to manage, evaluate, publish or install skills and no narrower terum-skills skill fits.

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

Use this skill when the user needs official desktop Obsidian CLI Sync workflows and, when detected as available, Publish workflows. This skill is for remote-side-effect operations and must use explicit intent, capability probing, and conservative safety checks.

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

Use when streaming durable workflow updates to a UI in real time — live order status pages that animate as steps complete, AI agent token streaming from a function to the browser, log tailing for long-running jobs, or human-in-the-loop approval flows that publish a prompt and wait for a user reply. Covers Inngest v4 native realtime: defining typed channels, publishing from inside step.run, minting subscription tokens via server actions, and consuming the stream from React/Next.js client components.

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

Synchronize curated Agent Skills across approved repositories with policy checks and verification. Use when publishing or updating managed skills, validating a repository mirror, or selecting a safe sync scope. Triggers on "sync public skills", "publish skills", "public 公開", "skill sync", "repository mirror".

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

Mosaic environment-sensitive areas (tenant name, user avatar, subscription name / ID, resource group, internal hostnames) on Azure Portal screenshots before publishing to blogs, Qiita, Medium, slides, or demos. Use when sanitizing screenshots, masking env info, or preparing portal captures for public sharing. Keywords: Azure Portal, screenshot, mask, mosaic, sanitize, tenant, subscription, public publishing, blur, redact.

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

Operate a logged-in Miaoshou ERP workflow for TikTok Shop Malaysia product discovery, product screening, profit estimation, listing preparation, and reviewed publishing. Use when the user asks to search or select products in 妙手 ERP, evaluate low-price traffic products, prepare Malaysian TikTok Shop listings, move products into the TikTok collection box, or publish approved listings. Prefer browser operation through the user's existing login; never store credentials or call undocumented private endpoints.

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

Prepare logical commits, publish through Pharos’s protected-main pull-request gate, monitor deployment, and hand off operational acceptance. Use only when commit, push, publish, release, or deployment watching is requested.

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

Publish finished creatives as live Meta (Facebook/Instagram) ads via the Meta Marketing API, plus research and ad-copy support. Uploads an image or video, builds a multi-variant creative (5 bodies / 5 titles / 3 descriptions in an asset feed), and creates a PAUSED ad in an existing ad set. Also pulls top-performing ads (ranked by ROAS) and competitor ads from the Ad Library to inform copy. Use when the user asks to deploy / publish / launch a creative as a Meta or Facebook ad, build a Meta ad, push a video or image into an ad set, pull their top ads, or research competitor ads. Not for generating creative (use the image/video skills) and not for writing ad-table rows.

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

Publish crates to crates.io with pre-flight checks

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

Use when a task needs the judgment of a Desktop Publisher — laying out a multi-page document on a grid system, applying typesetting rules (kerning, leading, widow/orphan control), preflighting a file for print (bleed, color mode, image resolution) before it goes to press, or deciding between a template and a custom layout under a deadline.

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

Use when a task needs the judgment of a book publisher — sizing an advance against a P&L model before an acquisition auction, setting a print run from comp-title sales data, deciding whether to keep bidding or walk in a multi-house auction, valuing subsidiary rights as part of a deal, or diagnosing why a title's early sell-through is diverging from its launch plan.

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

Scaffold or migrate a repository onto release-please. Generates release-please-config.json, .release-please-manifest.json, and a release-please.yml workflow, plus an opt-in menu of tag-keyed deploy/publish templates (Docker/ECR matrix, frontend host deploy, npm OIDC publish, GitHub Release asset, Fly.io deploy, generic). Supports monorepo (mutual exclude-paths matrix), single-package, and mixed-language (node/simple/python) repos. Use when user runs /release-please-setup, mentions "release please", "set up release please", "automate releases", "conventional-commit releases", "monorepo release automation", or "migrate to release-please".

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

Pre-publish (or retroactive) content-quality gate implementing Google's official self-assessment questions from the creating-helpful-content doc, plus 2024 spam-policy red flags. Verdict: PUBLISH / REVISE / RETHINK. Use when user says "helpful content", "people-first", "content self-assessment", "is my content helpful", or "content quality gate".

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

Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.

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

Publish a reusable native Muse Idea with idea.share when the user explicitly asks to share or publish an Idea or asks for a muse.ai/ideas link. Never offer it unprompted. Not for pages or write-ups, sending a result to someone, social posts, or sharing an artifact.

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

Use when the user provides a Facebook URL or asks to read personal posts, comments, reactions, friends, timelines, profiles, stories, feeds, groups, events, or saved items, or to publish personal text posts, comments, and replies, or to discover public events happening near a place, nearby, or in a local area on a date, or to create, edit, publish, or delete their own Marketplace listings. To find, browse, or buy Marketplace listings, use shopping instead. Use pages commands for managed Facebook Page discovery, insights, native draft editing/deletion, same-draft publication, approved posts and native scheduling.

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

Configure the complete Google Play Store publishing pipeline — upload key generation, AAB bundle optimization, Fastlane supply lanes for internal/beta/production tracks, staged rollout strategy, store listing metadata, data safety form guidance, and content rating preparation

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