「bli」の検索結果

Use when EZ_math_model coder or packaging fails repeatedly with the same error and needs root-cause analysis instead of another blind retry.

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

Report a problem with the open-pr plugin itself, or ask for a change, on its public issue tracker. Use when a run of one of its commands left something to say. Takes no URL.

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

Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation

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

Gather and persist project design context such as audience, brand personality, UX goals, and implementation defaults for future better-web-ui work. Use when starting a project, defining UI direction, or establishing reusable design guidance before other better-web-ui skills.

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

Build or improve a UI testing strategy covering visual regression, interaction testing, and accessibility assertions. Use when the user asks to add tests, set up testing, fix flaky tests, improve test coverage, validate UI behavior, catch visual bugs, or establish confidence in shipping frontend changes.

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

Guide for working with Wave Terminal's WPS (Wave PubSub) event system. Use when implementing new event types, publishing events, subscribing to events, or adding asynchronous communication between components.

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

Guide for creating WaveEnv narrowings in Wave Terminal. Use when writing a named subset type of WaveEnv for a component tree, documenting environmental dependencies, or enabling mock environments for preview/test server usage.

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

Use when ingesting text samples to extract quantitative writing style metrics. Produces a structured JSON style profile with vocabulary patterns, sentence structure, tone markers, and formatting preferences. Invoke before voice-clone-generator to establish style constraints.

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

Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident response procedures.

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

Workflow for repository reconnaissance and operations using GitHub CLI (gh). Optimizes token usage by using structured API queries instead of blind file fetching.

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

Use when analyzing published content (blog posts, social media, newsletters) for sentiment, structural quality, hook effectiveness, readability, topic classification, and engagement correlation. Invoke for daily post analysis, content audits, or engagement driver identification.

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

Academic research skill for Biblical Hebrew, Semitic linguistics, cuneiform studies, and comparative Ancient Near Eastern research. Provides Sefaria API for Hebrew Bible, CDLI/ORACC for cuneiform databases, and web discovery via Omnisearch, Exa, Firecrawl, and Obscura for finding scholarly sources across JSTOR, Perseus, Persée, Google Scholar, and academia.edu. Triggers on Hebrew quotes, cuneiform, Sefaria, ANE research, Minoan, search for scholarship, find papers, literature review, scholarly search, academic search, Genesis/Tehom, Ugaritic, Talmudic sources, extract from PDF, OCR academic.

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

Identify the source of an image or video frame — TV show episode, movie scene, geographic location, or original publication. This skill should be used when the user asks to identify where an image is from, trace a screenshot back to its source, geolocate a photo, find what show or movie a frame is from, or do a reverse image search. Chains Google Vision, Picarta geolocation, and Gemini in parallel with graceful degradation. Triggers on: reverse image search, identify source, what show is this, where was this taken, trace image, identify video, what movie, which episode, geolocate photo, image source.

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

Plan the UX and UI for a feature before writing code. Run a structured discovery interview, then produce a design brief (.design-context.md) that guides implementation. Establishes design direction, constraints, and strategy before any code is written. Triggers on plan the design, design brief, shape the UX, before we build, design discovery.

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

Build or update a CONTEXT.md domain glossary for the current project. Establishes shared vocabulary with term definitions, avoid-aliases, and relationships so agents use consistent, concise language. This skill should be used when starting a new project, when domain terminology is inconsistent across sessions, when the user says "build a glossary", "define our terms", "shared vocabulary", or "domain language", or when an existing CONTEXT.md needs updating after new domain concepts emerge.

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

Search and download images from 15 APIs in parallel (Openverse, Pexels, Pixabay, Met Museum, Cleveland Museum, Art Institute of Chicago, Getty Museum, NASA, Rijksmuseum, Wikimedia Commons, Unsplash, Smithsonian, Europeana, Iconify, Pollinations AI). Supports license filtering, presets (military, museum, stock), cached results, and bulk download with metadata sidecars. Triggers on find images, stock photos, public domain artwork, museum images, CC-licensed, NASA photos, icons.

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

Design human-visible, machine-readable website layers for AI assistants, RAG, and agentic search. Use this skill when the user asks for llms.txt, LLM discovery plans, visible TLDR or direct-answer blocks, source trails, entity pages, markdown alternates, AI crawler policy, topic-to-URL maps, assistant-readable public content, or LLM-friendly architecture that must preserve canonical SEO strategy without hidden bot-only facts or duplicate story bodies.

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

Map user journeys, onboarding paths, entry points, first actions, trust points, accessibility risks, and SEO/LLM handoffs for public websites without redesigning the visual system. Use this skill when the user asks how new readers, returning users, project reviewers, community members, buyers, or AI agents should move through a site and what each page must make clear before layout implementation.

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

Convert a semantic core into crawlable SEO and LLM-friendly information architecture. Use this skill when the user asks for URL structure, page taxonomy, canonical rules, hreflang groups, page roles, pillar/topic/news/article/blog/project separation, multilingual route strategy, or a durable content model such as one short brief plus one longform article. It prevents duplicate public content bodies and hands link-graph work to internal-link-graph-architect.

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

Agent Brain /brain-ship: a reviewed artifact is ready for release or publication.

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

Agent Brain /brain-review: after verification or before public/shipping decisions.

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

Builds, validates, packages, tests, and optimizes deployment-ready Skill files (SKILL.md + references/ + scripts/ + agents/) from design specifications. Three pre-build gates + 9-dimension quality gate (with D9a/b/c empirical evidence tiers) + behavioral iteration loop + automated description optimizer + blind version comparator. Use for building, reviewing, revising, testing, or optimizing Skills. Trigger on: "build this Skill," "review this Skill," "test my Skill," "optimize the description," "compare these Skill versions," "should this be a hook instead," "build a template first." Also: "my Skill doesn't activate," "my description truncates," "my SKILL.md is too long," "my Skill is overtriggering." Do NOT use when designing Skill methodology — that's design work, not packaging. Do NOT use for prompt compilation, project auditing, or prompt scoring (use rootnode-prompt-compilation, rootnode-project-audit, or rootnode-prompt-validation if available).

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

SEO & GEO content linter — validates Markdown/MDX files for AI search visibility using 92 deterministic rules (35 GEO, 32 SEO, 14 content quality, 8 technical, 3 i18n). Runs an autonomous lint-fix loop: scan content, read structured violations, fix them, re-lint until clean. Use when optimizing content for AI citations, auditing SEO compliance, checking GEO readiness, or running pre-publish content validation. Triggers on: "geo-lint", "lint content", "SEO audit", "GEO", "content optimization", "AI search", "citation readiness".

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

Prove geometric theorems using Euclidean axiomatic methods, coordinate geometry, or vector methods with rigorous step-by-step logical structure. Covers direct proof, proof by contradiction, coordinate proofs, vector proofs, and handling of special cases and degenerate configurations. Use when given a geometric statement to prove, verifying a conjecture, establishing a lemma, converting geometric intuition into a rigorous proof, or comparing the effectiveness of different proof methods.

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