1,983 件 ・ 関連度順
概要と使いどころ
Build a fully automated AI-powered data collection agent for any public source — job boards, prices, news, GitHub, sports, anything. Scrapes on a schedule, enriches data with a free LLM (Gemini Flash), stores results in Notion/Sheets/Supabase, and learns from user feedback. Runs 100% free on GitHub Actions. Use when the user wants to monitor, collect, or track any public data automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for building with the Astro web framework. Helps create Astro components and pages, configure SSR adapters, set up content collections, deploy static sites, and manage project structure and CLI commands. Use when the user needs to work with Astro, mentions .astro files, asks about static site generation (SSG), islands architecture, content collections, or deploying an Astro project.
日本語の概要は準備中です。原文の説明を表示しています。
对 profiling 数据（kernel_details.csv / trace_view.json / step_trace_time.csv）做统一分析： 5 层递进管道（analyze_trace.py）+ baseline/优化后 kernel diff（compare_traces.py），输出 瓶颈诊断、算子执行序、可融合候选与 P0-P2 方向建议。输入统一来自 profiling-collect。 只要用户有 profiling 产出并问"为什么慢/瓶颈在哪/优化前后差多少/往哪个方向"，都用本技能；采集走 profiling-collect，方案选档走 dit-perf-opt，实现/并行/基准走 pattern-dev/dit-parallel-opt/benchmark-dev——本技能只做诊断与方向。 由 model-auto-optimization 的 S1（融合分析）/S3（并行）阶段调用，亦由 dev-workflow 的分析阶段指引加载。 融合机会候选只做**识别**；候选的**边界与收益判定**（能不能融成一个单元、融多大、值不值）交 `fusion-scope-analyze`（本技能的辅助技能）——本技能不判融合边界。
日本語の概要は準備中です。原文の説明を表示しています。
三方框架特性落地（原 framework-feature-enablement ＋ framework-extension-dev 合并）： 一个入口信号「框架侧特性没落地」，内部分两分支——**分支 A 框架已有 → 使能与验证** （计数契约 + 三层证据 + 使能异常回修）；**分支 B 框架缺失 → 补齐开发** （注入点 + 代码组织/注册机制 + 合入姿势：平台注册优先 / 上游 PR / fork 钉版 / monkey 备选）。 分支 A 触发词：量化/稀疏/缓存开关没生效、融合算子没命中、使能异常或精度不符、 "起 vllm 服务""模型在框架里跑不通""把 mindiesd 接到其他框架"。 分支 B 触发词：框架没 comm-stream 掩盖、框架没缓存消费者、框架不支持某 collective/mask、 feature_* NotImplemented、要给框架补一条结构性能力。 near-miss：纯安装/权重 → env-install；纯采集/分析 → profiling-collect / profiling-analyze； 纯选档（该不该开量化、开哪一档）→ dit-perf-opt； mindiesd 仓内 pattern / 算子 / 图下发开发 → dev-workflow + pattern-dev / operator-dev / aclgraph-dev。 由 model-auto-optimization 的 S1（融合接入）/S4（有损使能）/S5（训练感知）与 §0 缺口补齐策略路由， 亦由 dev-workflow 的框架接入/验证场景指引加载。
日本語の概要は準備中です。原文の説明を表示しています。
Generates a post-judgment asset and enforcement report synthesizing debtor asset investigations, exemption analysis, fraudulent transfer assessment, and prioritized collection strategies. Use when preparing judgment enforcement plans, debtor asset profiles, collection status reports, or post-trial recovery analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building content-heavy sites with Astro, deciding between SSG/SSR/hybrid, choosing client directives (idle/visible/load/media), structuring content collections with type-safe schemas, integrating React/Vue/Solid/Svelte components in the same project, or migrating from Next.js for marketing/docs. Triggers: client:idle vs client:load tradeoffs, content collections schema with zod, image optimization via @astrojs/image, view transitions, server islands, MDX layouts. NOT for SPA-style apps that need full interactivity (use Next/Remix), Astro internals/plugin authoring, or non-content sites where islands provide no benefit.
日本語の概要は準備中です。原文の説明を表示しています。
Compose multi-panel publication figures with patchwork, cowplot, gridExtra (R), or matplotlib GridSpec/subfigures (Python) including shared axes/legends/guides collection, panel labels in Nature/Cell convention, and journal-spec sizing. Covers patchwork ≥1.2.0 axes='collect' feature, Type-42 font embedding, and the cairo_pdf save path. Use when composing 2+ subpanels into a single figure for journal submission.
日本語の概要は準備中です。原文の説明を表示しています。
Save, load, update, delete, merge, and navigate entity objects using TMS Aurelius ORM (TObjectManager). Use when the user asks how to persist or retrieve data with Aurelius, manage object lifetime, work with associations or collections at runtime, handle transactions, use cached updates, or control concurrency. Does NOT cover query DSL or criteria/projections (those are in a separate skill). Triggers on requests like "save an entity with Aurelius", "load a customer from the database", "add items to a collection", "how do I update an object", "flush changes", "delete a record with Aurelius", "merge a transient object", "how do transactions work in Aurelius", "batch updates Aurelius".
日本語の概要は準備中です。原文の説明を表示しています。
Skill for building with the Astro web framework. Helps create Astro components and pages, configure SSR adapters, set up content collections, deploy static sites, and manage project structure and CLI commands. Use when the user needs to work with Astro, mentions .astro files, asks about static site generation (SSG), islands architecture, content collections, or deploying an Astro project.
日本語の概要は準備中です。原文の説明を表示しています。
Manages government affairs, public policy communications, and collective action aligned with B Corp GACA standards. Creates policy position papers, advocacy communications, regulatory response documents, and transparent lobbying reports. Use when user asks about government relations, public policy, advocacy, lobbying, regulatory affairs, collective action, or political engagement transparency.
日本語の概要は準備中です。原文の説明を表示しています。
Virtual QA Lead that turns requirements into review-ready, TestRail-importable test cases in one conversation. Use it whenever the user has requirements, a spec, a user story, or acceptance criteria (PDF, DOCX, XLSX, TXT, MD, or pasted text) and wants test cases, a test plan, a checklist, test coverage, a regression suite, or a TestRail/Qase/Zephyr export, even without saying "test cases" ("write tests for this spec", "what should we check here?"). Especially useful when they attach their team's existing test cases to match. When the spec describes an API (endpoints, status codes, schemas, auth, OpenAPI/Swagger), Casely also builds a runnable Postman collection, so use it for "API tests", "Postman collection", or "tests I can run in Newman/CI". Triggers on the same request in any language.
日本語の概要は準備中です。原文の説明を表示しています。
Run evidence-disciplined Xiaohongshu social listening for foreign pharma employee pain points. Use when the user asks to collect and analyze notes/comments about pharma companies, aliases, roles, compliance, medical affairs, or AI topics, then produce a cited and scored sampled-insight report. Includes independent-evidence counting, MediaCrawler batch collection, and CAPTCHA/461 fallback to Agent Reach/OpenCLI.
日本語の概要は準備中です。原文の説明を表示しています。
Build a fully automated AI-powered data collection agent for any public source — job boards, prices, news, GitHub, sports, anything. Runs on a schedule, enriches data with a free LLM (Gemini Flash), stores results in Notion/Sheets/Supabase, and learns from user feedback. Runs 100% free on GitHub Actions. Use when the user wants to monitor, collect, or track any public data automatically.
日本語の概要は準備中です。原文の説明を表示しています。
The migration step and the package-owned-table exception — NOT the normal collection flow. For app collections use the crouton CLI/skill (schema JSON → `crouton config`); reach here when you then need to generate/apply the Drizzle migration and hit the schema.mjs-only-after-build gotcha ("No schema files found"), or when adding a package-owned infra table (the crouton-flow pattern) that does NOT go through `crouton config`.
日本語の概要は準備中です。原文の説明を表示しています。
Notion ページを描画する直前に粒度を検証したいとき、info-collector-agent ページと同等の section 充足度を section_canonical_map 基準で機械検証したいときに使う。
Collect volatile forensic evidence from a compromised system following order of volatility, preserving memory, network connections, processes, and system state before they are lost.
日本語の概要は準備中です。原文の説明を表示しています。
Collects and synthesizes open-source intelligence (OSINT) about threat actors, malicious infrastructure, and attack campaigns using publicly available data sources, passive reconnaissance tools, and dark web monitoring. Use when investigating external threat actor infrastructure, performing pre-engagement reconnaissance for authorized red team assessments, or enriching CTI reports with publicly available adversary context. Activates for requests involving Maltego, Shodan, OSINT framework, SpiderFoot, or infrastructure reconnaissance.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Nuxt Content v3 - provides collections (local/remote/API sources), queryCollection API, MDC rendering, database configuration, NuxtStudio integration, hooks, i18n patterns, and LLMs integration
日本語の概要は準備中です。原文の説明を表示しています。
명령형 for/while 루프를 Stream API/Collection Pipeline으로 변환하여 데이터 흐름 의도 명확화. "스트림으로 바꿔", "루프를 파이프라인으로", "for문 stream", "/replace-loop-with-pipeline" 요청 시 사용. 단, 루프 안 로직이 컬렉션 클래스로 모여야 하면 /first-class-collection이 적합. /replace-loop-with-pipeline [commit-ref]로 호출.
日本語の概要は準備中です。原文の説明を表示しています。
Add or improve canonical data catalog collections, fields, aliases, relations, evidence tags, docs, and tests.
日本語の概要は準備中です。原文の説明を表示しています。
Erkennt Nutzeraufträge der Form "hole aus einem Ordner immer bestimmte Dateien und sammle sie an einem Ziel" und richtet dafür das Modul file-collect-sort-action (CLI fcsa) ein — ein konfigurationsgetriebener Agent, der Ordner scannt, Dateien per Schablone kategorisiert und gestufte Aktionen anwendet (move/copy/duplicate-check/delete/OCR/place-information). Nutze diesen Skill bei Sätzen wie "hole aus <Ordner> immer <Dateiart> und sammle sie in <Ziel>", "sortiere den Ordner X automatisch nach ...", "sammle eingehende Dateien aus ... in ...", "räume diesen Ordner regelbasiert auf" oder "verschiebe alle <Dateiart> aus <Ordner> automatisch". Richtet IMMER zuerst einen Dry-Run ein und schaltet erst nach ausdrücklichem Nutzer-Go scharf; Löschen bleibt grundsätzlich im _trash-Modus.
日本語の概要は準備中です。原文の説明を表示しています。
Build an Anima LoRA from a single-character or style name, from Danbooru collection through curation, section-ordered WD14 captions, dataset checks, confirmed training, fixed-seed checkpoint validation, and a staged Civitai draft. Use for requests such as make a LoRA of X, collect images and train a character LoRA, train and upload to Civitai, or build a dataset from scratch and publish. Delegate training to lora-trainer and structural checks to dataset-doctor; never train without confirmation and never auto-publish.
日本語の概要は準備中です。原文の説明を表示しています。
/nix/store 配下の store path・ファイルを特定するときに必ず参照する。`find /nix/store` で名前を総当たりする前に読む。「あのパッケージの store path が知りたい」「nix-unit のバイナリはどこ」「flake input の実体パスを知りたい」「derivation の出力パスを取りたい」「store の中のこのファイルを探したい」「store path が実在するか確かめたい」といった場面が対象。/nix/store は数万エントリあり深さ無制限の find は完了しない（実測: 20秒でも終わらず出力ゼロ）。同梱の collect_store_lookup.sh が入力の種別判定・一意な解決・候補収集・実在確認までを決定論的に行うので、まずそれを実行してから分析する。nix-locate が返す path はローカルに存在しないことがあるという反直感的な挙動も、データとして検出される。
Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.
日本語の概要は準備中です。原文の説明を表示しています。