「cold-start」の検索結果

账号被限流/异常/担心操作触发风控/需要恢复时用：先自检from:@用户名搜不到即限流→区分临时标签(等24h不动账号)与正式标签(写申诉邮件+48h不操作)→复盘触发原因预防复发。Trigger："推文搜不到了""被限流了""账号异常""触发风控""临时标签""怎么申诉""shadowbanned""account suspended""appeal suspension""tweets not showing up"。不适用：正常发内容没出问题(→内容创作skill)、新号开业装修养号(→x-account-setup)、没粉丝怎么起量(→x-cold-start-playbook)。

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

规划变现路径/判断够不够格开创作者收益/决定卖什么产品时使用。三层金字塔定位：底层流量型(商单+广告分成,需500蓝V+3月5M曝光)、中层产品型(课程/付费专栏/带货)、顶层服务型(咨询/高端社群,利润率>80%)。IP路线可叠三层,泛流量卡底层。Trigger："怎么变现""够不够格开收益""卖什么产品""monetize""creator revenue""what to sell"。不适用：没粉丝的冷启动(→x-cold-start-playbook)、选IP还是泛流量(→x-positioning-tradeoff)、开蓝V/装修(→x-account-setup)。

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

Use when scraping JavaScript-heavy pages or SPAs, crawling multiple URLs concurrently, extracting structured data with reusable CSS/JSON schemas, or building automated web data pipelines. Wraps the Crawl4AI library (`crwl` CLI and Python SDK) with schema-generation patterns for LLM-free extraction. Triggers on crawl4ai, crwl, scrape JS-heavy site, scrape SPA, headless browser scrape, schema-based extraction, batch crawl, sitemap crawl, web data pipeline. SKIP when a static HTML page can be read with `defuddle` / `fetch-web` — those are faster cold-start and don't need a browser.

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

Use Therapeutics Data Commons through the PyTDC Python package for registry discovery, approved dataset access, task-aware splits (scaffold, cold-start, temporal, combination), evaluator metrics, benchmark groups, and bounded molecular-oracle workflows. Use this skill to find which TDC datasets exist for a therapeutic task, load them with a split that does not leak, score predictions with the task's own official metric rather than a generic one, and run benchmark groups reproducibly. Also trigger on PyTDC, Therapeutics Data Commons, tdc.single_pred, tdc.multi_pred, ADMET Benchmark Group, scaffold split, get_split, or molecular oracles such as GSK3B, JNK3 and DRD2.

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

Design guide + benchmarked pitfalls for building Monte-Carlo / Simulated Annealing refinement layers on top of greedy hex-grid layouts for code visualization (packages/gui/src/store/hexLayout.ts, sandbox/hex-sandbox, future Rust ports). Use when: (1) planning to add MC/SA on top of an existing hex-grid pack, (2) deciding whether a simpler SA would match a hierarchical MC with force-directed + chain drag, (3) budgeting wall-clock for million-node cold-start, (4) debugging "blob turns Swiss-cheese" or "folders stop nucleating" during MC refinement, (5) choosing between folder cohesion and raw Σ-link-length as cost function. Contains four hard-won, quantified lessons and anti-patterns that would take a full day of experiments to rediscover.

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

Read-only repository explorer. Use PROACTIVELY for cold-start exploration, broad cross-file localization, or when a direct search has failed and you need to find where something lives. Skip it when the issue already names the exact file or symbol, or a previous turn already returned usable file:line evidence. Returns only compact path:line citations; its reads and greps never enter the main conversation.

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

对 AI 治理合规 profile 做单点调整——不需要重跑整个 cold-start 访谈。可调公司基础信息、AI 活动角色（Provider/Deployer）、监管足迹、红线清单、用例注册表、供应商立场、政策承诺、备案状态、集成状态 9 大节中的任意子项。 用户说"改我的 [某项]""更新一下 ai-governance profile""调一下红线""微调供应商立场""customize"时触发。 本 skill 仅覆盖中国大陆 AI 治理法规——其他法域 AI 治理请走当地服务或律所。

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

初始化访谈，将业务规范写入 $LEGAL_AGENT_PROFILE_HOME/ai-governance-legal/profile.md。所有其他技能的先决条件。 本 skill 仅覆盖中国大陆 AI 治理法规——其他法域 AI 治理请走当地服务或律所。

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

Maintains repo-local action contracts and harness repositories where product CLI and MCP adapters stay thin over core libraries. Use when adopting or improving steward.yaml actions, capability-level adoption evidence, cold-start proof loops, probes, benchmarks, CLI/MCP/core parity, adapter refactors, packages/core boundaries, or sibling harness layout; use repo-quality-system-lifecycle first for general app/library/tool stewardship baselines.

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

Establish or audit a structural quality contract for any agent-operated engineering repository: app, library, CLI/tool, plugin, harness, or meta repo. Use when a repo needs charter clarity, docs/decision ownership, type-native validation gates, evidence paths, safe action policy, cold-start legibility, maturity proof, repair-loop routing, consumer/producer owner-boundary routing, command surface evolution, evolutionary simplicity (see references/evolutionary-simplicity.md), or a repo ecology pass to decide what should be compressed, merged, removed, updated, created, retired, or moved to checks.

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

Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists. Use when refactoring custom validation CLIs/MCPs for large polyrepos, extending Steward across sibling repos, or deploying a local tool to a consumer project for dogfooding and testing; use mcp-harness-repo-maintainer first for initial steward.yaml adoption and cold-start proof.

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

从对标账号导入 script + 数据 → 拆 pattern + 派生 base rubric 信号 → 写到 benchmark.md / script_patterns.md / rubric_notes.md。**这是工具最早期信号的来源**——cold-start 用户没自己历史时全靠对标，发过历史的用户也建议至少 1 个对标做 sanity check。触发词："学这个账号"/"拆这几个对标视频"/"learn from"/"导入对标账号"/"找对标"。

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

Recreate the nuxt-crouton dev environment from scratch and survive its install/build traps — the pnpm toolchain, the cold-start sequence (why packages must build before apps prepare), the version catalog and workaround pins, the per-app typecheck rule, required env vars, and the known environment traps. Use when setting up a fresh clone/worktree, when "pnpm install" or "nuxt prepare" fails, when an app won't boot after install, when typecheck output looks insane, or when a tool "isn't available". Trigger phrases: "set up the repo from scratch", "why does typecheck show thousands of errors", "playwright install fails", "what pnpm/node version". (Exact error strings — "Could not load '@fyit/crouton'", "Cannot find module '@vue/compiler-sfc'" — route via crouton-diagnostics-index first; it points back here for depth.)

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

Adversarial reviewer for The Federated Harbor whitepaper — the third paper in the Curiositech sequence after Anchor and Bonded Commons. Probes federation-specific threats: trust transitivity, cross-harbor token forgery, federated revocation under partition, cross-harbor Sybil, cross-domain settlement, equivocation, bond-pool draining, cold-start joining, federation-operator Sybil. Use during a versioned red-vs-white round; pairs with federated-harbor-whitehat. NOT for incident response, NOT for the Anchor or Bonded papers (use redteam-review).

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

Design discovery, directories, and guilds for agent swarms at scale. Use when agents need to find each other on a shared surface: capability indices, yellow-pages directories, whois/phonebook routing, reputation-aware discovery, and guild structures that scope trust. Covers the canonical prior art (FIPA Directory Facilitator, Contract Net, Chord/DHT, DNS-SD/Consul, EigenTrust, Greif's merchant guilds) and the failure modes (read-poverty, Sybil reset, Goodhart on rank, directory staleness, cold-start). Triggers: "agents can't find each other", "who owns this file/skill", "route a question to the right agent", "capability registry", "agent reputation", "guild / federation of fleets". NOT for issuing identities, granting authority, or automatically assigning work from a directory entry.

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