「arise」の検索結果

Use when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem results for a Ruff PR from a PR number, PR URL, GitHub ecosystem-results comment, or detailed HTML report.

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

Reads and summarises ScenarioRunner output — the criteria pass/fail tables from --output/--file, the machine-readable --json and --junit result files, and the criteria JSON written alongside a --record recording — and runs the metrics module (metrics_manager.py) to compute custom measurements over a recorded run offline, without the simulator. Use when the user asks "did the scenario pass", "why did it fail", "summarise these results", "compare these runs", or wants distance/speed/lane metrics from a recording.

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

Review and summarise any contract or legal agreement. Use when asked to review a contract, check an agreement, flag legal risks, or summarise key clauses. Produces a structured review with key terms, flagged clauses, risk rating, and plain English summary. Not a substitute for qualified legal advice.

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

Ask Questions If Underspecified workflow skill. Use this skill when the user needs Clarify requirements before implementing. Use when serious doubts arise and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Summarise the unit and e2e tests a branch/PR adds, run only those, and produce a paste-ready report (e.g. for a Linear card). Use when asked to 'summarise added tests', 'run the new tests', 'what tests did this PR add', or to prove a card's test coverage.

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

Summarises one sprint from the board export, sprint report and review or stand-up notes the user provides into a one-page DRAFT sprint review summary: the sprint goal as written, items delivered, items not delivered with the reasons the sources state, carry-over, impediments, metrics exactly as given, and numbered questions for the retrospective, every row referenced to a work item or note fragment and every missing fact marked UNKNOWN. Use when the user asks to "summarise the sprint", "write the sprint review", "what did we deliver this sprint", "list the carry-over and blockers" or "draft the sprint recap". Do not use for the retrospective write-up or themed lessons across several sprints, use lessons-learned-synthesis instead; for a weekly project status report, use project-status-tracker. Drafts for human review; never approves, authorises or signs off.

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

Synthesises exit interview notes or leaver survey responses into a DRAFT themed report: coded themes with record counts and shares, anonymised verbatim evidence, breakdowns by broad group only for groups that meet a minimum group size, referred items and open questions for the people team, without naming or identifying any individual. Use when the user asks to analyse, summarise, code, theme or report on exit interviews, leaver feedback, attrition interviews or departure surveys, or says "what are our leavers telling us", "theme these exit interviews" or "summarise the leaver survey". Do not use for customer or product feedback, use customer-feedback-theme-synthesis instead; for redacting one document with no theming, use document-deidentification-pass. Drafts for human review; never approves, authorises or signs off.

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

Reads and summarises ScenarioRunner output — the criteria pass/fail tables from --output/--file, the machine-readable --json and --junit result files, and the criteria JSON written alongside a --record recording — and runs the metrics module (metrics_manager.py) to compute custom measurements over a recorded run offline, without the simulator. Use when the user asks "did the scenario pass", "why did it fail", "summarise these results", "compare these runs", or wants distance/speed/lane metrics from a recording.

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

Clarify requirements before implementing. Use when serious doubts arise.

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

Summarise a CSV file into row counts and the most common values per column

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

Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template. Use when asked to write the changelog for this release, what changed since the last tag, draft release notes from my commits, or summarise this range for users in Cowork. Reads commits/PRs between two refs via the GitHub connector, groups them into user-facing changes (features / fixes / breaking), translates commit-speak into human benefit, and produces a changelog artifact ready for the release.

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

No Inference / Source-Locked Verification. Forces Claude to answer ONLY from user-provided materials and/or online sources actually accessed — no inference, no assumptions, no gap-filling. Every factual, legal, numerical, or procedural claim must be anchored to a cited source. Use whenever Claude reviews documents, summarises evidence, checks accuracy, drafts submissions, creates timelines, extracts facts, checks citations, analyses rules, prepares legal arguments, compares documents, verifies claims, produces chronologies, works from uploaded materials, performs legal research, checks case status, or does anything where evidential fidelity matters. Also trigger on: 'source-locked', 'no inference', 'only from the materials', 'don't assume', 'stick to the evidence', 'verify this', 'check this is right', 'work from the documents'. Overrides Claude's default tendency to fill gaps. If evidential accuracy matters, use this skill.

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

Draft matter status reports from emails, call notes, and updates. Internal and client-facing formats, RAG logic, variance commentary, escalation flags. Use when asked to draft a status report, write a project update, summarise matter progress, prepare a client report, create a weekly or monthly update, convert emails into a status summary, or produce any kind of matter reporting. Also triggers when the user pastes email threads and asks what the status is, or needs to turn internal updates into client-facing reports.

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

Produces detailed law-school case briefs of United States judicial opinions in a fixed nine-section structure: memory jogger, facts, procedural history, judicial votes, holding, opinion-by-opinion analysis, five future-application hypotheticals, critique, and verified key quotations. Also builds vote tables, cross-case consistency tables, perspective-based critiques, and LaTeX in article, Beamer and casebook-chapter formats. Use whenever someone asks to brief a case, analyse or explain an opinion, summarise a decision for students, generate hypotheticals from a holding, critique a judgment, tabulate how justices voted, or convert case analysis to LaTeX. Triggers on "brief this case", "case brief", "explain the holding", "what did the court hold", "hypotheticals based on", "critique this opinion", "vote table", "Beamer presentation", "chapter brief", and on any reference to a judicial opinion or Supreme Court decision in a teaching context. Requires web search to verify quotations, votes and holdings.

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

Build students' capacity to read historical documents closely — attending to word choice, tone, and rhetoric as evidence of perspective. Use when students summarise sources without analysing language.

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

Clarify requirements before implementing. Use when serious doubts arise.

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

Diagnose a failing TMDb integration-test run — summarise the failure, rank the likely cause, and suggest a concrete fix

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

Mine AI coding-agent session transcripts into structured, gate-validated GPU-kernel optimization records for the wiki. Use when asked to turn vibe-coding sessions, Codex rollout logs, or Claude Code project transcripts into wiki records; to summarise what a kernel-optimization session achieved; to build or extend a session-trace store; or to re-run and validate one. Also use when asked how a session-derived record's number, snippet, or provenance was established.

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

Ask Questions If Underspecified workflow skill. Use this skill when the user needs Clarify requirements before implementing. Use when serious doubts arise and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Analyzes an AI/ML publication — paper, preprint, article, technical blog post — and extracts what an enterprise AI engineer should do about it. Use when someone supplies a URL or document on RAG, embeddings, fine-tuning, prompt engineering, agents, or LLM deployment and asks "review this paper", "what do you make of this", "is this worth adopting", or "summarise the method and its limits". The subject matter must itself be machine learning.

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

Apply the strategic thinking of Thai Lee, CEO of SHI International. Use this skill when the user is navigating bootstrapping vs. venture capital, long-term career sequencing, building an egalitarian corporate culture, or scaling a customer-centric B2B sales organization. Trigger this skill for topics involving decade-by-decade life planning, empowering employees with extreme ownership, or turning personal disadvantages into fuel for preparation. Apply her frameworks whenever these themes arise, even if the user doesn't explicitly name her.

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

Build students' capacity to read historical documents closely — attending to word choice, tone, and rhetoric as evidence of perspective. Use when students summarise sources without analysing language.

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

Summarise the job search from the markdown tracker - funnel, response rate, what's working, where applications come from, what's pending on the user. Use when the user runs /seekter-report or asks how the search is going, for weekly numbers, or what to change.

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

Filter and summarise the cross-library KB audit log. Reports confidentiality events (attribution drops, synthesis aborts, dispatcher failures, no-evidence markers, cross-library promotions) over a date range, by event type, and by source handle.

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