4,165 件 ・ 関連度順
概要と使いどころ
Translates LaTeX documents (.tex) to Typst (.typ), focusing on article-class documents. Use when asked to convert, port, migrate, or translate LaTeX to Typst. Covers document structure, text formatting, page layout, math equations and symbols, figures, tables, TikZ-to-CeTZ diagrams, bibliography, cross-references, footnotes, and code blocks. Includes comprehensive symbol mapping tables.
日本語の概要は準備中です。原文の説明を表示しています。
Use whenever you state a fact. End the answer with a short Sources list mapping each claim to a file, URL, or reasoning. Shared across agents.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Stakeholder Theory (Freeman, 1984) and the Mitchell et al. (1997) salience model to identify, classify, and prioritize stakeholders based on power, legitimacy, and urgency. Use this skill when the user needs to map stakeholders for a project or strategy, determine which stakeholders demand immediate attention, balance competing stakeholder interests, or when they ask 'who are our key stakeholders', 'how do we prioritize conflicting demands', or 'which stakeholders can block this initiative'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Co-opetition Value Net framework (Brandenburger and Nalebuff, 1996) to map cooperative and competitive dynamics in business relationships. Use this skill when the user needs to identify complementors, analyze the PARTS framework, or design strategies that simultaneously cooperate and compete with the same players.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Bourdieu's field theory to analyze power relations through the interplay of field, capital, and habitus. Use this skill when the user needs to map positions and position-takings within a social field, analyze how different forms of capital (economic, cultural, social, symbolic) structure competition, explain why actors behave as they do within institutional settings, or when they ask 'why do people in this industry act this way', 'who has power and why', or 'how does this field reproduce inequality'.".
日本語の概要は準備中です。原文の説明を表示しています。
"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 Actor-Network Theory (Latour, Callon) to trace how human and non-human actors (actants) form networks through translation processes. Use this skill when the user needs to map sociotechnical assemblages, analyze how innovations stabilize or fail through network-building, trace the four moments of translation (problematization, interessement, enrollment, mobilization), or when they ask 'how did this technology become accepted', 'who and what holds this network together', or 'why did this innovation fail to gain traction'.".
日本語の概要は準備中です。原文の説明を表示しています。
Design and draft multi-email sequences with full copy, timing, branching logic, exit conditions, and performance benchmarks. Use when building onboarding, lead nurture, re-engagement, win-back, or product launch flows, when you need a complete drip campaign with A/B test suggestions, or when mapping a sequence end-to-end with a flow diagram.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Moore's business ecosystem framework to analyze how firms co-evolve through four stages (birth, expansion, authority, renewal) and occupy different ecosystem roles. Use this skill when the user needs to map ecosystem dynamics in a platform or industry, evaluate keystone vs dominator strategies, assess ecosystem health, or when they ask 'what stage is this ecosystem in', 'how should we position in this ecosystem', or 'why is this ecosystem declining despite having a dominant player'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Balanced Scorecard (BSC) framework to translate strategy into measurable objectives across Financial, Customer, Internal Process, and Learning & Growth perspectives. Use this skill when the user needs to set strategic KPIs, create a strategy map, align organizational goals, or connect daily operations to strategic vision — even if they say 'how do we measure strategy execution' or 'our KPIs feel disconnected'.".
日本語の概要は準備中です。原文の説明を表示しています。
Write a durable feature spec before touching code. Reads the codebase map, reads related models/migrations to ask technical questions (not generic ones), then produces a structured spec doc in docs/specs/. Designed to pipeline with /implementation --issue N. Use before any feature implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Design data models with Pydantic schemas, comprehensive validation rules, type annotations, and relationship mappings.
日本語の概要は準備中です。原文の説明を表示しています。
Validate user stories — INVEST scoring, story-to-test coverage mapping, PRP completeness, and development-readiness assessment. Use after writing stories and before starting implementation. Trigger on "validate the stories", "are these stories ready", "INVEST check", "story coverage", "is this ready to build".
日本語の概要は準備中です。原文の説明を表示しています。
Voegt een proof-of-concept toe aan het poc-portaal op poc.regelrecht.rijks.app — register-entry, map-indeling, de subpad-aanpassingen die een losse app nodig heeft om onder /<slug>/ te draaien, en de bedrading in de deploy. Gebruik dit bij "voeg poc X toe", het verhuizen van een losse PoC-repo naar de monorepo, of het aanpassen van status en voorbehoud van een bestaande poc.
日本語の概要は準備中です。原文の説明を表示しています。
Builds and audits a concept-ontology for a regelrecht corpus to decide and verify reference types — cross-law source-binding vs intra-law source-binding vs open-norm leaf vs external-fact leaf — and to catch concept conflation across laws. Core principle: a value's reference type is fixed by WHO derives it, and a binding is sound only when producer and consumer denote the SAME concept; the lexical surface (the word in the text) is not the concept. Detects false friends (one term, different concepts — e.g. a register-based vs a factual "naar de omstandigheden"-based residence/ingezetene concept), orphan plain-params (a value a regulation actually derives, modeled as a brute input), negation/complement re-entry (¬X modeled as an independent leaf next to X), and duplication (one concept re-entered as several independent leafs, losing the single-source-of-truth invariant). Produces a law-level glossary and a stelsel-level concept map with sound same-concept binding edges and flagged lexical-match-but-concept-mismatch edges. Use when deciding whether a value should be cross-law/intra-law/leaf, when the same term means different things across laws, or when a binding might silently conflate concepts.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically add a new memory-system reference to Auto_Memory's reference hub. Use when analyzing a new agent memory system, adding reference/<system>/details.md, saving prompts, or updating reference/hub/technique_map.json.
日本語の概要は準備中です。原文の説明を表示しています。
Idiomatic Go - package and interface design, error wrapping, table-driven tests, generics, the modern standard library (slices/maps/cmp/errors.Join), current syntax, and logging discipline. Use when writing, reviewing, or refactoring any Go code, especially code drifting toward Java/Spring shapes (deep layer trees, generic repositories, heavy frameworks) - even if the user never says "idiomatic". Distilled from spf13/go-skills and adapted to this repo.
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning, drafting, revising, compressing, or auditing conference rebuttals and author responses in OpenReview Markdown or PDF. Supports exact reviewer mapping, evidence and experiment integration, guided risk decisions, venue-format validation, and blind reviewer/AC audits.
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user to surface experience that is real but undocumented, mapped against a specific role's requirements, then update the profile. Use when a fit assessment or an adversarial review flags a section as thin.
日本語の概要は準備中です。原文の説明を表示しています。
Assess organizational training needs using ADDIE methodology and Kirkpatrick's 4-Level evaluation framework. Maps performance gaps to learning objectives using Bloom's taxonomy. Use when planning L&D budgets, designing training programs, or evaluating training effectiveness.
日本語の概要は準備中です。原文の説明を表示しています。
Rapidly map a new codebase, identify the runtime model, risk zones, and first high-value next steps.
日本語の概要は準備中です。原文の説明を表示しています。
Stand up or reset project governance for new, complex, or troubled initiatives using PMBOK 8 value delivery, OKR alignment, and Scrum or SAFe cadence choices where relevant. Use when a project needs a charter, decision rights, stakeholder map, RAID logic, escalation path, or reporting rhythm. Do not use for simple task lists, isolated sprint notes, or code implementation planning.
日本語の概要は準備中です。原文の説明を表示しています。
Facilitate sprint planning by organizing backlog items, estimating effort, balancing capacity, identifying dependencies, and producing a sprint commitment summary. Use when teams need structured sprint planning output. Do not use for strategic roadmap planning, annual budgeting, or product vision work.
日本語の概要は準備中です。原文の説明を表示しています。
Translate strategy into a balanced scorecard, strategy map, OKR bridge, and executive initiative portfolio with clear measures, targets, and owners. Use when leadership needs strategic alignment, portfolio prioritization, or a management dashboard tied to outcomes. Do not use for ad-hoc brainstorming with no strategic horizon.
日本語の概要は準備中です。原文の説明を表示しています。