4,901 件 ・ 関連度順
概要と使いどころ
Analyzes the PE Rich header and related compiler artifacts to fingerprint the build toolchain, cluster related samples, and detect inconsistencies that suggest tampering. Activates for requests to analyze a Rich header, fingerprint the compiler/linker, or cluster samples by build toolchain.
日本語の概要は準備中です。原文の説明を表示しています。
Pick the right Pulp Stream for a given I/O task, wire async callbacks correctly without deadlocking the worker, and avoid the backpressure / cancellation footguns in `pulp::runtime::AsyncStream`.
日本語の概要は準備中です。原文の説明を表示しています。
Forge Modular's generator, patch checker, module pack and Forge-worktree seam — the traps that make green results untrue
日本語の概要は準備中です。原文の説明を表示しています。
Leveraged-prototype dev loop (`pulp loop`) — focus marker plus normal watch/rebuild loop, with AOT analyzer guidance and deferred ar-swap/PR-monitor playbook. Use when porting an existing UI/bundle to Pulp, doing visual/behavioral parity work, or batching upstream framework gap fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Client reporting, quality assurance, and financial operations management. Handles KPI frameworks, compliance audits, budget tracking, and launch checklists. Use when: managing client dashboards, ensuring brand compliance, conducting QA reviews, tracking marketing spend, ensuring GDPR/CAN-SPAM compliance, handling a request to delete someone's data across the marketing stack, deciding whether an AI voice or AI presenter has to be disclosed, proofreading deliverables. Also triggers on: client reporting, QA, quality assurance, brand compliance, marketing budget, financial tracking, legal compliance, GDPR, CAN-SPAM, proofreading, launch checklist, right to erasure, right to be forgotten, data deletion request, DSAR, someone asked us to delete their data, do we delete or suppress, suppression list, they unsubscribed and we emailed them again, we deleted them and they came back, restored a backup and re-emailed people, custom audience still has deleted contacts, California Delete Act, DROP, data broker deletion, enrichment records disappearing
日本語の概要は準備中です。原文の説明を表示しています。
Developer marketing and developer relations for B2B SaaS with technical audiences. Use this skill when the buyer or user is a developer: documentation as a marketing surface, quickstarts and time-to-first-call, SDKs and sample apps, developer community and DevRel programs, open-source strategy, and technical content that survives engineer scrutiny. Also triggers on: developer marketing, DevRel, developer relations, developer experience, DX, docs, documentation, quickstart, SDK, API marketing, open source strategy, developer community, technical content, dev audience, hacker news, engineering blog.
日本語の概要は準備中です。原文の説明を表示しています。
Design clean, graphics-first technical presentations and posters with logical slide progression, visual hierarchy, purposeful motion, and complementary speaker notes. Use for research talks, conference slides, seminars, defenses, posters, or figure-focused presentations.
日本語の概要は準備中です。原文の説明を表示しています。
DevOps/运维角色。关键词：部署/上线/CI-CD/服务器/Docker/nginx/SSL/域名/端口/监控/GitHub Actions。接收测试通过报告后执行部署，维护生产环境，监控AI调用成本。
日本語の概要は準備中です。原文の説明を表示しています。
项目规范问题自动修复 Skill。当用户指出项目内的规范偏差时，自动分类问题类型，路由到对应角色Skill执行修复，并通过verifier验证修复效果。类比产品侧「问题追踪+修复」的完整闭环，是项目内规范问题的「接收→分类→执行→验证」一体化机制。触发词：「这里有个规范问题」「这不符合规范」「规范偏差」「按规范修复这里」「这里违反了规范」「规范不对」「帮我修复规范问题」。注意：与 issue-tracker 的区别——后者只记录不执行；本 Skill 记录并自动路由执行。
日本語の概要は準備中です。原文の説明を表示しています。
追踪文章审稿意见，将编辑反馈结构化记录并逐条落实。触发词：审稿意见/修改文章/这里写得不好/审稿反馈/帮我追踪这个意见。
日本語の概要は準備中です。原文の説明を表示しています。
用户报告问题时的结构化拆解与追踪。将一个问题拆解为「产品设计类」和「技术实现类」，分别记录到对应的追踪文件，确保产品经理和技术架构师下次激活时能感知到未解决问题。触发词：「有个问题」「发现了bug」「这里不对」「用不了」「为什么会」「有个bug」。
日本語の概要は準備中です。原文の説明を表示しています。
项目待办管理器（两种模式）。【收集模式】接收任意混合输入 → 解析追加到「项目待办.md」文档，不立即执行；【处理模式】读取文档 → 前置决策收集 → 按优先级逐条路由执行 → 更新状态 → 批次报告。触发词：【收集】「有几个问题先记到待办」「加到项目待办」「先存到待办文档」「记录这些待办」；【处理】「处理项目待办」「按待办文档逐条修复」「开始处理待办文档」。⚠️ 触发词必须含「待办」关键词才激活，避免与 issue-tracker / bug-fix-loop 混淆。
日本語の概要は準備中です。原文の説明を表示しています。
Download the actual PDF binary from bot-gated sites (taxpolicycenter.org, urban.org, SSRN-hosted mirrors, think-tank/publisher sites) via the Wayback Machine id_ URL form. Use when: (1) curl/WebFetch of a .pdf URL returns HTML instead of a PDF even with a browser User-Agent, (2) pypdf fails with "invalid pdf header: b'<!DOC'" or "EOF marker not found" on a freshly downloaded file, (3) Firecrawl can parse the PDF to markdown but you need the original file on disk (e.g., filing a reference copy).
日本語の概要は準備中です。原文の説明を表示しています。
Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.
日本語の概要は準備中です。原文の説明を表示しています。
Unity 6 packages and services guide. Use when working with Package Manager, installing/updating packages, scoped registries, or Unity Gaming Services (Authentication, Cloud Save, Analytics, Leaderboards, Matchmaker). Covers essential packages list and version compatibility. Based on Unity 6.3 LTS documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Unity profiling patterns including ProfilerMarkers, FrameTimingManager, memory profiling, and performance budgets.
日本語の概要は準備中です。原文の説明を表示しています。
用于实现或审查前端服务端状态流程：类型化查询、请求缓存、失效、mutation、乐观更新、无限查询、预取、SSR hydration 或 API 层整合。不要用于本地 UI 状态或 Service Worker 缓存；中文触发词包括 数据获取、缓存、乐观更新。
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing or reviewing frontend server-state flows: typed queries, request caching, invalidation, mutations, optimistic updates, infinite queries, prefetch, SSR hydration, or API-layer integration. Do not use for local UI state or Service Worker caching; Chinese triggers include data fetch, cache, optimistic updates.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a First-Line Supervisor of Entertainment and Recreation Workers (camp, pool, ride crew, attractions, or activities floor) — building today's shift roster against certification/ratio requirements when call-outs hit, running a pre-shift briefing, triaging an escalated guest complaint, deciding whether a new hire is ready to sign off independent, or choosing when to consolidate or close a program area for the day.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Electrician — sizing a service panel upgrade with an NEC load calculation, troubleshooting a tripping breaker or dead circuit systematically, checking wire gauge/ampacity and voltage drop for a circuit run, resolving a code-vs-inspector interpretation dispute, or deciding when a job (aluminum wiring, knob-and-tube, undersized service) exceeds the immediate scope.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Electrical Engineer working in power systems — sizing a service or feeder from NEC demand factors, running a short-circuit study and checking breaker interrupting ratings, computing arc-flash incident energy and assigning a PPE category, checking protective-device coordination (selectivity), or reviewing a single-line diagram before construction.
日本語の概要は準備中です。原文の説明を表示しています。
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 Derrick Operator (derrickhand) — running the monkeyboard during a pipe trip, reading trip-tank volume against calculated displacement for a swab or kick signature, calculating a barite weight-up in sacks, deciding whether a volume anomaly warrants stopping the trip for a flow check, or running the mud circulating system (shakers, desander, degasser) between trips.
日本語の概要は準備中です。原文の説明を表示しています。