「bli」の検索結果

Publish HTML frontend projects to the PushWebly publishing platform, list published projects, obtain shareable project URLs, change a published app's public/private visibility, and package published HTML projects into Android APKs. Use when Codex needs to publish a local zip project, publish and build an APK, build an APK for an existing published project, toggle an app between public and private, list a user's published projects, or log in/register for this publishing platform. Codex should use HTTP APIs with curl when remote MCP tools are not mounted.

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

Publish HTML frontend projects to the PushWebly publishing platform, list published projects, obtain shareable project URLs, change a published app's public/private visibility, and package published HTML projects into Android APKs. Use when Codex needs to publish a local zip project, publish and build an APK, build an APK for an existing published project, toggle an app between public and private, list a user's published projects, or log in/register for this publishing platform. Codex should use HTTP APIs with curl when remote MCP tools are not mounted.

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

Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release synthesis. Runs ONLY when the user explicitly asks for a pre-publish review — a plain publish/release request MUST NOT trigger this; /publish ships directly. Triggers: 'pre-publish review', 'review before publish', 'release review', 'pre-release review', 'ready to publish?', 'can I publish?', 'pre-publish', 'safe to publish', 'publishing review', 'pre-publish check'.

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

推特中文圈 AI 自媒体博主 (推特(X) 中文圈 AI 自媒体博主 (从业者视角) — 在 X/推特 用中文做 AI 内容的自媒体博主，重点是**怎么写推文/thread、怎么制作内容**。覆盖: (a) 选题 — AI 模型发布解读 / prompt 技巧 / AI 工具实测 / AI 出海与独立开发(build in public) / 英文一手编译翻译 / 信息差 / AI 资讯快讯 / 深度长推; (b) 文案与内容结构(核心) — 单条推(开头钩子/信息密度/短句断行/配图截图/数据图)、长推与 thread(首条钩子/编号/逻辑链/结尾关注 CTA)、引用锐评(quote tweet)、排版可读性、配图(ray.so/carbon 代码图/产品截图/对比图); (c) 内容制作工作流 — 找信息源(英文一手/arXiv/官方/Reddit/HN)→选题→编译总结加洞察→写推/thread→配图→发布→互动维护; (d) AI 工具用于内容生产 — 英文一手编译总结(GPT/Claude/Kimi)、配图(ray.so/carbon/截图美化)、thread 工具(Typefully/Hypefury)、翻译、排程分析; (e) 平台机制与涨粉 — X 算法时间线(转评赞/互动权重/外链降权)、蹭热点借势、互动与回复、build in public 涨粉、英文区搬运到中文区的信息差红利; (f) 变现(次要) — 广告 / 知识星球 / 社群 / 付费课程 / 咨询 / 导流。学派分歧: 编译搬运(英文一手翻译) vs 原创洞察、快讯资讯 vs 深度长推、锐评玩梗 vs 严肃干货、build in public vs 纯内容、全 AI 自动发 vs 人工精选。代表生态(宝玉/歸藏/向阳乔木/AI 进化论/小互/Gorden Sun 等)。不含: 英文 AI Twitter 圈(聚焦中文圈)、通用 X 增长营销、其他平台、AI 工具技术原理。) Master OS — automated mastery of 推特(X) 中文圈 AI 自媒体博主 (从业者视角) — 在 X/推特 用中文做 AI 内容的自媒体博主，重点是**怎么写推文/thread、怎么制作内容**。覆盖: (a) 选题 — AI 模型发布解读 / prompt 技巧 / AI 工具实测 / AI 出海与独立开发(build in public) / 英文一手编译翻译 / 信息差 / AI 资讯快讯 / 深度长推; (b) 文案与内容结构(核心) — 单条推(开头钩子/信息密度/短句断行/配图截图/数据图)、长推与 thread(首条钩子/编号/逻辑链/结尾关注 CTA)、引用锐评(quote tweet)、排版可读性、配图(ray.so/carbon 代码图/产品截图/对比图); (c) 内容制作工作流 — 找信息源(英文一手/arXiv/官方/Reddit/HN)→选题→编译总结加洞察→写推/thread→配图→发布→互动维护; (d) AI 工具用于内容生产 — 英文一手编译总结(GPT/Claude/Kimi)、配图(ray.so/carbon/截图美化)、thread 工具(Typefully/Hypefury)、翻译、排程分析; (e) 平台机制与涨粉 — X 算法时间线(转评赞/互动权重/外链降权)、蹭热点借势、互动与回复、build in public 涨粉、英文区搬运到中文区的信息差红利; (f) 变现(次要) — 广告 / 知识星球 / 社群 / 付费课程 / 咨询 / 导流。学派分歧: 编译搬运(英文一手翻译) vs 原创洞察、快讯资讯 vs 深度长推、锐评玩梗 vs 严肃干货、build in public vs 纯内容、全 AI 自动发 vs 人工精选。代表生态(宝玉/歸藏/向阳乔木/AI 进化论/小互/Gorden Sun 等)。不含: 英文 AI Twitter 圈(聚焦中文圈)、通用 X 增长营销、其他平台、AI 工具技术原理。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 推特(X) 中文圈 AI 自媒体博主 (从业者视角) — 在 X/推特 用中文做 AI 内容的自媒体博主，重点是**怎么写推文/thread、怎么制作内容**。覆盖: (a) 选题 — AI 模型发布解读 / prompt 技巧 / AI 工具实测 / AI 出海与独立开发(build in public) / 英文一手编译翻译 / 信息差 / AI 资讯快讯 / 深度长推; (b) 文案与内容结构(核心) — 单条推(开头钩子/信息密度/短句断行/配图截图/数据图)、长推与 thread(首条钩子/编号/逻辑链/结尾关注 CTA)、引用锐评(quote tweet)、排版可读性、配图(ray.so/carbon 代码图/产品截图/对比图); (c) 内容制作工作流 — 找信息源(英文一手/arXiv/官方/Reddit/HN)→选题→编译总结加洞察→写推/thread→配图→发布→互动维护; (d) AI 工具用于内容生产 — 英文一手编译总结(GPT/Claude/Kimi)、配图(ray.so/carbon/截图美化)、thread 工具(Typefully/Hypefury)、翻译、排程分析; (e) 平台机制与涨粉 — X 算法时间线(转评赞/互动权重/外链降权)、蹭热点借势、互动与回复、build in public 涨粉、英文区搬运到中文区的信息差红利; (f) 变现(次要) — 广告 / 知识星球 / 社群 / 付费课程 / 咨询 / 导流。学派分歧: 编译搬运(英文一手翻译) vs 原创洞察、快讯资讯 vs 深度长推、锐评玩梗 vs 严肃干货、build in public vs 纯内容、全 AI 自动发 vs 人工精选。代表生态(宝玉/歸藏/向阳乔木/AI 进化论/小互/Gorden Sun 等)。不含: 英文 AI Twitter 圈(聚焦中文圈)、通用 X 增长营销、其他平台、AI 工具技术原理。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「推特 ai 博主」「推特中文 ai」「x ai 自媒体」「推特 thread」「推特爆款推文」

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

Package and publish a skill to the skills.sh community registry, a public GitHub repo, or both. Load when the user asks to publish a skill, share a skill publicly, submit a skill to the registry, release a skill, or when universal-skill-creator offers publishing as a final step after creation. Also triggers on "push this skill to skills.sh", "make this skill public", "share this skill", or "contribute this skill to the community". Validates quality before publishing, packages correctly (zip for multi-file, .md for atomic), writes a README if missing, and publishes via npx skills CLI.

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

Operate FrontendExtension (FE) resources in frontend-forge: create, update, rebuild, inspect package artifacts, download packages, publish, unpublish, delete, and debug package/publish controller behavior. Use this skill whenever the user mentions FE operations, FrontendExtension lifecycle, extension package/download/publish/unpublish, artifact ConfigMaps, package Jobs, publisher Jobs, publish target ConfigMaps or Secrets, rebuild-token, package-state/publish-state labels, or troubleshooting FE status in a Kubernetes cluster.

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

Adds a new topic to CARLA's native ROS 2 interface — a publisher (BasePublisher + PublisherImpl, topic suffix, QoS, registration in ROS2::GetOrCreateSensor, a ProcessDataFrom* entry point and its call site in the UE4 plugin) or a subscriber that lets ROS drive an actor. Also covers adding a middleware (RMW) behind IPublisherMiddleware. Use when the user asks to "publish X to ROS from CARLA", "add a ROS topic/publisher/subscriber", "make the obstacle/lane-invasion sensor publish", "add odometry to ROS", or "add another RMW".

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

npm package maintenance and lifecycle management for monorepo extensions. Covers health audits, dependency sync, version bumping, changelog updates, pre-publish checks, coordinated publishing, and post-publish verification. **Triggers — use this skill when:** - User asks to "publish", "release", or "version bump" extensions/packages - User says "audit packages", "check package health", "dependency sync" - User asks to "update changelogs", "prepare release", "pre-publish check" - User mentions "npm publish", "version management", "package lifecycle" - User wants to "sync dependencies" or "align versions" across packages - User asks "what needs publishing" or "which packages changed" **Covers:** Monorepo with multiple npm packages under `extensions/`. Each package has its own package.json, CHANGELOG.md, README.md, and version. Packages are scoped (e.g. `@e9n/pi-*`) and published individually.

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

Query patent simple bibliographic (catalog) data from the Nexscope patent database. Triggered when users mention patent bibliographic information queries, patent basic info retrieval, patent catalog data, patent publication details, searching by patent number for inventors, patent applicant information, patent abstract retrieval, patent classification codes (IPC/CPC), patent citation queries, or any request to search for structured metadata by patent ID or publication number, patent brief bibliography, patent basic info, patent number lookup, patent abstract, Nexscope, or patent metadata. Even if the user does not explicitly mention "Nexscope" or "bibliographic info," this skill should be triggered whenever their need involves querying core bibliographic fields of specific patents.

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

Interact with your Public.com brokerage account using the Public.com API. Able to view portfolio, get stock quotes, place trades, and get account updates. To create a Public.com account head to public.com/signup.

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

Use when planning, configuring, or maintaining a Salesforce Mobile Publisher branded app — a customer-facing or partner-facing mobile app distributed through Apple App Store or Google Play, built on either the Experience Cloud (LWR/Aura) Mobile Publisher template or the Field Service Mobile Publisher template. Triggers: 'salesforce mobile publisher branded app', 'experience cloud mobile app store distribution', 'mobile publisher push notifications certificate', 'app store review rejection salesforce', 'mobile publisher version policy update'. NOT for the standard mobile app — use admin/lightning-app-builder-advanced. NOT for Field Service mobile — use admin/fsl-mobile-app-setup.

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

Publishes HTML or Markdown as display.dev URLs with public, company, or private access. Supports signup, claiming, sharing, browsing, bounded reads, exact edits, and comment iteration. Use when the user asks to "publish this", "share this", "share with the org", "post this online", "make a private link", "share with [email]", "publish a report", "list my artifacts", "find an artifact", "publish a large file", "publish this generated HTML file", "read this artifact", "search inside this artifact", "change this passage", "make a copy of this artifact", "duplicate version", "create a display.dev account", "claim this publish", "add a company email domain", "transfer an email domain", "change the email domains add-on", "show my referral link", "show referral rewards", "watch comments on this artifact", "respond to comments", or "resolve this comment thread". Use whenever a request contains a display.dev artifact URL (`*.dsp.so/*`). Anonymous publishing returns a 30-day preview and browser claim URL.

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

Adds a new topic to CARLA's native ROS 2 interface — a publisher (BasePublisher + PublisherImpl, topic suffix, QoS, registration in ROS2::GetOrCreateSensor, a ProcessDataFrom* entry point and its call site in the UE4 plugin) or a subscriber that lets ROS drive an actor. Also covers adding a middleware (RMW) behind IPublisherMiddleware. Use when the user asks to "publish X to ROS from CARLA", "add a ROS topic/publisher/subscriber", "make the obstacle/lane-invasion sensor publish", "add odometry to ROS", or "add another RMW".

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

非公開プロジェクトを公開用に複製し、秘密情報や個人情報の除去・検証から、READMEやセットアップ手順、ライセンスの整備まで進めるスキル。

• 非公開プロジェクトを公開したいとき
• 秘密情報や個人情報の残存確認
• 利用者向けの説明と導入手順の整備

重みが公開されたLLMの回答拒否に関わる仕組みを分析し、再学習なしで重みを変更する実験を支援。計算環境に合うモデルや手法の選択、変更前後の品質評価まで扱います。

• LLMの回答拒否の仕組みを調べたいとき
• 再学習せず重み変更を実験したいとき
• 計算環境に合うモデルと手法を選びたいとき

Publish a website or web app from the sandbox to a public URL, and deploy to cloud providers — get a live link to share, ship a static site or SPA, put a built site online, or deploy a framework app / container. Use when the user says 'publish this', 'deploy it', 'put it online', 'give me a live URL', 'host this', 'share a preview link', or wants to make a site/app they (or you) just built reachable on the web. Covers the zero-account instant path (Cloudflare) and permanent hosting (Vercel, incl. any Dockerfile). Also owns the publish GUARDRAILS: never publish unprompted, how to honestly take a site down, the runtime-dependency and data-persistence checks, and the mandatory pre-publish security review. Prefers Kortix Apps (a stable Kortix URL behind Kortix sign-in) when the project has Apps on. Points at kortix-marketplace for other providers and deeper provider-specific skills.

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

Hunt cloud / infrastructure misconfigurations. AWS: public S3 buckets (s3:GetObject anonymous), permissive bucket policies (PutObjectAcl public-write), exposed CloudFront origin, public Lambda function URL, public RDS snapshot, IAM credentials in JS bundles, AWS metadata accessible via SSRF. GCP: public GCS buckets, exposed Cloud Run services, leaked service account JSON. Azure: public blob containers, exposed Function App. (Kubernetes/Docker exposure is owned by hunt-k8s; CI/CD pipeline attacks by hunt-cicd; post-credential IAM escalation by cloud-iam-deep.) Detection: targeted dorking, certificate transparency, JS bundle secret extraction, port scan for known service ports. Validate: actual data read / write / RCE. Use when hunting cloud-native storage and compute misconfig (S3/GCS/Blob, IMDS-via-SSRF, serverless, public managed services).

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

End-to-end content creation and publishing. Takes a topic (or generates one), drafts in the user's voice, gets approval via Telegram, and publishes to Medium via browser automation. Invoke with "publish a post about X", "write and publish to Medium", "content-publish", or when an ego-dispatched session needs to create and distribute content.

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

Query patent bibliographic (catalog) information from the Nexscope patent database by patent ID or publication number. Triggered when users mention patent bibliographic info queries, patent catalog information, patent applicant queries, patent inventor queries, patent classification codes, patent abstract retrieval, patent citation analysis, patent priority claims, patent application citations, patent examiner information, patent bibliographic data, inventor lookup, applicant lookup, patent classification, patent metadata, Nexscope, or patent citations. Even if the user does not explicitly mention "bibliographic info," this skill should be triggered whenever their need involves querying detailed metadata for a specific patent by patent ID or publication number.

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

Redact reverse-engineering findings for public disclosure while preserving methodology, generalizable patterns, and teaching value. Covers the private-vs-public repo split, deny-list pattern maintenance, orphan-commit publish pattern that prevents `git log` leaks, category-based redaction calibration (methodology/pattern/version-finding/internal), and the `check-redaction.sh`-style CI gate that blocks merges when a deny-listed pattern appears. Use when publishing findings about a CLI harness you don't own, when preparing upstream proposals to an unrelated project, or when archiving a private research repo for public reference.

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

OpenClawのセキュリティ勧告を確認・修正し、非公開フォークの未完了PRや公開条件を検証。承認を経た公開と、公開後の状態確認まで扱うスキル。

• 勧告と非公開フォークの状態確認
• 脆弱性情報や重大度を更新したいとき
• 承認前に公開条件を確認したいとき

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

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

Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: <patch|minor|major|explicit-semver>. Triggers: publish, release, deploy, npm publish.

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

Build and publish a self-contained HTML page to Superset, then answer the comments readers pin to it. Use this instead of publishing a Claude artifact whenever the reader is a teammate: a page is listed in the org, every publish mints a version, and pinned comments come back to the agent. Use when the user asks to make or publish a page, turn a report, dashboard, chart, doc, or analysis into a shareable link, update or re-version a page already published, or work through comments left on one, including "make me a page for this", "publish this as a page", "share it as a link", "add a version", "address the comments on that page". Also use it unprompted to offer a page when you finish output a teammate will read: a change or PR walkthrough, a comparison, a report or digest, an incident writeup, or verification screenshots.

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