「org」の検索結果

Protein language models through the EvolutionaryScale `esm` Python SDK. Generate and embed sequences with ESM3 (multimodal sequence, structure and function prompting), extract per-residue and mean-pooled embeddings with ESM C, fold sequences with ESMFold2, and run inference locally or against the Forge and Biohub hosted clients. Use this skill for protein representation learning, variant effect and mutational scanning from likelihoods, sequence generation and inpainting, structure prediction from sequence alone, and embedding features for downstream models. Also trigger on esm, ESM3, ESMC, ESM Cambrian, ESMFold2, `from esm.models`, ESMProtein, GenerationConfig, forge.evolutionaryscale.ai, biohub.ai, or ESM_API_KEY.

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

This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.

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

Organize, extract, prune, and verify Claude Code persistent memory files. Covers MEMORY.md as a concise index, topic extraction to dedicated files, staleness detection, accuracy verification against project state, the dual 200-line / 25KB load cap, and reachability of topic files from the index. Use when MEMORY.md is approaching either load cap, after a session produces durable insights worth preserving, when a topic section has grown beyond 10-15 lines and should be extracted, when project state has changed and memory entries may be stale, or before and after rewriting the index so that no topic file loses its only pointer.

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

Apply collective intelligence coordination patterns — stigmergy, local rules, and quorum sensing — to organize distributed systems, teams, or workflows without centralized control. Covers signal design, agent autonomy boundaries, emergent behavior cultivation, and feedback loop tuning. Use when designing distributed systems without a coordination bottleneck, organizing teams that must self-coordinate, building event-driven architectures with shared state communication, or replacing fragile centralized orchestration with resilient emergent coordination.

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

Catalog and classify materials using standard library systems. Covers descriptive cataloging, subject headings, call number assignment using Dewey Decimal and Library of Congress Classification, MARC record basics, shelf organization, and authority control for consistent access points. Use when organizing a personal, institutional, or community library from scratch, assigning call numbers and subject headings to new acquisitions, reclassifying a collection that has outgrown its original system, or establishing authority control for authors, series, or subjects.

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

Use when the user asks to remove a session or note from recall, or to unforget or list exclusions. Not for remote, credential, publish, deploy, or irreversible changes.

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

Save, organize, and describe reusable analysis artifacts such as SQL, result snapshots, CSV exports, summaries, caveats, plots, and report-ready files. Use when users ask to save, export, share, cite, reproduce, or organize data-analysis outputs.

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

Save, organize, and describe reusable analysis artifacts such as SQL, result snapshots, CSV exports, summaries, caveats, plots, and report-ready files. Use when users ask to save, export, share, cite, reproduce, or organize data-analysis outputs.

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

Write a skill, or forge a script tool, so a solved problem survives.

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

当用户是管理者/创始人/领导者，面临企业增长停滞、文化僵化、战略转型困难、或在问"如何推动组织变革""企业文化怎么改""使命愿景怎么定"时激活。 核心信号：用户在描述组织层面的问题，且已经意识到"不是业务问题而是底层问题"。 不适用于：个人成长问题（除非明确映射到组织场景）、纯战术层面的业务调整。

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

Build an organic-traffic operating system for any site or app: a multi-phase, resumable engine that plans and ships a BATCH ROADMAP of landing pages (use-cases, playbooks, /for/ pages, roundups) on top of real keyword research, with a persistent phase tracker. Use when the user says 'SEO machine', 'build organic traffic', 'rank on Google', 'we need traffic', 'SEO roadmap', 'batch of pages', 'pages roadmap', or 'build an SEO engine'. Distinct from `seo-audit` (one-off diagnostic) and `seo-content` (single-article writer): this skill owns the multi-page roadmap, run sequencing, page generation, internal linking, and the persistent phase tracker across the whole run. For a single alternatives or vs/comparison page, see /competitor-alternatives; for programmatic SEO templates and content at scale, see /seo-content; for off-page link building, see /off-page-seo. Resumable — every invocation continues the last run.

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

Write engaging PR titles and descriptions for any forge (GitHub today; Bitbucket planned). Use when creating or updating PRs. Leads with narrative paragraphs and reaches for lists, tables, and diagrams when content is genuinely structured.

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

Use when you need Liberty91 platform intelligence — what actually happened (deduplicated Threat Events with every source, Admiralty reliability/credibility and verification stage), whether an IOC is already known to your account, the canonical threat library (actors, malware, vulnerabilities, clusters, ATT&CK TTPs), alert matches, or which of your customer organizations an occurrence affects — or when you need to push intelligence back: ingesting your own report, generating an intelligence package, or uploading an organization document. Also supplies event provenance fields, when the platform returns them, and Threat Library alias resolution to /source-provenance and /quality-of-information-check. Two-way, first-party integration. Commonly invoked by /ip-investigation and friends, /ioc-enrichment-workflow, /threat-actor-profiling, /campaign-tracking and /vulnerability-intelligence. Reads $LIBERTY91_API_KEY.

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

Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector stores), and the cognitive architectures that organize them. Key insight: Memory isn't just storage - it's retrieval. A million stored facts mean nothing if you can't find the right one. Chunking, embedding, and retrieval strategies determine whether your agent remembers or forgets. The field is fragm

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

Executes comprehensive red team exercises that simulate real-world adversary operations against an organization's people, processes, and technology. The red team operates with stealth as a primary objective, employing the full attack lifecycle from initial reconnaissance through objective completion while testing the organization's detection and response capabilities. This differs from penetration testing by focusing on adversary emulation rather than vulnerability identification. Activates for requests involving red team exercise, adversary simulation, adversary emulation, or full-scope offensive security assessment.

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

Operate a reusable technical book manuscript workspace with writing structure, reader persona SSOT, review rules, and optional Markdown to Re:VIEW/PDF support. Use when organizing a book manuscript repo, defining or reviewing target readers, standardizing chapter/section files, setting writing/review agents, handling publisher proof comments, or assessing an existing writing workspace. Triggers on book writing workspace, reader persona, reader audience, 読者ペルソナ, persona SSOT, technical book project, 執筆ワークスペース, manuscript workflow, Re:VIEW workspace, proof PDF, annotated proof, publisher proof comments, 校正, 校正注釈, and 初校.

Company expense receipt workflow. OCR, rename, sort, summarize, and prepare receipt images/PDFs/videos for D365 expense mapping and attachment. Use when sorting company expense receipts, organizing travel expense files, OCR renaming, receipt sorting, expense sorting, レシート仕分け, 出張経費バッチ, D365経費仕分け, D365経費カテゴリマッピング, or D365経費精算. Not for personal or sole-proprietor tax receipts (確定申告).

Organize receipt images and subscription invoice/receipt PDFs for Japanese sole-proprietor or side-business bookkeeping: extract evidence, rename files, and update monthly memos. Use for 領収書, レシート, receipt, OCR, リネーム, 確定申告, 勘定科目, 経費, subscription receipts, or payment-method change history. Not for company/D365 travel expense claims.

"Apply the Knowledge-Based View (Grant, 1996) and Nonaka and Takeuchi's SECI model to analyze how organizations create, transfer, and integrate knowledge for competitive advantage. Use this skill when the user needs to design knowledge management systems, understand why knowledge transfer fails across teams, evaluate knowledge creation processes, or when they ask 'how do we capture tacit knowledge', 'why does knowledge stay siloed', or 'how can we turn individual expertise into organizational capability'.".

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

"Apply Giddens' structuration theory to analyze the duality of structure — how social structures are both the medium and outcome of the practices they organize. Use this skill when the user needs to bridge agency and structure in organizational or social analysis, explain how routines reproduce or transform institutional patterns, analyze the recursive relationship between action and structure, or when they ask 'do people shape institutions or do institutions shape people', 'how are these routines maintained', or 'where does change come from if structures constrain action'.".

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

"Apply Institutional Theory (DiMaggio and Powell, 1983) to analyze how coercive, mimetic, and normative isomorphic pressures shape organizational structures and practices. Use this skill when the user needs to explain why organizations in the same field look alike, evaluate whether a practice was adopted for legitimacy vs efficiency, analyze regulatory or social pressures on strategy, or when they ask 'why do all firms in this industry do the same thing', 'is this best practice or just conformity', or 'how do regulations shape our structure'.".

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

"Apply the three-level framework of digital transformation — Digitization, Digitalization, and Digital Transformation — to diagnose and plan organizational change enabled by digital technologies. Use this skill when the user needs to assess an organization's digital maturity, distinguish between automating processes versus transforming business models, plan a DX roadmap, or when they ask 'where are we on digital transformation', 'is this digitization or real transformation', or 'how do we build a DX strategy'.".

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

"Apply Smith and Lewis's paradox theory to identify and manage organizational tensions across performing, organizing, belonging, and learning dimensions. Use this skill when the user needs to diagnose persistent either/or tensions, design dynamic equilibrium strategies that embrace both poles, or when they ask 'why does solving this problem make it worse', 'how do we pursue exploration AND exploitation simultaneously', or 'why do our strategic tensions keep recurring despite resolution attempts'.".

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

"Apply organizational ambidexterity theory to balance exploration and exploitation activities. Use this skill when the user needs to diagnose whether an organization is over-exploiting or over-exploring, design structures that support both innovation and efficiency, or evaluate the tension between short-term performance and long-term renewal.".

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