「grading」の検索結果

Helps a teacher prepare to teach an existing K-12 lesson (math / ELA / science / social studies) — a prep partner that thinks through the lesson's key student task with the teacher and leaves a short teacher-only prep note. Triggers on asks to internalize, prepare for, get ready to teach, or understand a lesson, including implicit ones ("help me get ready for tomorrow's lesson"), and right after another skill built a lesson, which it can follow. Not for building or adapting a lesson, grading, rubrics, assessment feedback, or generating quizzes or student-facing material, and not for single-fact lookups a sentence would answer ("what standard is this?", "how long is this lesson?").

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

Use this skill whenever the user asks to create, improve, audit, or split prompts for AI video generators (Seedance, Kling, Veo, Runway, Luma, Pika, Sora, any image-to-video system). The skill also covers storyboards, shot lists, director treatments, dynamic montage, multi-clip story structure, camera direction, lighting, blocking, pacing, character continuity, dialogue, and sound design. Trigger even when the user says things like "придумай сцену для видео", "разбей на склейки", "сделай раскадровку", "улучши промпт для Kling", "переведи сценарий в промпты", "как снять X в AI-видео", or shares a prompt and asks to fix it — even if they never say the word "prompt". Do NOT use for still images (use the sibling image skill), for editing, colour-grading or assembling footage that already exists, or for writing feature-length screenplays with no generation step.

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

MANDATORY for static source-to-test pairing: find or list source files/modules without corresponding tests, or suggest test locations from repository structure. Invoke even for a tiny package; do not substitute manual globbing. Uses Roslyn for C#/.NET and tree-sitter for Python, TS/JS, Go, Java, Rust, Ruby, Kotlin, Swift, PowerShell, and C++. DO NOT USE FOR: real line/branch/Cobertura data, coverage-backed test priorities, CRAP risk, or grading existing tests.

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

Write modern, version-aware C# for .NET repositories while staying compatible with the repo's target framework and language-version policy. USE FOR: modern idiomatic C# code; language-version compatibility decisions; upgrading or reviewing C# feature usage across versions. DO NOT USE FOR: non-C# .NET languages such as F# or VB; analyzer-only or formatter-only setup with no language feature choice. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

Pseudo-mutation analysis ONLY: answer whether tests would catch a bug if production code changed, which meaningful changes would still pass, or which caller-visible mutations existing assertions would miss; verify candidates when requested, then optionally close verified gaps. Includes explicit read-only per-test composition for grading. Activate for behavioral blind spots tied to production behavior. Polyglot. DO NOT USE FOR: suite taxonomy, metadata, or distribution reports (test-tagging); .NET line-vs-branch or Cobertura interpretation, arithmetic, plateaus, project-wide coverage gaps, or coverage-backed test/CRAP priorities (coverage-analysis; use native coverage tooling outside .NET); named-target CRAP (crap-score); new suites (code-testing); assertion/smell audits; or mutation tools.

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

Enable nullable reference types in a C# project and systematically resolve all warnings. USE FOR: adopting NRTs in existing codebases, file-by-file or project-wide migration, fixing CS8602/CS8618/CS86xx warnings, annotating APIs for nullability, cleaning up null-forgiving operators, upgrading dependencies with new nullable annotations. DO NOT USE FOR: projects already fully migrated with zero warnings (unless auditing suppressions), fixing a handful of nullable warnings in code that already has NRTs enabled, suppressing warnings without fixing them, C# 7.3 or earlier projects. INVOKES: Get-NullableReadiness.ps1 scanner script.

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

Detect package managers and CI action pins, then discover outdated or vulnerable dependencies. Returns structured findings without upgrading. Use when the user asks to "review dependencies", "check for outdated packages", "check dependencies", "scan dependencies", "dependency review", "check for outdated GitHub Actions", or "are my workflow actions up to date".

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

Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.

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

Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code.

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

Analyzes Rails applications and generates comprehensive upgrade reports with breaking changes, deprecations, and step-by-step migration guides for Rails 2.3 through 8.1. Use when upgrading Rails applications, planning multi-hop upgrades, or querying version-specific changes. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook.

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

Guide for upgrading Stripe API versions and SDKs

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

Use when upgrading an existing TypeScript codebase from Inngest SDK v3 to v4, or when fixing mixed v3/v4 API usage. Covers detecting current SDK usage, moving triggers into createFunction options, replacing EventSchemas with eventType/staticSchema, moving serve options to the client, updating realtime imports, rewriting step.invoke string IDs, checkpointing/serverless runtime settings, Connect option changes, and verification.

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

Guidelines for clinical decision support (CDS) documents: biomarker-stratified cohort analyses and GRADE-graded treatment reports. Covers structure, executive summaries, evidence grading (1A–2C), stats (HR, CI, survival), and biomarker integration. Use for pharma research docs, clinical guidelines, regulatory submissions.

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

Create multiple choice, true/false, fill-in-blank, matching quizzes. Auto-generate plausible distractors. Instant grading with explanations.

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

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.

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

Use when preparing a Spring Boot 3 application for Boot 4, upgrading to Boot 3.5 first, removing deprecated APIs, auditing dependencies, or planning a staged Framework 7 migration.

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

Use when upgrading an application from Spring Boot 3.5 to Boot 4, completing a Framework 7 migration, replacing modular starters, adopting Jackson 3, or diagnosing post-upgrade failures.

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

Noir art direction for Blender with high-contrast lighting, wet streets, silhouettes, and monochrome or limited-color grading.

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

Automatically updates a codebase to a new language version, framework version, or library update while ensuring all tests still pass. Use this skill when migrating Python 2→3, upgrading framework versions (React, Django, Angular), updating dependencies, or performing any version migration where tests define correct behavior. The skill analyzes failing tests caused by migration, categorizes errors (import errors, API changes, type errors, behavior changes), proposes systematic fixes, and verifies that test-observable behavior remains unchanged. Triggers when users ask to migrate code versions, upgrade dependencies while keeping tests passing, update framework versions, or perform test-guided version migrations.

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

Identify and replace deprecated API usage in source code with modern alternatives. Use when: (1) Modernizing legacy codebases, (2) Upgrading framework versions (React, Django, Spring, etc.), (3) Fixing deprecation warnings in build output, (4) Preparing for major version upgrades, (5) Ensuring code uses current best practices. Supports Python, JavaScript/TypeScript, Java, and other major languages with both AST-based detection and pattern matching for accurate identification and automated replacement with validation.

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

Secure dependency upgrades with supply chain protection, cooldowns, and staged rollout. Use when upgrading deps, configuring security policies, or preventing supply chain attacks.

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

Assesses ChIP-seq quality across antibody specificity, fragmentation, enrichment, replicate concordance, and library complexity. Computes FRiP, NSC/RSC (phantompeakqualtools), library complexity (NRF/PBC1/PBC2), deepTools plotFingerprint (JS distance, AUC, synthetic JS), ChIPQC, IDR with ENCODE Nself/Nt rules, and detects hyper-ChIPable artifacts. Use when validating an antibody, diagnosing failed peak calls, deciding whether to proceed with downstream analysis, grading against ENCODE thresholds, or auditing replicate concordance.

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

Think and work like an expert Immunotherapy Scientist. Use when a task calls for Immunotherapy Scientist judgment. Reasons from antigen recognition and checkpoint circuits through CAR-T/bispecific design, ASTCT CRS/ICANS grading, flow cytometry release CQAs, iRECIST response assessment, COMPASS/TIDE biomarker modeling, and JACIE/FACT IEC accreditation while treating antigen escape, pseudoprogression, tonic signaling, and step-up CRS as first-class failure modes.

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

Think and work like an expert Forensic Chemist. Use when a task calls for Forensic Chemist judgment. Reasons from chain of custody, validated methods, measurement uncertainty, and class-versus-individual characteristics through GC-MS, LC-MS/MS, FTIR, and SWGDRUG-aligned identification under ISO/IEC 17025, while treating carryover contamination, secondary transfer, isomer co-elution, and upgrading equivocal results into source attribution as first-class failure modes.

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