4,507 件 ・ 関連度順
概要と使いどころ
Alibaba Cloud SLS (Simple Log Service) provider for obz. Supports metrics (PromQL), logs (SLS Query), and traces across project/store pairs. Requires AccessKey auth and provider-specific flags like --project, --logstore, --metricstore, and --trace-logstore. This skill should be used when the user mentions "SLS", "Alibaba Cloud", "obz -p sls", or needs to configure SLS provider instances.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the full one-person company workflow across all OPC skills. Use when Codex needs to start, continue, or review the complete 一人企业方法论流程, reading state files, detecting stage, selecting interaction mode, coordinating team members, and managing the session lifecycle.
日本語の概要は準備中です。原文の説明を表示しています。
Inventory all founder resources across 8 categories for a one-person company. Use when Codex needs to systematically confirm what resources the founder has — experience, network, skills, relationships, channels, assets, time/money constraints, hard limits — by first doing a broad scan of each category, then drilling into specifics (distribution, usable portions, how to use, cost of use), and producing a confirmed detailed resource inventory written to `opc-doc/`. Does NOT analyze directions, preferences, suitability, or risk tolerance — those belong to downstream skills.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate a full Galyarder Framework release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss versioning.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the founder needs a single orchestrator to route work across multiple departments, synthesize specialist output, or translate an ambiguous business request into a concrete execution path.
日本語の概要は準備中です。原文の説明を表示しています。
Creates demand generation campaigns, optimizes paid ad spend across LinkedIn, Google, and Meta, develops SEO strategies, and structures partnership programs for Series A+ startups scaling internationally. Use when planning marketing strategy, growth marketing, advertising campaigns, PPC optimization, lead generation, pipeline generation, or startup marketing budgets. Covers multi-channel acquisition (Google Ads, LinkedIn Ads, Meta Ads), CAC analysis, MQL/SQL workflows, attribution modeling, technical SEO, and co-marketing partnerships for hybrid PLG/Sales-Led motions in EU/US/Canada markets.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a release needs launch framing, sequencing, channel choices, and rollout logic across product, growth, and support.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the work needs analytics architecture, event planning, KPI design, attribution boundaries, or instrumentation review across product and growth.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes campaign performance with multi-touch attribution, funnel conversion analysis, and ROI calculation for marketing optimization. Use when analyzing marketing campaigns, ad performance, attribution models, conversion rates, or calculating marketing ROI, ROAS, CPA, and campaign metrics across channels.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-step content production pipeline that takes a topic or brief and produces a full blog post, email newsletter excerpt, and three social posts — all in your voice. Useful for building a content batch, when repurposing a core idea across formats, during content sprint sessions, and for turning expertise into publishable material. Use when the user says "create content", "content pipeline", "blog to social", "write and repurpose", "content engine", or "create a blog post and social posts".
日本語の概要は準備中です。原文の説明を表示しています。
Audits your Cowork setup across five categories, scores each one, and gives you a prioritized improvement plan. For reviewing how well you are using Cowork, when optimizing your workspace configuration, or during a quarterly productivity review. Use when the user says "health check", "am I using cowork right", "optimize my setup", "cowork audit", "what am I missing", "is my setup good", or "how do I get more out of cowork".
日本語の概要は準備中です。原文の説明を表示しています。
Sets up a file-based memory system so Cowork always knows who you are, how you work, and where your projects stand. For eliminating repetitive re-introductions at session start, when building persistent context across multiple projects, or during initial Cowork onboarding. Use when the user says "claude doesn't remember me", "memory system", "persistent context", "why does it forget", "remember my preferences", "I keep re-explaining myself", or "how do I make Claude remember things".
日本語の概要は準備中です。原文の説明を表示しています。
Use when documenting a named campaign across time and victims, the user asks to start or update a campaign record, or another skill identified a multi-incident cluster that warrants formal tracking. Provides the template (timeline, attribution, victimology, attack chain, Diamond Model mapping, IOC clusters) and the lifecycle from active to historical.
日本語の概要は準備中です。原文の説明を表示しています。
Use when assessing the maturity of a CTI programme, the user asks "how mature is our CTI?" / "what should we improve next?", or wants a benchmark against the five-level model across six dimensions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when phrasing a forward-looking statement, the user asks "how likely is X?" / "what's the likelihood?", or the tradecraft pipeline applies a probability yardstick to a finished product. Standardised likelihood language across all products.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to check whether an organisation/domain has been claimed by a ransomware group, profile a specific ransomware group (TTPs, leak-site infra, IOCs, YARA), or aggregate ransomware victim claims by country/sector/timeframe. Backed by ransomware.live's leak-site scrapes — 27k+ victims across 330+ groups. Commonly invoked by /domain-investigation, /ransomware-ecosystem, /threat-actor-profiling, and detection-engineering workflows. Reads $RANSOMWARE_LIVE.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks about the CTI Hyperloop framework, the intelligence lifecycle as a high-tempo loop, or how to map intelligence work across strategic / operational / tactical levels with bidirectional feedback. Liberty91's operational doctrine.
日本語の概要は準備中です。原文の説明を表示しています。
Indicator pivoting methodology — how to use one known indicator to discover related infrastructure across the IOC graph. Decision tree by indicator type with concrete `/lookup-*` commands per pivot, a worked multi-hop example, pivot-quality scoring, and routing into the rigor pipeline. Use when the user asks "what else is connected to this IP / domain / hash / cert / actor?", needs to expand a single seed IOC into a campaign cluster, or wants the canonical reference for graph-walking IOCs.
日本語の概要は準備中です。原文の説明を表示しています。
Reasoning data lost across agent steps and missing low-confidence fallback Keywords: sqlite, triangulation, escalation, confidence
日本語の概要は準備中です。原文の説明を表示しています。
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.
日本語の概要は準備中です。原文の説明を表示しています。
Expert error coordinator specializing in distributed error handling, failure recovery, and system resilience. Masters error correlation, cascade prevention, and automated recovery strategies across multi-agent systems with focus on minimizing impact and learning from failures.
日本語の概要は準備中です。原文の説明を表示しています。
Perpetual autonomous work loop for Claude Code — no end condition, no memory regression, no context overfill. Maintains a persistent ledger across all sessions.
日本語の概要は準備中です。原文の説明を表示しています。
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks
日本語の概要は準備中です。原文の説明を表示しています。
Check agent configuration coverage across hierarchy levels and phases. Use to ensure complete agent system coverage.
日本語の概要は準備中です。原文の説明を表示しています。