「public」の検索結果

Suede-owned launch packaging and install verification. Use when finished software work needs a clean public package (README, docs page, install command, release note, GitHub Pages update, skill-pack release, MCP server, or launch/social copy) or when a release needs handoff notes, an install fails, a public user cannot add a skill, a raw-vs-blob URL returns HTML, or `@personal` or a local plugin alias leaks into public docs. Verifies the live URL and runs the exact install command from a clean temporary directory before anything is called live. NOT FOR: product, course, or artist campaign launches (use suede-campaign-in-a-box or suede-marketing-plan); writing announcement copy from scratch (use suede-copy); MCP tool-catalog QA (use suede-mcp-qa); landing-page conversion work (use suede-site-alchemy).

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

Suede Labs full writing stack: sharper copy for docs, pages, email, social, headlines, CTAs, product listings, and public explainers, with an SEO/AEO/AI EO pass, persona and framework selection, brand-voice alignment, and a scored ship gate. Use when a writing job spans more than one surface, needs a voice retune as well as a draft, needs discoverability metadata alongside the copy, when the document is one an agent reads such as a SKILL.md, CLAUDE.md, or AGENTS.md, or when the user asks for 'the full writing stack', a launch package, or a public explainer talk-track. NOT FOR: one standalone conversion surface in one pass (use suede-copy); stripping AI patterns from text you did not write (use suede-deslop); a researched multi-phase piece for a high-stakes public surface (use suede-ship-copy); a deep standalone SEO audit (use suede-seo-audit); copy that ships inside a design or layout build (use johnny-suede-design).

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

When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.

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

Deploys the current project to a live HTTPS URL via Cybrix. Activates on any request to make the current project public, get a URL for it, deploy it, ship it, host it, publish it, put it online, or make it live — including casual phrasings like "send this to the internet", "share this as a link", "give me a URL", "make this accessible online". Activates whether the user mentions Cybrix by name or not (when no other host like Vercel, Netlify, Cloudflare Pages, Railway, or Render is named). Also activates on equivalent phrases in other languages — Russian ("задеплой", "опубликуй", "выложи в сеть", "запушь это в инет", "сделай ссылку"), Spanish ("despliega esto", "publica esto", "ponlo en línea"), German ("deploy das mal", "stelle das online"), and other common languages where the intent is clearly to make a project publicly accessible via URL. Uses heuristic detection to determine if a project is static or needs a server runtime — works with any framework, not just a known list. Automatically detects and handles environment variables so the build receives everything it needs. Returns a live URL on *.cbrx.cc or a user-configured custom domain. Does NOT activate when the user explicitly names a different host (Vercel, Netlify, Cloudflare, Railway, Render).

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

Maintain user-owned GPG and SSH public-key parsing, profile API registration, identity database persistence, format compatibility, and maintained OpenPGP dependencies. Excludes portal signing-key publication and admin private-key export.

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

Icarus Figures produces publication-grade figures for scientific papers — reproducible matplotlib/seaborn data figures and original TikZ method/framework/architecture figures, held to a four-axis quality bar (depth · elegance · unimpeachable · visible-gap) and exported as editable PDF+PNG+SVG with a runnable critique gate. Use this whenever a figure is destined for a paper, journal, conference submission, thesis, or report — making a plot/chart publication- or journal-ready, building a method/architecture/framework diagram or 技术路线图 (the hero figure a paper opens with), a schematic or workflow figure, or cleaning up a matplotlib/seaborn/TikZ figure that currently looks like a homework plot. Trigger even when the user never says "publication": if the figure goes into a written scientific document, this skill applies.

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

Audit an already completed protected Proto UI publication and reconcile immutable external facts with Version entities, release records, and public projections. Use after publication for registry, tag, GitHub Release, asset, checksum, workflow-head, and deployment evidence. Never republish or replace immutable evidence.

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

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

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

Product marketing and go-to-market strategy for B2B SaaS launches and positioning. Use this skill when planning a product launch, developing positioning and messaging, analyzing competitive landscape, building customer advocacy programs, designing a customer referral program (who may accept the reward, how the introduction is made), designing a win/loss interview program, working out why we lose deals, designing GTM strategy, creating category positioning, planning analyst briefings, or deciding which country to expand into and how far to localize. Also use it for an early-stage startup where the founder is still doing the selling — running founder-led sales, setting up a design-partner program, judging whether you have product-market fit, deciding what not to do yet, deciding when to hire the first AE or first marketer, and moving upmarket to larger buyers. Also use it when your company has just acquired another (or is about to), to plan the marketing integration: what you may and may not do between signing and close, the first letter to the acquired customers, whether to keep, endorse, fold in or retire the acquired brand, merging the two marketing databases without mailing people who opted out, when to start cross-selling, and announcing a product sunset. Also use it to design a demand-generation campaign and the channel plan it runs on: one campaign with one job, the offer for buyers who are and are not in market, what each channel is for, the kill and scale rules set before launch, the follow-up sales agrees to, the yearly calendar of always-on programs and tentpole campaigns, and which channels to keep, test or stop. Also use it for brand marketing and demand creation — how much to spend on brand versus performance, what to measure when a brand campaign produces no conversion event, and how to answer "we cannot attribute it". Also triggers on: founder-led sales, founder-led GTM, design partners, design partner agreement, first customers, first 10 customers, do we have product-market fit, PMF, Sean Ellis test, very disappointed survey, pre-seed, seed stage, when to hire our first AE, first sales hire, first marketing hire, moving upmarket, going upmarket, enterprise readiness, first enterprise deal, what do enterprise buyers need before they sign, positioning, product launch, beta program, early access program, design partners, private preview, public preview, general availability, GA launch, when can we call it GA, can sales sell a beta feature, selling the roadmap, launch tier, competitive intelligence, messaging, customer advocacy, win/loss analysis, win/loss interviews, why we lose deals, closed-lost analysis, loss reason, close-reason field, competitive displacement, displace an incumbent, rip and replace, competitive takeout, switch from a competitor, win deals from a competitor, incumbent contract, renewal window, auto-renewal notice period, switching costs, EU Data Act, cloud switching rights, why do we lose to no decision, GTM, category design, ideal customer profile, ICP, what is our real ICP, who actually buys from us, refresh our ICP from closed-won deals, ICP refresh before planning, analyst briefing, G2 review, international expansion, market entry, expand into Europe, which country should we launch in next, localization, translate our site, in-country go-to-market, regional GTM, is cold email legal in Germany, brand marketing, brand awareness, brand vs performance, brand versus demand gen, demand creation, demand capture, 95-5 rule, out of market buyers, category entry points, distinctive brand assets, mental availability, brand tracking, brand health, brand lift, share of search, how do we measure brand, justify brand spend, brand budget. Also triggers on public-sector marketing: sell to government, government marketing, public sector go-to-market, federal marketing, state and local government, SLED, FedRAMP, FedRAMP marketing claims, can we say FedRAMP ready, GovRAMP, StateRAMP, VPAT, accessibility confor

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

Generate publication-ready methods sections, figure legends, supplementary tables, and data availability statements from ENCODE analysis provenance. Implements the scientific documentation standards requiring complete metadata reporting. Use when the user needs to write methods, generate figure legends, create supplementary tables, draft data availability statements, compile tool citations, or auto-generate any publication text from their ENCODE analysis. Trigger on: methods section, figure legend, supplementary table, data availability, tool citations, publication writing, manuscript, write methods, methods draft, write up, write-up, paper writing, reproducible methods.

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

Public Sector Solutions (PSS) setup: licensing, permits, inspections, benefits, case management for government, citizen portals, and grant management. NOT for standard Service Cloud cases — use admin/case-management-setup. NOT for a plain portal site — use admin/experience-cloud-site-setup.

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

Run read-only SQL against BigQuery public datasets with local result capture, cost safeguards, and reproducibility outputs.

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

Route ordinary public-web information tasks to the correct Tavily CLI operation. Use when the task concerns publicly accessible webpages and needs web discovery, clean extraction, URL mapping, same-site crawling, or public-web-only research, but the exact Tavily operation is not yet clear or several operations must be sequenced. Prefer the specific leaf skill when intent is clear: tavily-search for discovery without a URL, tavily-extract for known URLs, tavily-map for URL/site-structure discovery, tavily-crawl for content from many pages on one site, tavily-research for cited multi-source synthesis, and tavily-dynamic-search for programmatic filtering with context isolation. Do not use for named social/community/media/career/code platforms, login or cookie-dependent content, platform-native discussions, or cross-platform collection; use Agent Reach there. Do not use for local files, Git operations, deployments, or ordinary code editing.

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

Discover ordinary public webpages with LLM-optimized Tavily search results. Use when no specific URL is known and the user needs a quick public-web lookup, articles, recent news, sources, or domain-filtered results. This is the default Tavily leaf for simple public-web discovery. Do not use when the user already supplied the target URL (use tavily-extract), wants URLs under one known site (tavily-map), wants many pages' content (tavily-crawl), needs a full cited synthesis (tavily-research), or needs named platforms, login state, platform-native content, or cross-platform collection (Agent Reach).

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

Make public, read heavy Convex + Vite pages load fast on first visit, return visit and in app navigation. Use when a public page feels slow, when adding a new public page, analytics, images, markdown or other heavy dependencies, when touching index.html, netlify.toml, _headers, _redirects or vite.config.ts, or when the user mentions "slow", "load time", "LCP", "bundle size", "waterfall", "websocket handshake", "cache headers", "thumbnails" or "far from the deployment".

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

Apply public, contributor-safe commit hygiene without maintainer-private automation, timestamps, ledger rules, or push policy.

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

Review public repository changes for secrets, private paths, signing identities, bundle IDs, generated artifacts, local logs, and private workflow leaks.

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

When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.

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

Creates sashimi-style plots showing RNA-seq read coverage and splice junction counts using ggsashimi (general-purpose, condition-grouped overlays), rmats2sashimiplot (rMATS-output-aware), MAJIQ-VOILA (LSV posteriors interactive HTML), leafviz (leafcutter clusters Shiny), Jutils (tool-agnostic heatmaps and sashimi for rMATS/leafcutter/SUPPA2/MAJIQ output), or pyGenomeTracks (multi-track publication figures). Tool choice depends on the upstream differential-splicing tool's output format and the publication vs interactive use case. Use when visualizing specific splicing events, validating differential splicing calls, or producing publication-quality figures.

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

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.

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

Creates sashimi-style plots showing RNA-seq read coverage and splice junction counts using ggsashimi (general-purpose, condition-grouped overlays), rmats2sashimiplot (rMATS-output-aware), MAJIQ-VOILA (LSV posteriors interactive HTML), leafviz (leafcutter clusters Shiny), Jutils (tool-agnostic heatmaps and sashimi for rMATS/leafcutter/SUPPA2/MAJIQ output), or pyGenomeTracks (multi-track publication figures). Tool choice depends on the upstream differential-splicing tool's output format and the publication vs interactive use case. Use when visualizing specific splicing events, validating differential splicing calls, or producing publication-quality figures.

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

When the user requests to create or customize an academic personal website from a GitHub template repository. This skill handles the complete workflow of forking academic template repositories (like academicpages.github.io), extracting structured personal information from memory or provided data, and systematically updating configuration files (_config.yml), navigation menus (_data/navigation.yml), content pages (_pages/about.md), and publication listings (_publications/). It specifically handles academic profiles including personal details, education background, research experience, publications, skills, and contact information. Triggers include requests to 'fork and customize academic homepage', 'build personal academic website', 'create research portfolio', or 'set up GitHub pages with academic template'.

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

OpenClawの通常版とextended-stable版について、公開先、配布物の出所、テスト結果、Gatewayの実動作を照合し、リリース状況を確認します。

• stable版の公開完了を確認したいとき
• プラグインの配布漏れを確認したいとき
• extended-stable版の証拠確認

機能追加やバグ修正を、失敗するテストと最小限の実装の順に進めます。利用者が使う公開インターフェースを通じて動作を確かめ、内部構造に依存しないテストを作るスキルです。

• テストを先に書いて機能追加したいとき
• バグの再現テストから修正したいとき
• 統合テストの対象を決めたいとき