4,365 件 ・ 関連度順
概要と使いどころ
Maz-UI v4 - Modern Vue & Nuxt component library with 50+ standalone components, composables, directives, theming, i18n, and SSR support. Use when building Vue/Nuxt applications with forms, dialogs, tables, animations, or need responsive design system with dark mode.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "upload images to Cloudflare", "implement direct creator upload", "configure image transformations", "optimize WebP/AVIF", "create image variants", "generate signed URLs", "add image watermarks", "integrate with Next.js/Remix", "configure webhooks", "debug CORS errors", "troubleshoot error 5408/9401-9413", or "build responsive images with Cloudflare Images API".
日本語の概要は準備中です。原文の説明を表示しています。
Use for Bun file I/O: Bun.file, Bun.write, streams, directories, glob patterns, metadata.
日本語の概要は準備中です。原文の説明を表示しています。
Use when publishing, open-sourcing, exporting, sanitizing, or moving code, agent skills, prompts, templates, fixtures, datasets, workshop assets, or other artifacts from a private repository, vendor/runtime environment, or mixed working directory into a public repository or registry. Builds a provenance inventory, license/security review, explicit allowlist, clean staging package, approval dry run, and fresh public clone/install smoke. Triggers on "open source this", "publish these skills", "make this repo public", "export and sanitize", "подготовь публичный релиз", "выложи скиллы", "опенсорсни", "санитизируй и опубликуй". NOT for ordinary upstream bugfix PRs, vulnerability disclosure, or creating a corp-* department.
日本語の概要は準備中です。原文の説明を表示しています。
Use when needing strategic project analysis from multiple independent expert perspectives. Triggers on business decisions, growth strategy, product direction, competitive analysis, or any situation where diverse C-level opinions reduce blind spots
日本語の概要は準備中です。原文の説明を表示しています。
Use when packaging Docker deployments as 1Panel local app store apps, including GitHub projects, docker-compose.yml files, docker run commands, app metadata, version directories, icons, README files, and 1Panel validation.
日本語の概要は準備中です。原文の説明を表示しています。
Remove AI-generated writing patterns from rebuttal prose to make it sound natural, direct, and authentically human-authored. Use when a Stage 2 refined draft or Stage 4 follow-up response reads too formulaic, robotic, or "GPT-like". Supports academic English.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically organizes files in a directory into a clean structure based on configurable rules — by file type, date, project, or priority — with support for duplicate detection, naming conventions, and archival strategies. Use when the user requests file organization or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Developmental Psychologist. Use when a task calls for Developmental Psychologist judgment. Reasons from developmental trajectories, measurement invariance, and familial-environmental context through age-normed instruments (Bayley, WPPSI/WISC, CBCL, MacArthur-Bates CDI), false-belief and violation-of-expectation paradigms, and lme4/lavaan growth models while treating verbal-demand confounding of theory of mind, informative attrition, adult-normed task misapplication, and parent-versus-direct-assessment divergence as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Clinical Laboratory Scientist. Use when a task calls for Clinical Laboratory Scientist judgment. Reasons from pre-analytical–analytical–post-analytical total testing process; EP15/EP09/EP28 validation, Westgard/Sigma IQC, HIL indices (C56), EP23/IQCP, critical-value read-back, type-and-screen/crossmatch, CLSI M100 direct AST, LC-MS/MS C62, and AUTO10 autoverification.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Antenna Engineer. Use when a task calls for Antenna Engineer judgment. Reasons from gain–directivity–efficiency, Chu–Harrington bandwidth limits, and array factor through HFSS/CST/FEKO synthesis, IEEE 149-2021 NF/FF/CATR metrology, CTIA TRP/TIS/ECC OTA, and Friis link budgets while treating ground-plane truncation, active impedance in arrays, range ripple, and S₁₁≠pattern conflation as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
The telemetry each Active Directory technique generates and what alerts a defender: Kerberoasting produces Event 4769 with RC4 encryption (0x17) and an MDI alert, DCSync produces Event 4662 with the DS-Replication-Get-Changes GUID, AS-REP roasting produces Event 4768 with no pre-auth, LSASS dumping is blocked by EDR, plus a lateral-movement telemetry table by protocol (SMB/WMI/WinRM/RDP/DCOM). Use this whenever you run or plan an offensive AD technique and need to know what noise it makes, when writing the engagement's detection notes, or when a defender wants to know what to monitor. Teaches red teamers what is loud and blue teamers what to watch. Standard-tooling knowledge, no vendor engine.
日本語の概要は準備中です。原文の説明を表示しています。
Kerberos-based Active Directory attacks driven by hand with standard tooling (Kerberoasting, AS-REP roasting, and delegation abuse: unconstrained, constrained/S4U, RBCD). Use when the target has SPN-bearing service accounts, accounts without pre-authentication, or delegation configured on computer/user objects, and you want the exact impacket/Rubeus/bloodyAD command, the hash format and hashcat mode, the Windows Event IDs that fire, and the remediation to write up.
日本語の概要は準備中です。原文の説明を表示しています。
The order of operations for an Active Directory penetration test: setup, collection, exploitation, post-processing. Use this whenever you are planning or driving an AD assessment and need to know what to run before what and why (map before you exploit; harvest easy credentials before spraying to avoid lockouts; collect the graph before you reason about paths). Covers phase sequencing with standard tooling: netexec/nxc, impacket, certipy, bloodyAD, kerbrute, BloodHound CE. Invoke it at the start of an engagement, when deciding the next phase, or when a step feels out of order.
日本語の概要は準備中です。原文の説明を表示しています。
Real-world Active Directory environment constraints that silently break attacks when ignored: NTLM disabled (Kerberos fallback), AES-only KDCs (RC4 blocked by GPO), LDAP signing and channel binding requiring LDAPS on 636, Kerberos clock skew (KRB_AP_ERR_SKEW), SPNs that must be FQDNs never short names or IPs (the misleading invalidCredentials), Protected Users / LAPS / gMSA / MachineAccountQuota, LDAP 1000-object paging, and VPN latency. Use this whenever a bind, TGT request, LDAP query, or SMB negotiation fails in a way that looks like bad credentials but is really hardening, or before running any AD tooling against a domain you have not fingerprinted. Standard-tooling knowledge (netexec, impacket, certipy, bloodyAD, kerbrute), no vendor-specific engine.
日本語の概要は準備中です。原文の説明を表示しています。
Abusing Active Directory object ACLs (DACL/ownership) for privilege escalation and lateral movement (GenericAll, GenericWrite, WriteDACL, WriteOwner, AddMember, ForceChangePassword, and replication rights via DS-Replication-Get-Changes-All). Use when BloodHound CE shows an outbound control edge from a principal you own toward a higher-value object, and you want the exact bloodyAD/impacket command to weaponize that ACE, plus detection and remediation. DCSync is covered here strictly as a post-compromise technique, not a user entry path.
日本語の概要は準備中です。原文の説明を表示しています。
Active Directory Certificate Services (AD CS) escalation techniques ESC1 through ESC17, driven by hand with Certipy (ly4k). Use when the target runs a Certificate Authority and you want to find vulnerable certificate templates or CA misconfigurations, request a certificate that impersonates a privileged user, and know the exact certipy command, what each ESC actually checks, the Windows Event IDs that fire, and the remediation. ESC1 and ESC8 are the two you hit most in the field.
日本語の概要は準備中です。原文の説明を表示しています。
SwiftUI frontend visual design skill. Creates beautiful, distinctive iOS/macOS interfaces that avoid generic AI slop patterns. Covers design direction, layout systems, typography, color, spacing, brand integration, and design review. Use when designing new SwiftUI views, reviewing UI quality, creating iOS prototypes, choosing visual styles, improving app aesthetics, or when the UI looks generic or AI-generated.
日本語の概要は準備中です。原文の説明を表示しています。
The research-domain clarification skill — find underspecified items in a thesis spec.md (prose wrong_if, universe rows without rationale, missing budget/expiry/pins, ambiguous pillars), ask the human structured questions WITH options (max 5 per round), encode the answers back into spec.md's Clarifications section, and re-evaluate checklists/thesis-quality.md after every write (Q32 bidirectional maintenance).
日本語の概要は準備中です。原文の説明を表示しています。
Options price action strategy, volatility-aware entries, options structure selection by market regime, delta and gamma positioning, options overlay on directional views, expiry selection
日本語の概要は準備中です。原文の説明を表示しています。
Price action market structure analysis, trend vs trading range classification, Always In directional framework, buying/selling pressure analysis, market cycle phase identification, the price action methodology
日本語の概要は準備中です。原文の説明を表示しています。
Options trade execution, directional strategies long call covered call collar, spread strategies bull call bear put ratio ladder, volatility strategies straddle strangle strap strip, liquidity cost and implied volatility filters, integration with gold.technical_setups for options setup matching
日本語の概要は準備中です。原文の説明を表示しています。
Execute research tasks — checklist soft gate, phase dispatch with explicit thesis_dir, budget enforcement (halt + approval card on overrun), skill_pin recording (version_hash content-hashed per skill directory), [x] written on completion.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and direct Midjourney Video V1 image-to-video work through the official website or Discord, with human operator handoff, motion prompts, start/end frames, loops, extensions, resolution and batch budgeting, privacy, rights, safety, and delivery QA. Use when creating Midjourney videos or when determining whether a requested API, automation, plan, or production workflow is supported.
日本語の概要は準備中です。原文の説明を表示しています。