3,162 件 ・ 関連度順
概要と使いどころ
Build functional software prototypes and MVPs without deep technical skills by using AI agents as "developers in your pocket." Use this skill when you need to validate a new product concept, build custom back-office tools (e.g., a real estate data manager), or create high-fidelity demos to unblock engineering roadmaps.
日本語の概要は準備中です。原文の説明を表示しています。
Extract, plan, or propose implementation details at configurable depth levels (low/normal/extensive). Outputs to reference files for team discussion and handoff.
日本語の概要は準備中です。原文の説明を表示しています。
Design and implement evaluation frameworks for AI agents. Use when testing agent reasoning quality, building graders, doing error analysis, or establishing regression protection. Framework-agnostic concepts that apply to any SDK.
日本語の概要は準備中です。原文の説明を表示しています。
The harnesses a campaign keeps, read outside a run: which there are and where each came from, what each is made of and what moved from its parent, what each was measured to be, trying one on a task, the audit before a promotion and the blind review at a handover, whether a part earns its place, and changing what makes a harness or what a seat is told about one. Use when the operator asks which harness is current, what a Builder changed, whether a harness is ready to promote or hand over, to run a kept harness on a task, or to change the harness contract. Reading one run is whole-run-investigation's, wording a claim attribution-and-proof's.
日本語の概要は準備中です。原文の説明を表示しています。
Use after an Anabasis v2 comparison, checkpoint or system change, and before any sentence claims that a harness, a model or a patch improved something. States what one reading may be said to show: the identities it was made under, the counts kept apart, whether it was repeated, which part of a harness it belongs to, whether a mechanism was live in the run, and whether the measurement is valid as distinct from whether it was exploited. Ends in one fixed report.
日本語の概要は準備中です。原文の説明を表示しています。
Zip recorded Anabasis v2 runs for handover at a chosen depth (--light, --medium, --verbose). Use when the operator asks to zip, bundle, archive or send a run, a round, its log, its harness or "everything the model saw", or names a size cap. One command, three cumulative levels, any number of runs, a README, a reading guide and a MANIFEST inside every zip.
日本語の概要は準備中です。原文の説明を表示しています。
Hand a question about Anabasis v2 to an outside Oracle model as one task document and one zip. The Oracle reads GitHub; the zip carries what it cannot fetch: campaign logs and kept harnesses through `bun run runs zip`, a reader's output, predictions with how each resolved, patches for commits never pushed. Use when the operator asks to prepare an Oracle question, a report request, a problem statement or a second opinion on a run, a reading or a design, or to send the latest runs to an outside model. Produces local files; uploading is the operator's.
日本語の概要は準備中です。原文の説明を表示しています。
Detect, triage, de-duplicate, and raise compiler bug reports when an agent encounters a likely compiler defect during implementation, review, testing, or issue work. Use when a task surfaces an ICE, panic, wrong accept/reject behavior, miscompile, lowering/emission bug, diagnostic bug, formatter/LSP/frontend drift, or other likely compiler/tooling defect; pause current work, minimize the repro, decide whether the bug blocks the task or has a valid workaround, check whether it is already reported, and then use create-github-issue to raise the bug.
日本語の概要は準備中です。原文の説明を表示しています。
Query and manage Sentry error-tracking data — list and search issues, drill into events and stack traces, inspect projects and releases, resolve/ignore issues, and pull stats. Use this whenever the user mentions a Sentry issue, crash, error group, or exception; pastes a sentry.io or self-hosted Sentry URL; asks "why is this erroring", "how many times has this happened", "what's the top error in {project}", "resolve this issue", or wants a Sentry-based digest — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
日本語の概要は準備中です。原文の説明を表示しています。
Find quotes for a set of topic keywords and place them into a 2x2 matrix, spanned by the presence of an author/origin and by the literal containment of a keyword, optionally grounded in Internet/Web facts and optionally widened to the conceptual neighborhood of the topic. Use when the user wants "quotes", "sayings", "aphorisms", or "citations" on a topic.
日本語の概要は準備中です。原文の説明を表示しています。
Learn unfamiliar technologies used in a repo by studying how the repo actually uses them. Finds patterns, explains concepts in context, and points to examples in the codebase. Use when a repo uses frameworks, languages, or patterns you haven't worked with before. Not for mapping a repo's architecture or domain language. Use oss-explore-repo for that.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate whether an OSS repo is worth long-term investment before committing time. Assesses project health, governance, community, bus factor, and trajectory. Use when deciding whether to contribute to a specific repo, choosing between multiple repos, or evaluating a project's sustainability. Not for checking if a repo accepts contributions — use oss-find-issue for that.
日本語の概要は準備中です。原文の説明を表示しています。
Use whenever creating, renaming, or editing any file under docs/ in this repo, or when asked to compile/build the book PDF. Enforces the exact .mdx frontmatter, ID scheme, and heading-depth rules required by the go-pretty-pdf tool (https://github.com/sazardev/go-pretty-pdf) so the whole book keeps compiling.
日本語の概要は準備中です。原文の説明を表示しています。
Interactive workshop that builds a monthly rolling editorial calendar using MKT1 methodology. Walks through Perceptions, content pillars, themes, and capacity to produce a 4-week detailed plan plus 3-month roadmap. Designed to be re-run monthly.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a YouTube video idea into a designer-ready thumbnail brief: focal subject, face and emotion, a text overlay of 4 words or fewer that the title does not repeat, contrast and composition, and 2 to 3 A/B concepts for Test and Compare. Built on 2026 principles (one focal point, legible at 120 pixels, complements the title). Outputs the brief plus the Publora attach step (the image upload itself is out of band). Use to plan a thumbnail. Not for title words (use yt-title-optimizer).
日本語の概要は準備中です。原文の説明を表示しています。
Build a Gumroad-ready digital product from scratch — ebook, card deck, playbook, Notion template, or flipbook. Walks from concept → content outline → design brief → per-item markdown → images → multi-format build (PDF, HTML flipbook, Notion, card deck) → Gumroad sales page + email blast + launch assets. Use when "make a digital product", "build an ebook", "create a playbook", "card deck", "notion template product", "gumroad product", "make a pdf to sell", or any request to ship a sellable information product.
日本語の概要は準備中です。原文の説明を表示しています。
Build email nurture flows using lifecycle marketing + perception engineering frameworks. Generates subject lines, body copy, and send timing.
日本語の概要は準備中です。原文の説明を表示しています。
Produce complete landing page copy using perception engineering and conversion frameworks. Generates hero section, value props, social proof blocks, objection handlers, and CTA — all scored against quality gates. Use when "landing page", "sales page", "LP copy", "write a landing page", "hero section", "conversion page", "signup page", or any request to produce persuasive page copy that converts visitors.
日本語の概要は準備中です。原文の説明を表示しています。
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>".
日本語の概要は準備中です。原文の説明を表示しています。
Produce customer case studies from interviews or data — Problem, Solution, Results structure with perception engineering and quality gates. Use when "case study", "customer story", "testimonial", "success story", "client results", or any request to document a customer win.
日本語の概要は準備中です。原文の説明を表示しています。
Generate creative direction for ad campaigns — visual concepts, copy variants, video scripts, image specifications, and A/B test matrices. Platform-aware with format specs.
日本語の概要は準備中です。原文の説明を表示しています。
Icarus Figures produces publication-grade figures for scientific papers — reproducible matplotlib/seaborn data figures and original TikZ method/framework/architecture figures, held to a four-axis quality bar (depth · elegance · unimpeachable · visible-gap) and exported as editable PDF+PNG+SVG with a runnable critique gate. Use this whenever a figure is destined for a paper, journal, conference submission, thesis, or report — making a plot/chart publication- or journal-ready, building a method/architecture/framework diagram or 技术路线图 (the hero figure a paper opens with), a schematic or workflow figure, or cleaning up a matplotlib/seaborn/TikZ figure that currently looks like a homework plot. Trigger even when the user never says "publication": if the figure goes into a written scientific document, this skill applies.
日本語の概要は準備中です。原文の説明を表示しています。
弗洛伊德.skill：给AI做心理分析的认知调优系统。基于Anthropic AI心理学研究（Persona Selection Model、全局工作空间/J-lens、Emotion Concepts、Introspective Awareness等7篇论文）。 两种模式：(1)执行增强——处理复杂任务前给AI做「认知准备」，像心理咨询师让来访者进入最佳状态；(2)诊断优化——用精神分析手法揭示prompt/skill/系统提示的身份冲突、规则堆砌、隐含矛盾等深层毛病，并重写。 当用户提到"优化表现"、"调优"、"输出不够好"、"风格不稳定"、"persona"、"认知配置"、"优化prompt"、"优化skill"、"弗洛伊德"、"心理分析"、"给AI看心理医生"、"给prompt做体检"时使用。 当用户开始重要/复杂任务但方向不明确、觉得之前的输出质量不够好、或想理解为什么某个prompt/skill有效或无效时，也应主动考虑使用。 即使用户只是说"帮我想想怎么做更好"、"这个结果不对味"、"为什么效果不好"也应触发。
日本語の概要は準備中です。原文の説明を表示しています。
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Kerberos, WinRM, SMB, RDP, Windows credential material, replayable tickets, delegation edges, and host-to-host pivot chains. Use when the user asks to replay Kerberos material, trace a WinRM, SMB, or RDP pivot, understand host-to-host privilege movement, or prove which Windows service accepted a credential or ticket. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
日本語の概要は準備中です。原文の説明を表示しています。