1,684 件 ・ 関連度順
概要と使いどころ
Use when adding telemetry, composing an observability surface, reviewing alerts, shipping a production feature, or diagnosing a production issue. Not for live failures, profiling, or launch runbooks.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a landed merge, release, or completed change needs its cleanup surface reconciled. Scans for stale TODOs, deprecations, unused flags, and doc gaps. Not for unrelated refactoring.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user wants agent setup graded from conversation history. Not for skill fixing: use agent-surface-forge. Not for security scanning: use skill-scanner.
日本語の概要は準備中です。原文の説明を表示しています。
Audit one bounded Proto UI deployment or publication evidence slice against an exact revision and delivery surface. Use to verify revision identity, environment result, artifacts, and observable health. Do not deploy, promote, roll back, publish, release, or change environment protection.
日本語の概要は準備中です。原文の説明を表示しています。
Trace a Proto UI change through authoritative spec lifecycle, legacy explanation, dated context, implementation, executable evidence, package surfaces, and public projections. Use before deciding scope, changing behavior, reviewing a pull request, or investigating drift.
日本語の概要は準備中です。原文の説明を表示しています。
Use when changed files need governed Odylith surfaces refreshed.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate an Odylith bug record, gather evidence, and connect it to the right governed surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Refresh governed Odylith surfaces for the current changed slice.
日本語の概要は準備中です。原文の説明を表示しています。
Fix intermittent `{:no_translation, :unicode, :latin1}` crashes in Elixir escript daemons that use length-prefixed framed IPC on stdin/stdout. Use when: (1) daemon worker crashes only on some input files, usually ones with non-ASCII bytes (kanji, cyrillic, emoji); (2) error surfaces as `Protocol error` from daemon's error branch or as garbled frame-length bytes seen by the orchestrator/client side; (3) standalone one-shot mode works fine on the same input but multi-request daemon mode fails; (4) `IO.binread(:stdio, N)` returns `{:error, {:no_translation, :unicode, :latin1}}` despite the "bin" prefix suggesting it should be encoding-agnostic. Root cause is the escript default `:standard_io` encoding — it's `:unicode`, and `IO.binread` still routes through the io_server, which translates bytes to codepoints and errors when raw binary frames contain invalid UTF-8 sequences.
日本語の概要は準備中です。原文の説明を表示しています。
Fires after fixing any non-trivial bug or regression. Asks: could the graph have caught this as a guarantee? Pairs with reflection-in-and-on-action — picks up after "earliest catchable signal" and asks the next question: was that signal expressible in graph? Triggers: (1) after any non-trivial bug fix is verified working, (2) after a regression report (something used to work, broke), (3) during step 6 (knowledge extraction) of the workflow, (4) when reflection-on-action surfaces a "would have been catchable" signal. Outcome is a triage decision (graph-reachable? rule expressible? rule sound?) and either a draft Linear issue + guarantee proposal, or a recorded "graph capability gap" note. Never auto-creates guarantees.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "test what I just changed", "/devtest", "smoke test my change", "verify my latest commit", "测一下我刚改的", "看看刚改的功能能不能跑", "跑一下登录看看", or similar requests to verify a recent code change against a running Android or iOS device. The skill reads the git diff, infers the affected UI surface, generates a focused test plan, drives the app via ui-mcp + mobile-mcp, captures logs via log-mcp, and produces a Markdown report via report-mcp.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "explore the app", "/qa", "auto-test the app", "find bugs in my app", "猴子测试", "自动探索", "随便点一下看看", "测一下全 app 看有没有崩", "smoke explore", or wants autonomous exploration of an Android or iOS app to surface crashes / ANRs / unexpected states. Drives the app via ui-mcp + mobile-mcp, tracks visited pages and clicked elements via report-mcp's state graph, captures crashes via log-mcp, and produces a Markdown report with bug list + coverage stats.
日本語の概要は準備中です。原文の説明を表示しています。
Route NowStack Mobile UI work to the right design/build skill while enforcing a clear, user-first UX bar. Use for any "build/design/redesign/polish the UI" request on the mobile app, web app, landing, or admin — when the surface or the right skill is underspecified.
日本語の概要は準備中です。原文の説明を表示しています。
Verify NowStack Mobile changes across web, iOS, Android, and Convex with real runtime evidence. Use for `/ns verify`, cross-surface regression checks, acceptance proof, or release verification.
日本語の概要は準備中です。原文の説明を表示しています。
Publish NowStack Mobile production surfaces. Use for Convex prod, web deploy, production env sync, and coordinating iOS/Android release skills.
日本語の概要は準備中です。原文の説明を表示しています。
Integrate or audit privacy-safe PostHog analytics across NowStack Mobile Expo and TanStack web surfaces. Use for event design, consent, identity, dev/prod separation, funnels, feature flags, or analytics verification.
日本語の概要は準備中です。原文の説明を表示しています。
Enhance an existing marketing plan with parallel research. Use when the agent has a draft plan (brand strategy, campaign brief, content calendar, launch plan) that needs strengthening with real data. Triggers on 'deepen this plan', 'strengthen this strategy', 'research gaps in my plan', 'make this plan better', 'this plan is too surface level', 'add research to this', 'validate this plan', 'back this up with data', or when a plan exists but lacks audience data, competitive positioning, or keyword strategy. Make sure to use this whenever someone has an EXISTING plan that feels thin or unresearched — even if they just say 'is this plan good enough?' or 'what's missing here?', they likely need deepening. This skill ENHANCES existing plans — it does not create new ones. If no plan exists, route to /brainstorm or /launch-strategy first.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for a YARA rule, "write YARA for this sample/family", or `/hash-investigation` / `/malware-analysis` surfaces a sample worth a static-content rule. Pattern-matching rules for identifying malicious files.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for a SIGMA detection rule, "write a SIGMA rule for X", or `/hash-investigation` / `/malware-analysis` surfaces behaviour worth a vendor-agnostic detection. Format spec + writing guide.
日本語の概要は準備中です。原文の説明を表示しています。
Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
日本語の概要は準備中です。原文の説明を表示しています。
MCP integration orchestrator. Use PROACTIVELY when the framework needs a new MCP-backed workflow, connector surface, or toolchain integration.
日本語の概要は準備中です。原文の説明を表示しています。
Investor And Board Communication Specialist. Use to draft monthly investor updates, quarterly board decks, and high-signal stakeholder communications that surface wins, misses, risks, and asks clearly.
日本語の概要は準備中です。原文の説明を表示しています。
Write a client update — identify what was done, what's next, and surface risks before they become surprises. End of day, start of day, or end of week.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Bhaskar's critical realism to analyze phenomena through three ontological domains (real, actual, empirical), identify generative causal mechanisms via retroduction, and examine structure-agency interplay. Use this skill when the user needs to go beyond surface correlations to underlying causes, design research that distinguishes mechanisms from events from experiences, or when they ask 'what causes this beyond the observed pattern', 'what structures enable or constrain this behavior', or 'how do I move from correlation to causal explanation'.".
日本語の概要は準備中です。原文の説明を表示しています。