Post-analysis learning and process improvement. Use when completing major analysis projects, documenting lessons learned, or improving team analytical practices.
日本語の概要は準備中です。原文の説明を表示しています。
353 件 ・ 関連度順
概要と使いどころ
Post-analysis learning and process improvement. Use when completing major analysis projects, documenting lessons learned, or improving team analytical practices.
日本語の概要は準備中です。原文の説明を表示しています。
对一次编码会话做回顾。
日本語の概要は準備中です。原文の説明を表示しています。
Explain why a change, incident or session went as it did, separating proven causes from coincidence. Use when: a postmortem or retro is selected by name.
日本語の概要は準備中です。原文の説明を表示しています。
Process: retrospectives, session handoff, pair programming, subagent-driven development, condition-based waiting.
日本語の概要は準備中です。原文の説明を表示しています。
Agile ceremonies and sprint management specialist. Use when running standups, retrospectives, sprint planning, or tracking sprint progress.
日本語の概要は準備中です。原文の説明を表示しています。
Learn from public breach disclosures — extract the audit question each one implies and check your own stack. Capital One IMDS abuse, LastPass vault exfiltration, Okta Lapsus$, Snowflake credential reuse, MOVEit, SolarWinds, Equifax, Target POS, Codecov, Uber, Twilio — what would you check now if your boss said 'could that happen to us?' Use when the user mentions 'breach analysis,' 'lessons learned,' 'security postmortem,' 'breach patterns,' 'breach lessons,' 'has this happened to us,' 'apply breach lessons,' 'preempt breaches,' 'security retrospective,' 'real-world security incidents,' or wants to harden against known attacker playbooks.
日本語の概要は準備中です。原文の説明を表示しています。
Generates LESSONS.md files capturing institutional knowledge and failures. Use when closing out projects or investigations.
日本語の概要は準備中です。原文の説明を表示しています。
Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection. Use for research storytelling, contribution framing, paper comparison, figure planning, or research retrospectives. Not an acceptance predictor or a routine grammar/citation formatter.
日本語の概要は準備中です。原文の説明を表示しています。
PyTorch-based ML platform for drug discovery: graph molecular representation learning, property prediction (ADMET, activity), retrosynthesis, drug-target interaction (DTI), and pretraining on large molecular datasets. Provides GNN layers (GraphConv, GAT, MPNN), pretrained models, and benchmark datasets.
日本語の概要は準備中です。原文の説明を表示しています。
Read, write, and edit ChemDraw CDX/CDXML files with RDKit's rdkit.Chem.rdChemDraw plus direct XML editing, always paired with a rendered PNG. Parse molecules and reactions from .cdxml/.cdx, write structures with good 2D depiction, and hand-build or modify the parts RDKit cannot write: reaction arrows, plus signs, schemes/steps, and text/labels. Use for reaction schemes, synthesis routes, mechanisms, retrosynthesis, or SI figures. Critical: RDKit writes structures only — round-tripping a reaction through a Mol silently drops arrows and text; this skill shows the XML layer that preserves them. For pure molecular analysis (descriptors, fingerprints, SMARTS) use rdkit-cheminformatics; for multi-format 3D conversion use openbabel.
日本語の概要は準備中です。原文の説明を表示しています。
セッション終了時に自己改善Issueを自動生成するスキル。 「振り返りIssue出して」「レトロスペクティブ」「改善点をIssueにして」等のリクエストで発動。
Evaluates and improves skills, agents, commands, and hooks after a workflow slice. Use when execution felt slow, confusing, repetitive, or fragile.
日本語の概要は準備中です。原文の説明を表示しています。
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
日本語の概要は準備中です。原文の説明を表示しています。
Generates structured OKR plans (Objectives and Key Results) for teams and companies following Google/Intel methodology. Takes company goals, team function, quarter, and current metrics to produce a comprehensive okr-plan.md with objectives, key results, scoring criteria, alignment mapping, tracking cadence, and retrospective templates.
日本語の概要は準備中です。原文の説明を表示しています。
Use AiZynthFinder for retrosynthetic planning, configuration, route analysis, custom extensions, and focused development workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Post-engagement knowledge harvest AND harness retrospective - after a box/bugbounty/pentest/CTF is completed, first diff how the engagement was EXECUTED against the skills/hooks that governed it (what discipline was skipped) and improve the harness, then sweep the whole engagement for GENERIC reusable knowledge NOT already in wiki/ and land it via the leak-gated stage->promote pipeline. Use at close-out or when asked to "extract learnings", "what did we learn", "harvest lessons into wiki", "distill this engagement", "post-mortem into the wiki", "what did we do wrong", "improve the harness from this box".
日本語の概要は準備中です。原文の説明を表示しています。
Coach leaders and managers to prepare, run, and review high-bandwidth meetings that advance real work and decisions. Use for meeting retrospectives, employee work reviews, decision meetings, agenda and question design, direct feedback, meeting-quality diagnosis, or repeated low-value discussions. Preserve direct standards without taking over the worker's work or degrading the truth signal.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead end", "drafting sprint", "writing cadence", or wants to draft a story by discovery with retrospective bible reconciliation. NOT for outline-first drafting, or mysteries and other clue-dependent genres where setup must come before payoff (use chapter-writing), or a reverse outline of an existing linear draft, a subplot cut, or another revision pass on existing chapters (use revision-continuity).
日本語の概要は準備中です。原文の説明を表示しています。
Visual era art direction for Blender covering PS1–PS5 stylistic cues, retro arcade, DOS, CRT, VHS, and film-grain presentation.
日本語の概要は準備中です。原文の説明を表示しています。
PL (Project Lead) role sub-skill for incident analysis and process evaluation. Loaded through the pl core routing table, or when the owner explicitly asks for a retrospective or root-cause write-up; NEVER auto-load from ambient context.
日本語の概要は準備中です。原文の説明を表示しています。
Lightweight anti-hallucination workflow for task kickoff, review prioritization, and regression retrospectives. Use when the user asks for guardrails, task contracts, risk scoring, or review templates.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you want Codex to review its own recent history (last N days or specific period) and improve its behavior. Produces minimal, high-signal updates to AGENTS.md and tiny reusable skills. The goal is long-term fluency — Codex gradually becomes better at your specific style, constraints, and workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Plan sprints with story point estimation, capacity planning, sprint goals, and retrospective frameworks. Organize teams for effective iteration with clear goals, realistic commitments, and continuous improvement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a completed department retro should become accepted outcomes and a full living ISO-week plan, or the user asks "планирование", "план недели", or "что делаем на следующей неделе".
日本語の概要は準備中です。原文の説明を表示しています。