「used」の検索結果

Used to invoke the PXMeter tool for rigorous quality assessment of biomolecular structure prediction models (e.g., proteins, nucleic acids, small molecules). This skill covers single-sample CIF evaluations and large-scale dataset benchmarks, providing rich result parsing support. Trigger this skill when the user asks to "run PXMeter", "compare PDB/CIF evaluation results of different tools", "check benchmark scores", or asks "how accurate is the structure generated by the model".

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

Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does this site use', 'how is this built'. Also for single elements: 'copy this navbar', 'recreate this illustration', 'give me a prompt to regenerate this graphic' — element mode outputs a focused element.md, with token-grounded image-model prompts when the element is visual art. If the user brings any visual source and wants to understand it at a design level — this skill should activate.

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

Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).

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

Reusable writing-style contract for agent outputs (reports, ARCH docs, verdicts, threat models). Forces direct prose with concrete evidence, no marketing voice, no hedge words. The single most-referenced skill across the pipeline — used by 28 agents.

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

Structured idea generation + multi-LLM debate for the product-owner stage. Diverge (generate genuinely different bets), debate (a 4-persona panel on 4 models argues over 2 rounds), converge (synthesize a recommendation). Used by product-owner before architect; available to architect for design-space exploration.

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

This skill should be used when a session's job is to DRIVE OPEN PRs TO MERGE rather than to write new code — "close out the open PRs", "review and fix the open PRs", "what's blocking our PRs", "which PRs are mergeable". It owns the In Review column: it reads each PR's gate status, verifies and fixes review findings on PRs OTHER sessions built, replies in-thread, and stops at the merge gate for the user's per-PR approval. Do NOT load it for building a feature and opening its PR — that is a build session (`genesis-development`).

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

This skill should be used when the user asks to "write a LinkedIn message", "draft a connection request", "help me reach out to someone on LinkedIn", "write an InMail", "message this person", or when the prospect-researcher skill identifies a high-value contact worth reaching out to. Also triggered by "how should I approach [person/company]" in a LinkedIn context.

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

This skill should be used when the user asks to "plan my LinkedIn content", "create a content calendar", "what should I post about this week", "plan my posting schedule", or when Genesis proactively suggests a weekly content plan during surplus compute. Also triggered by "I need post ideas" or "I don't know what to write about".

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

This skill should be used when the user asks to "optimize my LinkedIn profile", "update my LinkedIn headline", "rewrite my LinkedIn summary", "improve my LinkedIn about section", or when Genesis identifies that the user's profile doesn't align with their current goals or target audience.

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

This skill should be used when the user asks to "research this company", "look into this person", "find the best angle for reaching out to", "who should I contact at [company]", "what does [company] care about", or when preparing outreach to a specific target. Also triggered by "help me prepare for an interview with [company]" or "I want to apply to [company]". Combines lead-generation intelligence with LinkedIn-specific approach planning.

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

This skill should be used when the user asks to "write a comment for this LinkedIn post", "help me respond to this post", "what should I comment on this", "craft a LinkedIn comment", or when Genesis identifies high-value posts in the user's network worth engaging with. Also triggered by "how should I engage on LinkedIn" or "help me be more visible on LinkedIn".

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

This skill should be used when the user asks to "write a hook for my post", "give me opening lines", "help me start this LinkedIn post", "I need a better opener", or when the linkedin-post-writer skill needs strong opening options. Also triggered by "my posts aren't getting clicks" or "how do I get people to read my posts".

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

This skill should be used when a session's job is POST-MERGE VERIFICATION — taking merged PRs and establishing whether the change actually does what it claimed, then recording the result against its `pr_verifications` obligation. "validate the merged PRs", "work the verification backlog", "did that PR actually work", "run the post-merge E2E". It owns the obligation ledger the repo-pulse worker fills. Do NOT load it for building a change and opening its PR (that is `genesis-development`), or for driving open PRs to merge (that is `closing-session`).

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

This skill should be used when the user asks to "write a LinkedIn post", "draft a post about", "help me post on LinkedIn", "create LinkedIn content", or when Genesis proactively generates post ideas during surplus compute. Also triggered by content calendar execution or when the user shares a topic they want to write about.

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

This skill should be used before answering "does Genesis have X", "does Genesis lack X", auditing Genesis capabilities, comparing Genesis to an external system, or reviewing/summarizing the architecture. It routes to the canonical judgment-layer subsystem map so audits start from the map, not from a cold grep. Also fires after changing a subsystem's capabilities, to keep the map current.

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

Executes an approved implementation plan through fresh implementer and reviewer agents for each task, with explicit handoffs, focused tests, and task-by-task integration. Use for multi-task work where independent agent context improves implementation and review quality. Not for a single small edit, an unresolved design, or a failure that still needs root-cause analysis.

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

Executes an existing implementation plan task by task, preserving its interfaces and constraints, running focused checks after each slice, and stopping when the repository differs from the plan. Use when a written plan or approved checklist already exists. Not for inventing the plan, debugging an unexplained failure, or broad unscoped cleanup.

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

Processes code review feedback by classifying each finding, reproducing or validating it against the real contract, applying the smallest in-scope fix, and re-running focused proof. Use after comments arrive on a diff, pull request, design, or implementation. Not for requesting a first review or debugging an unrelated failure.

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

Reviews a GitHub pull request or focused branch diff for correctness, regressions, security, compatibility, test gaps, and maintainability. Use when an implementation needs an independent source-aware review before merge. Produces prioritized findings with evidence and actionable fixes. Not for architecture-only audits, formatting preferences, or processing existing review feedback.

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

Prepares a focused code review request for a branch, commit, pull request, or substantial working-tree diff by defining the review boundary, contract, risk areas, evidence, and questions for an independent reviewer. Use before merge or when another agent needs to review an implementation. Not for processing feedback already received or for claiming runtime correctness.

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

Tests whether changes caused a metric move without a clean A/B test: DiD, synthetic control, IV, RDD. Use when asking did a launch cause lift.

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

Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations as PowerPoint (.pptx) files; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email, summary, or creating a different type of slide deck); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user asks for a PowerPoint or .pptx file, or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. However, when the user asks for a deck, slides, a slide deck, or a presentation without naming a file format, default to using a dedicated slide-deck artifact type or a separate slides skill if this session offers one; otherwise, use this skill.

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

ALWAYS start here when the user wants a page OR a doc: page, living page, doc, document, living doc, bongo or bongo doc (the old name; new ones are made here, not by a Bongo connector), shared or collaborative doc, write-up, one-pager, memo, brief, proposal, plan, spec, report, meeting notes, notes, checklist, tracker, or anything to read, edit, comment on and share together — 'write this up', 'put this in a doc', 'draft a brief', 'jot this down somewhere we can share and edit', 'turn this file into a page' — the DEFAULT for any of these when no file format is named; a Word/.docx, PDF, .pptx or .xlsx FILE asked for by name goes to that format's skill instead. Also whenever the pages connector is about to be used to create a page. Not for READMEs, code or docstrings. A lowercase /pages as its own word anywhere in the message (not in a URL, path or longer name) invokes this skill whatever else is asked — a summary, an answer, a comparison, a plan: the page is the reply.

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

Use when implementing PlainTab features or bug fixes with test-first development, red-green-refactor, regression scripts, browser checks, or behavior-focused validation before production code changes.

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