3,825 件 ・ 関連度順
概要と使いどころ
This skill should be used when the user asks to "plan team structure", "determine hiring needs", "design org chart", "calculate compensation", "plan equity allocation", or requests organizational design and headcount planning for a startup.
日本語の概要は準備中です。原文の説明を表示しています。
Für Formvorgaben Anzeigen Erklärungen 309: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.
日本語の概要は準備中です。原文の説明を表示しています。
Breaks down complex software, writing, or research tasks into small, atomic, independently completable units with dependency graphs and milestone breakdowns. Use when the user asks to plan a project, decompose a feature, create subtasks, split up work, or needs help organizing a large piece of work into a step-by-step plan. Triggered by phrases like "break down", "decompose", "where do I start", "too big", "split into tasks", "work breakdown", or "task list".
日本語の概要は準備中です。原文の説明を表示しています。
Organize care for an aging or ill family member across multiple helpers — the shared care map, a fair rotation with backup rules, the information binder, and family-meeting agendas that prevent the one-sibling-does-everything spiral. Use when asked help me coordinate care for my mom, my siblings and I need to split caregiving, organize care for a sick family member, or set up a care schedule. Produces the care map of needs and coverage, the rotation schedule with escalation rules, the binder outline, and the family meeting agenda.
日本語の概要は準備中です。原文の説明を表示しています。
Create a structured change management plan for any organisational change. Use when asked to write a change management plan, manage a change initiative, plan a system rollout, or lead an organisational transformation. Produces a plan covering stakeholder analysis, impact assessment, communication strategy, and resistance management.
日本語の概要は準備中です。原文の説明を表示しています。
Organize the people and information involved in caring for someone — family, doctors, helpers — so care doesn't fall through the cracks or all land on one person. Use when asked help me coordinate care for, organize caregiving for my parent, set up a care system, or I'm drowning coordinating everyone. Produces a map of who does what (medical, daily, financial, emotional), a shared-information system so everyone's on the same page, a way to divide tasks fairly among family, a communication rhythm, and how to keep the key information (meds, contacts, wishes) in one accessible place — turning caregiving chaos into a coordinated effort.
日本語の概要は準備中です。原文の説明を表示しています。
Help users design their marketing organizational structure and select the foundational technology stack needed to drive scalable growth.
日本語の概要は準備中です。原文の説明を表示しています。
Help users design high-performing product and engineering organizations by choosing the right reporting models, team sizes, and cross-functional partnerships. It focuses on reducing friction and maximizing ownership through structural clarity.
日本語の概要は準備中です。原文の説明を表示しています。
Help users navigate complex transitions, from scaling new business units to managing crises and driving AI adoption across large organizations.
日本語の概要は準備中です。原文の説明を表示しています。
SpecStory Lore - mine your SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more) into a persistent corpus, surface your reproducible workflows with corroborated evidence, and interactively forge the chosen ones into skills installed across all your agent harnesses. Use when the user wants to turn past AI coding sessions into reusable skills, asks "what could I make into a skill", "mine my lore", "forge skills from my history", or points at a .specstory/history directory.
日本語の概要は準備中です。原文の説明を表示しています。
Detect Server-Side Request Forgery (SSRF) vulnerabilities in a codebase using a three-phase approach: recon (find outbound call sites), batched verify (trace user input to destinations in parallel subagents, 3 sites each), and merge (consolidate batch results). Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/ssrf-results.md. Use when asked to find SSRF or server-side request forgery bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Writes Vitest tests following project patterns: __tests__/ directories, vi.mock() for module mocking with vi.hoisted() for test-time factories, global LLM mock from src/test/setup.ts, environment variable save/restore in beforeEach/afterEach, vi.clearAllMocks() lifecycle, and test file organization. Use when user says 'write tests', 'add test coverage', 'test this', creates *.test.ts files, or when test failures appear in CI. Do NOT use for non-test code or for debugging without writing tests.
日本語の概要は準備中です。原文の説明を表示しています。
Use when choosing or sharpening a research question for an Accounting, Organizations and Society (AOS) manuscript — testing whether the question genuinely concerns the social, organizational, behavioral or institutional life of accounting, and picking the intellectual tradition the question demands. Screens fit; it does not build the theory (aos-theory-development).
日本語の概要は準備中です。原文の説明を表示しています。
Use when situating an Accounting, Organizations and Society (AOS) manuscript in the literature — entering one of the journal's own long-running conversations, engaging the interdisciplinary sources (organization theory, sociology, psychology) those conversations draw on, and marking precisely what the paper adds. Positions the argument; it does not build the theory itself (aos-theory-development).
日本語の概要は準備中です。原文の説明を表示しています。
Use when building the theoretical engine of an Accounting, Organizations and Society (AOS) manuscript — choosing a social/organizational theory tradition (institutional theory, governmentality, Bourdieu, actor-network theory, practice theory, psychological process theory) and making it generate the analysis rather than decorate it. Builds the lens; it does not collect data (aos-methods) or frame the contribution (aos-contribution-framing).
日本語の概要は準備中です。原文の説明を表示しています。
Use when articulating what an Accounting, Organizations and Society (AOS) manuscript contributes — converting findings into a claim that changes how the field understands accounting's social, organizational, behavioral or institutional operation. Frames the payoff; it does not produce new analysis (aos-data-analysis).
日本語の概要は準備中です。原文の説明を表示しています。
Detects and removes contamination in genome assemblies via two disjoint workflows - foreign-sequence screening of a single-organism (eukaryote/isolate) assembly with NCBI FCS-GX (GenBank-submission-mandatory), FCS-adaptor, and BlobToolKit blob plots; and MAG/bin quality assessment with CheckM2 plus GUNC (chimerism) plus GTDB-Tk taxonomy, judged against MIMAG. Covers why CheckM2 alone is blind to disjoint-marker chimeras, the FCS-GX RAM wall, organelle/NUMT triage, strain heterogeneity, and the HGT-vs-contamination (tardigrade) trap. Use when screening an assembly for foreign contamination before GenBank submission, assessing MAG completeness/contamination/chimerism, deciding which contigs to remove, or distinguishing real HGT from contaminant contigs.
日本語の概要は準備中です。原文の説明を表示しています。
Profiles a genome from raw reads BEFORE assembly with a k-mer spectrum (KMC or Jellyfish histogram), then models it with GenomeScope2 to estimate genome size, heterozygosity, repeat content, and ploidy, and Smudgeplot to infer ploidy from heterozygous k-mer pairs (diploid AB vs triploid AAB vs tetraploid AABB). Covers choosing k via Merqury best_k.sh, the k-mer-coverage vs sequencing-coverage confusion, reading het/repeat/contamination/organelle peaks, why noisy ONT must not be used for counting, and how the estimate becomes the NG50 denominator, the Flye -g value, the hifiasm --hom-cov/purge setting, and the 1.5-2x-too-big haplotig sanity check. Use when starting any de novo assembly, deciding whether short reads can work, estimating genome size for an unknown organism, diagnosing ploidy, or sanity-checking an assembly's size against expectation.
日本語の概要は準備中です。原文の説明を表示しています。
Style MATLAB charts and figures. colororder palettes for chart series colors, colormap selection, brand color organization, and the R2025a Theme API for uifigure apps (dark mode with fliplightness, ThemeChangedFcn, uistyle, component colors). Use when customizing chart colors, applying a color palette, organizing brand colors, implementing dark mode, or importing an external color scheme. Triggers: theme, dark mode, brand colors, colororder, colormap, palette, fliplightness, color scheme, styling, chart colors.
日本語の概要は準備中です。原文の説明を表示しています。
SEO and GEO (Generative Engine Optimization) for organic traffic and AI search visibility. Covers technical SEO, content SEO, keyword strategy, schema markup, and optimization for AI search engines (ChatGPT, Perplexity, Gemini). Use when the user needs SEO audit, keyword research, GEO optimization, schema markup, or says 'SEO', 'search optimization', 'keywords', 'organic traffic', 'AI search', 'GEO', or 'rank higher'.
日本語の概要は準備中です。原文の説明を表示しています。
Take a list of projects and their related documentation, and organize them into the SRED format for submission.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to add or optimize structured data (Schema.org, JSON-LD). Also use when the user mentions "schema," "structured data," "JSON-LD," "rich results," "rich snippets," "Google rich snippets," "featured snippet schema," "add schema to page," "missing structured data," "schema validation error," "Schema Markup Validator," "Google Rich Results Test," "FAQ schema," "Article schema," "Organization schema," "JobPosting," "HowTo," "Event," "SoftwareApplication," "BreadcrumbList," "WebSite," "Recipe," "Product," or "Dataset." For SERP feature types and zero-click patterns, use serp-features. For AI search visibility strategy (not markup), use generative-engine-optimization. For HowTo step sections (placement, copy, vs FAQ), use howto-section-generator.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Expert NIST Cybersecurity Framework (CSF) advisor covering CSF 2.0 and CSF 1.1. Use this skill whenever a user asks about NIST CSF, cybersecurity risk management, the six CSF functions (Govern, Identify, Protect, Detect, Respond, Recover), CSF profiles, implementation tiers, gap assessments, organizational profiles, community profiles, CSF core subcategories, informative references, or mapping to other frameworks (NIST SP 800-53, ISO 27001, CIS Controls, COBIT). Also trigger for questions like "how do I implement NIST CSF?", "what does CSF 2.0 change?", "help me build a CSF profile", "how do I assess my cybersecurity posture?", or any request involving organizational cybersecurity risk strategy or framework alignment.
日本語の概要は準備中です。原文の説明を表示しています。