「what」の検索結果

Run a premortem on any plan, launch, product, hire, strategy, or decision. Imagines it failed 6 months from now, works backward to find every reason why, then produces a revised plan. Triggers include "premortem this", "premortem my", "what could kill this", "stress test this plan", "find the blind spots", "poke holes in this", "where will this break", "am I missing anything", "what could go wrong", "future-proof this", "devil's advocate this".

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

Reflective pass over your memory — merge duplicates, fix stale facts, prune what no longer matters. Use when the user asks to clean up or review what you remember, or when memory has grown cluttered or contradictory.

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

Show one skill in full — its team record or Library folder, versions, installs, health, and its eval report when it is a team skill — as Markdown boards from the terum-skills CLI. Use when the user names a skill and asks what it is, who installed it, how it scored, or what its receipt says.

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

Search and explore an Obsidian vault through the NoteBrain CLI (semantic search, tags, backlinks, connections, hidden links, boosted retrieval). Use it whenever the user mentions their notes, knowledge base, Obsidian vault, semantic search, finding connections or unlinked notes, or asks exploratory questions like "what do I know about X", "find notes related to Y", "what connects to Z", or "summarize my notes on W" — even when they never say NoteBrain, vector search, or ChromaDB.

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

This skill should be used when the user asks "How do I...", "What is...", "How does X work in Prismatic?", "What's the best practice for...", wants to understand Prismatic concepts, features, or architecture, or needs guidance on marketplace deployment, customer connections, embedded UI, config pages, triggers, or other Prismatic product features. Search and retrieve documentation from prismatic.io/docs and reference examples from github.com/prismatic-io/examples.

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

Plan a content strategy, topic clusters, editorial roadmap, and content mix for traffic, authority, and lead generation. Use when deciding what to publish, what topics to prioritize, or how to structure a content program.

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

X/Twitter public sentiment research. Searches X for real-time perspectives, market sentiment, expert opinions, breaking news, and community discourse. Use when: user asks "what are people saying about", "X/Twitter sentiment", "check X for", "search twitter for", "what's CT saying about", or wants public opinion on a stock, sector, company, or market event.

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

Sets up safe working habits and a change log so you always know what Cowork has done to your files — and can undo anything. Use when setting up file protection guardrails, for establishing safe automation habits, during initial access configuration, when granting file permissions for the first time, or when the user says "is cowork safe", "file safety", "what if it deletes my files", "audit trail", "safety setup", "I'm nervous about file access", "how do I trust cowork with my files", "can cowork mess up my computer", "I heard someone lost files", or "how do I stay in control".

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

Teaches you how to delegate tasks to Cowork so clearly that you get exactly what you asked for — every time. Use when learning how to give better instructions, for improving your delegation technique, during early Cowork adoption when results feel off, when writing clearer task descriptions, or when the user says "how do I ask cowork to do things", "delegation tips", "better instructions", "cowork isn't doing what I want", "help me delegate", "my results are bad", "how do I give better prompts", "cowork keeps getting it wrong", "I don't know how to use this", or "how do I get good results".

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

Gathers information from multiple sources in parallel, compares what they say, flags where they agree or conflict, and delivers a clean synthesis with a confidence rating for each finding. Useful for making evidence-backed decisions, when evaluating competing claims, during due diligence on a vendor or market, and for building research briefs before strategy sessions. Use when the user says "research this", "synthesize multiple sources", "compare sources", "research report", "what does the evidence say", "gather information on", or "deep dive into".

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

Perform a reflective consolidation pass over a hyalo-managed knowledgebase directory — detecting structural issues, fixing broken links, flagging stale content, normalizing metadata, and reporting what changed. Use this skill when the user says /hyalo-tidy, "consolidate the knowledgebase", "clean up the KB", "run KB hygiene", "tidy", or "what needs attention in the knowledgebase". Also use when the user asks about knowledgebase health, broken links, orphan files, stale iterations, or metadata inconsistencies.

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

Use when assigning a confidence level to an analytical judgment, the user asks "how confident are we?" / "what is the confidence on X?", or the orchestrator's tradecraft pipeline calls for a confidence level before publishing. Provides three named levels (High, Moderate, Low) with 0-100 score ranges aligned to STIX, and the rule that confidence cannot exceed what the weakest load-bearing claim supports.

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

Use when challenging a prevailing analytical judgment, the user asks "what is the opposing case?" / "argue the other side" / "play devil's advocate", or wants an assessment stress-tested before release. Takes the team's own lead judgment and builds the strongest case that it is wrong. A contrarian technique. It does not model what an adversary would do next, which is Red Team Analysis. Formerly /red-team-analysis.

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

Use when you need to answer "which attacker techniques do our controls actually stop, and how well?", "what controls should I have for this threat?", or "what telemetry should I collect to detect it?" — joining a customer's or your own security control baseline to ATT&CK techniques using a public, versioned evidence base of 9,545 control-to-technique mappings from six sources. Produces four ranked lists (addressed strongly, addressed weakly, real gaps, and techniques no control anywhere addresses). Use for control gap analysis, security programme prioritisation, board reporting on coverage, or the Resistance Strength side of a FAIR risk assessment. Invoke after /threat-actor-profiling or /lookup-liberty91 has produced a technique list.

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

Visual context analyzer for AI agents. Provides screenshots, accessibility scans, DOM snapshots, and element descriptions for web pages. Use when you need to see what a web page looks like, analyze accessibility issues, inspect DOM structure, or get detailed element information. Triggers on requests like "take a screenshot", "check accessibility", "what does this page look like", "analyze the UI", "inspect this element", or any visual/UI analysis task.

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

When reviewing, optimizing, or inheriting an LLM agent, systematically identify what's actually load-bearing vs. cruft. Instruments usage, ablates components, and strips the agent to minimum viable form. Answers: "What can we remove without degrading quality?" The goal is the leanest agent that still works.

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

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.

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

Explain what a piece of code does — a specific file, class, or method in close detail, or a user-facing flow as a concise system overview. What it does and why, not whether it's good.

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

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

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

"Apply the Capital Asset Pricing Model (CAPM) to estimate expected returns and assess risk-return tradeoffs. Use this skill when the user needs to calculate expected return on an asset, interpret beta as systematic risk exposure, evaluate whether an investment compensates for risk, or when they ask 'what return should I expect', 'what is the risk premium', or 'how does beta affect pricing'.".

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

"Apply Theory of Constraints (TOC) to identify and manage system bottlenecks. Use this skill when the user needs to find what limits throughput, optimize a constrained process, apply the Five Focusing Steps, or implement Drum-Buffer-Rope scheduling — even if they say 'our output is stuck', 'what's the bottleneck', or 'why can't we produce more'.".

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

On-demand situational awareness — fresh git/PR snapshot plus continuation, distilled into one concrete "next action" suggestion. Use mid-session when you've lost track, after a compaction, or starting a new work block. Trigger on "where was I", "what's next", "progress", "what should I do now", "/progress".

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

Read every application.yaml in the workspace and report the state of the search — the ranked queue, what is waiting on you, what has gone quiet, and the regression of the pipeline's own predictions against actual outcomes. Writes the calibration findings back into job_search.md and preferences.yaml.

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

An adversarial job search that gets better as it goes. Set up a job-search workspace, search a careers board and score roles against the realistic applicant pool, build a resume and cover letter, review them with seven agents that return a verdict per submission channel, then write what the review finds back into the profile. Invoke with /slushpile and name what you want to do.

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