5,147 件 ・ 関連度順
概要と使いどころ
Harvest every `honey:` comment in the codebase into a debt ledger, so the deliberate shortcuts Lever 1 leaves behind get tracked instead of rotting into "later means never". Flags markers with no revisit trigger — those are the ones that go permanent silently. Use when the user says "honey debt", "/honey-debt", "what did honey defer", "list the shortcuts", or "what did we mark to do later". One-shot report; changes nothing.
日本語の概要は準備中です。原文の説明を表示しています。
Stack Honey onto Superpowers-style workflows (subagent-driven-development, dispatching-parallel-agents, executing-plans) and any orchestration that dispatches fresh subagents. Dispatched subagents run in isolated context and do NOT inherit the session's Honey hook, so they emit full-fat code and verbose reports. Use when you are about to dispatch implementer/reviewer/fixer/parallel subagents: it gives the exact Honey directive to paste into each dispatch prompt, with a worker variant and a reviewer variant, so the levers apply inside the subagents too — where the multiplied cost actually is.
日本語の概要は準備中です。原文の説明を表示しています。
Harvest honey shortcut markers into a debt ledger.
日本語の概要は準備中です。原文の説明を表示しています。
Harvest every `honey:` shortcut marker into a debt ledger, flagging the ones with no revisit trigger. One-shot report, changes nothing.
日本語の概要は準備中です。原文の説明を表示しています。
Local Windows privilege escalation on a STANDALONE / workgroup host, or a local shell on a domain member - foothold to SYSTEM. Token privileges (SeImpersonate/Potato), service misconfig (weak perms / unquoted path / writable binary), registry autologon creds, scheduled-task + writable-script abuse, DLL hijack, AlwaysInstallElevated, UAC bypass, credential loot. For DOMAIN escalation (kerberoast/DCSync/ADCS/BloodHound) use hunt-ad instead. Wiki-first, FIND schema output.
日本語の概要は準備中です。原文の説明を表示しています。
XSS hunting - reflected, stored, DOM-based. Marker discipline to avoid false positives. Blind-XSS beacons for stored contexts. SVG/markdown/redirect vectors. Wiki-first, FIND schema output.
日本語の概要は準備中です。原文の説明を表示しています。
Shared discipline for every hunt-* skill: scope and authorization gating, the two-account rule, the confirmation gate that separates a real finding from a false positive, enumeration limits, stop conditions, marker discipline, wiki-first query and self-heal, FIND output, Deadends, and wiki distillation. ALWAYS LOADED alongside any hunt skill. Also trigger directly on "is this in scope", "is this a real bug", "how do I confirm this", "should I keep going", "how many IDs should I test", "what severity", "how do I report this", "I got someone else's data". Every hunt-* skill assumes this file; without it they run without their safety and quality layer.
日本語の概要は準備中です。原文の説明を表示しています。
Active Directory attack hunting - enumeration to domain dominance. Spray-safe (lockout gate), AS-REP/Kerberoast, ACL + ADCS (ESC1-16), delegation, DCSync, lateral movement. Wiki-first, FIND schema output.
日本語の概要は準備中です。原文の説明を表示しています。
Designs and verifies skilld CLI output, terminal pickers, and full-screen flows. Use for terminal colours, loading feedback, keyboard controls, layout, errors, or end-to-end CLI UX reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze liquid markets with a strict ICT/SMC framework that combines multi-timeframe bias, liquidity sweeps, displacement, close-confirmed MSS/BOS, FVG/OB/Breaker/OTE retracements, premium-discount location, session timing, invalidation, targets, and risk-to-reward. Use for ICT chart reviews, live-market analysis, OHLCV scans, or validating a user's trade thesis. Return an auditable setup status and conditional plan; do not use for generic indicator analysis, order execution, or claims of proven institutional intent.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "write a query letter", "query", "querying", "pitch", "blurb", "back cover copy", "jacket copy", "comp titles", "comparable titles", "synopsis for agents", "submit to agents", "submission tracker", "self-publishing description", "retailer description", "ready to query", "submission readiness check", "submit a short story", "magazine submission", "short-fiction markets", "simultaneous submission", "reprint rights", "order a short story collection", or wants to prepare and track a finished manuscript's submission to agents, publishers, magazines, anthologies, or retailers. NOT for pitching a series of several books (use series-continuity), or self-publishing production, metadata, or book rights deals (use publishing). The blurb, retailer description, and the rights a short-fiction market buys, such as reprint rights, stay here.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead end", "drafting sprint", "writing cadence", or wants to draft a story by discovery with retrospective bible reconciliation. NOT for outline-first drafting, or mysteries and other clue-dependent genres where setup must come before payoff (use chapter-writing), or a reverse outline of an existing linear draft, a subplot cut, or another revision pass on existing chapters (use revision-continuity).
日本語の概要は準備中です。原文の説明を表示しています。
POS analytics tracking patterns (WooPosAnalyticsEvent sealed class, WooPosAnalyticsTracker, WooPosAnalyticsEventConstant). Use when writing, editing, exploring, debugging, or reviewing analytics tracking in POS (WooPos*) code. NOT for main store app — use the `store-analytics` skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Main app analytics tracking patterns (AnalyticsEvent enum, AnalyticsTrackerWrapper, KEY_*/VALUE_* constants). Use when writing, editing, exploring, debugging, or reviewing analytics tracking in the store management app. NOT for POS (WooPos*) code — use the `pos-analytics` skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Builds new Claude Code skills with consistent structure, enforced standards, and project-aware configuration. Use when creating a new skill, when the user describes a workflow they want automated, or when the user says they want a new slash command.
日本語の概要は準備中です。原文の説明を表示しています。
Builds new Claude Code agents with consistent structure, enforced standards, and project-aware configuration. Use when creating a new agent, when the user describes a specialised role they want delegated to, or when discussing team composition.
日本語の概要は準備中です。原文の説明を表示しています。
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
日本語の概要は準備中です。原文の説明を表示しています。
Collaborative brainstorming mode for thinking through problems, ideas, and features before planning. Use when the user wants to discuss, explore ideas, or think through a problem without writing code.
日本語の概要は準備中です。原文の説明を表示しています。
What this skill does and when to use it. Claude reads this to decide relevance. Include keywords users would naturally say.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Create platform-native content that resonates with each community's culture. Use when adapting technical content for WeChat, Hacker News, Reddit, Medium, Twitter/X, Dev.to, or LinkedIn. Transforms generic writing into content that feels written BY that community, not AT them.
日本語の概要は準備中です。原文の説明を表示しています。
Tracks and monitors US state privacy legislation across all 50 states, DC, and territories. Covers enacted comprehensive privacy laws (California CCPA/CPRA, Virginia VCDPA, Colorado CPA, Connecticut CTDPA, Utah UCPA, and subsequent enactments), pending bills, effective dates, and key requirement differences. Keywords: state privacy law, CCPA, CPRA, VCDPA, CPA, CTDPA, UCPA, multi-state.
日本語の概要は準備中です。原文の説明を表示しています。
Establishes boundaries for monitoring remote and hybrid workers including screen capture, productivity tracking, camera and microphone activation, attendance verification, and activity logging. Applies proportionality principles, transparency requirements, and evaluates less intrusive alternatives per EDPB and national DPA guidance. Keywords: remote work, monitoring, screen capture, productivity tracking, webcam, home office, hybrid work, proportionality, surveillance.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive methodology for auditing website cookies and tracking technologies. Covers automated scanning, cookie categorization, lifecycle documentation, and compliance gap analysis referencing the Planet49 CJEU ruling (C-673/17).
日本語の概要は準備中です。原文の説明を表示しています。