4,744 件 ・ 関連度順
概要と使いどころ
Match a free-text intent against the accumulated help of all ASE skills, generate all adequately fitting `/ase:ase-xxx-xxx` commands -- ranked best-fitting first, each with concrete options and arguments -- and let the user execute one of them, refine the intent, or cancel. Use when the user knows what they want but not which skill or flags realize it, or mentions "intent" or requests "help".
日本語の概要は準備中です。原文の説明を表示しています。
Self-test the LLM's ability to execute ASE's core interpreter machinery (control flow, XML placeholders, regex matching, arithmetic) and report an overall compatibility rating. Use when the user wants to check how well the current model/harness is compatible with ASE, or asks to "test ASE compatibility" or "check ASE compatibility".
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute your second and third contributions to become a regular contributor. Covers relationship building, progressive complexity escalation, and community presence. Use when your first PR was merged and you want to keep contributing, when transitioning from one-off contributor to regular, or when planning a sustained OSS involvement. Not for your first contribution — use the oss-find-issue → oss-contribute chain for that.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing the structure, ordering, coherence, and narrative flow of the book as a whole or across chapters. Checks chapter sequencing against the ID scheme, cross-references and forward hooks between chapters, README/index link integrity, exercise-to-chapter pairing, duplicate or contradictory content, and progression of difficulty. Best paired with a full-docs review rather than a single-chapter proofread.
日本語の概要は準備中です。原文の説明を表示しています。
Use when generating weekly GTM performance reports, summarizing pipeline activity, reviewing outreach metrics, or creating executive updates. Triggers: 'weekly report', 'GTM report', 'pipeline review', 'weekly update', 'outreach summary', 'Friday report'.
日本語の概要は準備中です。原文の説明を表示しています。
Automate on-target verification of a program's logic by driving its RTT console with rttsh - write Lua scripts that exercise commands and assert responses, output and timing on real hardware. Use when asked to verify target-side behavior on board, build board-level checks for firmware features, or automate hardware test runs.
日本語の概要は準備中です。原文の説明を表示しています。
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
Partnership and co-marketing campaign planner — partner selection criteria, joint content strategy, cross-promotion plans, and co-branded assets. Use when "partnership", "co-marketing", "partner program", "cross-promotion", "joint venture", "co-branded", "partner campaign", or any request to plan or execute a marketing partnership.
日本語の概要は準備中です。原文の説明を表示しています。
Surface the right marketing checklist for any task. Covers content, SEO, ads, email, press, landing pages, launches, and technical audits. 17+ checklists indexed by task type.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute account-based marketing campaigns for enterprise targets — account selection, personalized outreach, multi-channel touch sequences, and deal acceleration. Use when "ABM", "account-based marketing", "enterprise marketing", "target accounts", "named accounts", "enterprise outreach", "key accounts", or any request to build personalized campaigns for specific companies.
日本語の概要は準備中です。原文の説明を表示しています。
Client-ready HTML presentation builder for Kai audit and report folders. Converts weekly audits, monthly audits, marketing reports, scorecards, findings, data-source notes, and action plans into a polished single-file HTML deck with sourced metrics, executive slides, speaker notes, and delivery-ready styling. Use when "HTML presentation", "HTML deck", "client-ready audit deck", "turn this audit into slides", "present the weekly audit", "present the monthly audit", or any request to deliver Kai reports as HTML slides.
日本語の概要は準備中です。原文の説明を表示しています。
Run a marketing objective to completion over hours, days, or weeks — not a single deliverable. Takes a business outcome ("40 qualified demos a month from organic by Q4", "cut blended CAC below $90", "launch the product in September"), decomposes it into work items with declared ECO floors, executes them across context windows with resumable state, and stops only when an independent gate returns SHIPPED or CLOSED. Use when the request is an outcome rather than an artifact, when work must continue in the background or across sessions, or when the user says "goal", "run this until", "keep working on", "autonomous", "long-running", "over the next month", or "get us to <number>".
日本語の概要は準備中です。原文の説明を表示しています。
Work with a running QDash instance through qdash-client and saved local profiles. Use when an agent needs to inspect chips, metrics, task results, calibration data, provenance, issues, flows, executions, project files, project-scoped QDash API data, or OpenAPI endpoints from QDash using qdash-client, ~/.config/qdash/config.ini, XDG_CONFIG_HOME/qdash/config.ini, QDASH_* environment variables, or a local oqtopus-team/qdash checkout.
日本語の概要は準備中です。原文の説明を表示しています。
Go-to-market engineering for the Yupcha portfolio (OmniVoice-Studio, the Clay-alternative in this repo, ResuBird). A closed set of executable verbs — research, audit, draft, measure, prepare, publish, escalate — each with a typed contract, required sources, and a risk tier. Use when: (1) researching ICP/competitors/channels/prior art, (2) auditing our own properties for what's actually broken (dead pricing pages, 404ing clone URLs, unfilled demos, licence detection, watermark coverage), (3) drafting docs/comparison pages/release notes/launch copy, (4) measuring real numbers against GOAL.md, (5) preparing a Show HN or a listing up to the send button, (6) any question about whether a GTM action is allowed. Triggers: 'gtm', 'go to market', 'launch', 'show hn', 'growth', 'marketing', 'positioning', 'icp', 'competitors', 'outreach', 'cold email', 'audit our', 'is it ok to', 'can we post', 'promote'.
日本語の概要は準備中です。原文の説明を表示しています。
Trace Odoo execution flow from an entry point through controllers, button actions, cron jobs, model methods, overrides, computes, onchanges, constraints, database operations, security checks, and side effects. Use before implementation, during debugging, impact analysis, performance review, or code review when behavior depends on Odoo call chains.
日本語の概要は準備中です。原文の説明を表示しています。
Odoo 20 development knowledge base covering actions, controllers, data files, API decorators, SQL constraints, indexes, modules, fields, manifests, mixins, ORM methods, migrations, OWL components, performance, QWeb reports, security, testing, transactions, translations, and XML views. Use when writing, reviewing, or debugging Odoo 20 Python, XML, or JavaScript code, creating or modifying modules, fixing performance issues, or looking up Odoo 20 API patterns and best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Odoo 19 development knowledge base covering actions, controllers, data files, API decorators, SQL constraints, indexes, modules, fields, manifests, mixins, ORM methods, migrations, OWL components, performance, QWeb reports, security, testing, transactions, translations, and XML views. Use when writing, reviewing, or debugging Odoo 19 Python, XML, or JavaScript code, creating or modifying modules, fixing performance issues, or looking up Odoo 19 API patterns and best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for forced-auth coercion, relay chains, target selection, NTLM or related acceptance paths, and coercion-to-privilege transitions. Use when the user asks to trace a coercion primitive, follow a relay path, analyze forced authentication, determine which service accepts relayed auth, or connect a coercion step to resulting privilege, enrollment, or code execution. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
日本語の概要は準備中です。原文の説明を表示しています。
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for queues, async workers, cron jobs, delayed tasks, retry behavior, worker-only config drift, and payload-to-side-effect chains. Use when the user asks to trace a queue payload, inspect async job execution, explain worker-only behavior, follow retries or dead-letter handling, or connect an enqueued item to a later file, cache, email, or privilege-bearing side effect. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
日本語の概要は準備中です。原文の説明を表示しています。
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for CI/CD, registry, dependency drift, artifact provenance, image build, release pipeline, and runtime consumer challenges. Use when the user asks to trace dependency drift, registry pulls, malicious packages, build or release tampering, CI execution, artifact signing, or which shipped artifact the runtime actually consumes. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
日本語の概要は準備中です。原文の説明を表示しています。
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for browser cookies, localStorage, sessionStorage, IndexedDB, Cache Storage, service workers, offline caches, and client-side session persistence. Use when the user asks to inspect browser state, replay cached auth or session behavior, explain why a page behaves differently after load, or trace how stored client state changes requests, rendering, or access. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
日本語の概要は準備中です。原文の説明を表示しています。
Execute comprehensive client-side injection vulnerability assessments on web applications to identify XSS and HTML injection flaws, demonstrate exploitation techniques for session hijacking and credential theft, and validate input sanitization and output encoding mechanisms.
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this before any creative work or multi-step task. Explores intent and writes execution-ready plans before coding.
日本語の概要は準備中です。原文の説明を表示しています。
Progressive Disclosure skill index — efficient skill loading in 3 layers. Layer 1 (index, ~100 tokens) always loaded. Layer 2 (summary, ~300 tokens) loaded on context need. Layer 3 (full SKILL.md) loaded on execution only.
日本語の概要は準備中です。原文の説明を表示しています。