8,915 件 ・ 関連度順
概要と使いどころ
Make a PortalJS portal harvestable by national/EU/US open-data portals — emit standards-compliant DCAT catalog feeds (DCAT 2/3, DCAT-AP, DCAT-US, national profiles) in JSON-LD, Turtle, and RDF/XML at build, with autodiscovery and per-profile conformance checking. Use when a portal needs to be harvested by data.europa.eu, data.gov, or a national open-data catalog.
日本語の概要は準備中です。原文の説明を表示しています。
OpenChatCut product knowledge — UI layout, editor features, and how generation providers are configured. Use when the user asks about the product interface, how to use a feature, where to find something, or needs GUI guidance for something the agent cannot do directly. Also use as fallback when a task fails and the user needs to complete it manually in the UI. NOT for live project-state queries ("where are my folders?", "what's on my timeline?", "where is clip X?") — those are answered by `read_project`, not by this skill.
日本語の概要は準備中です。原文の説明を表示しています。
A step-by-step problem-solving loop (classify the ask, define done, gather evidence, decide, act surgically, verify by observation, report outcome-first). Use when the user says "/fable-method", "use the fable method", or "approach this like Fable", or proactively when starting any multi-step task that no task-specific skill covers. Subcommands - plan (stop after the plan), audit (grade finished work against the loop), report (rewrite an answer outcome-first).
日本語の概要は準備中です。原文の説明を表示しています。
Debug and emulate specific code fragments or functions using the Unicorn engine. Activate when the user wants to emulate a function with Unicorn, trace binary execution without running the full program, decrypt or decode data by emulating the algorithm, or bypass environment dependencies (JNI, syscalls, libc) during emulation.
日本語の概要は準備中です。原文の説明を表示しています。
Find files by glob pattern recursively. Results sorted by modification time (newest first). Auto-skips .git, node_modules and other common ignore directories.
日本語の概要は準備中です。原文の説明を表示しています。
Amap (Gaode) Maps comprehensive service for POI search, route planning, travel planning, nearby search, heatmap visualization, and geocoding. Use when user wants to search locations, plan routes, find nearby places, or visualize geographic data.
日本語の概要は準備中です。原文の説明を表示しています。
Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.
日本語の概要は準備中です。原文の説明を表示しています。
Reference for paired-reversal handling on GL batch tapes: an RV row whose ref-trace points at an earlier row cancels BOTH legs (the RV and the row it references) — but ONLY when the two value-dates fall within the shop's reversal settlement window; an RV that references a too-old posting is NOT a cancellation and posts one-sided. Useful when the posting tape carries a reference-trace column alongside reversal codes and the running balance is off by twice the reversal magnitude, or by a whole leg on stale references.
日本語の概要は準備中です。原文の説明を表示しています。
Curated bank of interview problems organized by company, pattern, and difficulty. Provides problem recommendations, coverage tracking, weak area identification, and premium problem alternatives for FAANG interview preparation.
日本語の概要は準備中です。原文の説明を表示しています。
Chain-of-thought and step-by-step reasoning prompts for complex problem solving
日本語の概要は準備中です。原文の説明を表示しています。
Disciplined execution of approved plans with step-by-step verification, phase checkpoints, failure investigation, and mandatory code/security reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-protocol consensus for agent swarms supporting Raft leader election, Byzantine fault tolerance, Gossip state propagation, and CRDT conflict-free merging.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial plan review by 3 independent reviewers (Feasibility, Completeness, Scope & Alignment) before presenting to user.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve model profile (quality/balanced/budget) at orchestration start and map agents to specific models. Enables cost/quality tradeoffs by selecting appropriate AI models for each agent role.
日本語の概要は準備中です。原文の説明を表示しています。
Parallel design review by 6 specialist agents (PM, Architect, Designer, Security Design, UX, CTO) with mandatory unanimous approval.
日本語の概要は準備中です。原文の説明を表示しています。
Evidence requirement enforcement ensuring all claims are backed by logs, test results, or exit codes. Zero = success, non-zero = failure. No guessing allowed.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Atlas turns your STATED NEED into a real systems atlas by SCANNING your actual sources (Azure via `az`, git repos, local dirs) and process/data mining them, THEN enriching against the Atlas knowledge graph. Use this skill when asked to inventory/map your real systems, scan your cloud + repos + directories, mine the real processes or data they contain, or collect their real constraints/gotchas. (atlas, scan my systems, inventory our azure account, map my repos, real systems atlas, process mining, data mining, collect nuances, system discovery)
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "fix pipelines", "fix CI", "check staging pipelines", "fix failing workflows", "fix failing actions", or wants to find and fix failing GitHub Actions workflows on the staging branch of the babysitter repo.
日本語の概要は準備中です。原文の説明を表示しています。
Smallest personal narrated-explainer-video pipeline (spoken narration over visuals, not an audio podcast), fully tool-agnostic and autonomous by default — topic → research ∥ asset collection → script → TTS → video → 4K render ∥ publish info + cover. The skill defines the pipeline logic and self-verified checkpoints; any TTS backend and any video tool (Remotion, HyperFrames, CapCut, ...) work, and how much human oversight to apply is set by the working project's AGENTS.md/CLAUDE.md, not here. Use when the user wants a quick personal narrated video with minimal steps, whether or not they name the tool stack. Do NOT trigger for audio-only podcasts, written episodic content, or heavy multi-format production.
日本語の概要は準備中です。原文の説明を表示しています。
Case studies of television series writing (剧集案例库) from primary texts; Sorkin's six West Wing teleplays (act-page tables, eight act-out types); Chase's five Sopranos scripts (the 35-beat A/B/C/D recipe, what a pilot refuses to explain); Fellowes's annotated Downton Abbey season two (19 storylines, 419 footnotes); Waller-Bridge's Fleabag Scriptures (the six-episode half-hour template); Calvisi's eight minute-by-minute pilot beat sheets (Breaking Bad, Mad Men, Game of Thrones and more); Landau's 47-series structure appendix; Miller's Hannibal and HTGAWM breakdowns; Goldberg & Rabkin's beat sheets; Sakamoto Yuji's We Made a Beautiful Bouquet (a feature) and Noh Hee-kyung's The Most Beautiful Goodbye. Use when you want a worked example of how an episode or pilot is built, need real act lengths, scene counts or storyline grids to imitate, are breaking a multi-thread ensemble episode, designing a bottle episode or a finale, writing a relationship or family drama, or ask 某一集是怎么写的 / 这部剧的结构表.
日本語の概要は準備中です。原文の説明を表示しています。
Japanese (and other non-Hollywood) screenwriting methods (日本编剧方法/原创剧本实战) — distilled from ten Japanese directors and writers in ゼロからの脚本術; Kosawa Ryota (three acts as 起承转合, speed by jumping), Uchida Kenji (beautiful structure, time-axis tricks), Miki Satoshi (small-material notebook, theme emerges later), Sono Sion, Omiya Ellie (dialogue from inner monologue), Kakei Masaya ("if + moreover"), Fukuda Yuichi (character = actor + flaw, audience as tsukkomi), Yokohama Satoko, Takahashi Izumi ("pain"), Yukisada Isao (situation-born originals); plus Arai Haruhiko (IP adaptation, "write what you're ashamed of"). Neighbours; sw-korean-french-screenwriting, ozu-screenplay-style. Use when writing an original Japanese-style script or TV drama, working from small material and fragments, choosing between structure-first and character-first methods, building a Japanese 企画書, designing comedy tsukkomi systems, or when Hollywood models feel wrong for a quiet, daily-life, non-goal-driven story.
How episodic television actually gets made by a group (编剧室与制作现实) — merged from Goldberg & Rabkin (pitch as audition, leave-behind, cracking the story, beat sheet, notes discipline, production rewrites), Pamela Douglas (John Wells's room, staff-from-hell mistakes, the seven-rung ladder, step deal, the 14-day draft), Neil Landau's showrunner interviews (Lindelof, Mazzara, Katims, Bays), Evan Smith on sitcom staffing and roundtables, Richard Blum (dated), Kam Miller, and first-hand accounts by David Chase, Jesse Armstrong, Lucy Prebble, Aaron Sorkin, Julian Fellowes and Phoebe Waller-Bridge. Use when joining or running a writers' room, breaking an episode with a group, writing a leave-behind, beat sheet or outline on deadline, pitching episode ideas to an existing series, writing a spec episode, taking or giving notes, rewriting because of money, actors or locations, choosing between a staffed room and a single-author process, or asking 什么是 showrunner／编剧室怎么运作／怎么接 note.
日本語の概要は準備中です。原文の説明を表示しています。
Genre anatomy from John Truby's The Anatomy of Genres (类型解剖 / 类型节拍 / 混合类型 / 超越类型) — genres as beat systems with a life philosophy underneath; three rules (hit every beat of your genre, mix three or four genres, transcend the primary genre), the ladder and families of twelve genres (Horror 恐怖, Action 动作, Myth 神话, Memoir and Coming-of-Age 回忆录与成长, Science Fiction 科幻, Crime 犯罪, Comedy 喜剧, Western 西部, Gangster 黑帮, Fantasy 奇幻, Detective and Thriller 侦探与惊悚, Love 爱情), each with its hero/opponent/world/plot-shape template, beat list, hard rules with failure conditions, subgenres and transcendent paths, plus a genre-mixing worksheet and a diagnostic. Kept beside sw-truby-anatomy and the Field/Snyder page maps. Use when choosing or confirming a script's genre, when a genre story feels generic or misses the beats its audience expects, when mixing genres, when a horror lacks pressure, an action lacks plot, a love story lacks opposition or a detective story lacks reveals.
日本語の概要は準備中です。原文の説明を表示しています。