Verify your Hugging Face account and search the model hub. Read-only. Trigger phrases: hugging face, huggingface, hf model, search models.
日本語の概要は準備中です。原文の説明を表示しています。
2,440 件 ・ 関連度順
概要と使いどころ
Verify your Hugging Face account and search the model hub. Read-only. Trigger phrases: hugging face, huggingface, hf model, search models.
日本語の概要は準備中です。原文の説明を表示しています。
Work with Linear: view your assigned issues and create issues. Trigger phrases: linear, linear issue, ticket.
日本語の概要は準備中です。原文の説明を表示しています。
Look up your Figma user, read file metadata, and post comments on files. Trigger phrases: figma, figma file, design file.
日本語の概要は準備中です。原文の説明を表示しています。
ALWAYS invoke this skill before asking the user any technical question or offering options, and whenever they ask to be asked in plain words - "ask simple", "ask me simply", "ask me in plain words" - in any language. ALWAYS invoke it too when the user asks for your view on a technical choice: whether it is worth doing, more than the problem needs, or replaceable by something simpler, and which option you would take. Invoke it even when the code makes the answer look obvious: the checks are what make the answer more than a guess. Rewrites the question in plain words and always ends with one marked recommendation. A structural choice first passes six checks, shown as a table: effort now, simpler substitute, extra work later, lock-in, over-engineering, easy to undo. Doing nothing is always weighed.
日本語の概要は準備中です。原文の説明を表示しています。
ALWAYS invoke this skill when you need the user to act - run a command, paste a secret, click, approve - and whenever they ask how to do something or say they do not know what to do: "step by step", "walk me through it", "what do I do", "what should I do", "I don't understand what to do", "explain what I need to do", in any language. Picking which task comes next is os-whats-next; this skill is for doing the thing in front of you. First earn the ask: try it yourself, find another route, shrink it to the part only they can do. Then one action per step, commands labelled by what they touch, no jargon. Commands are single lines that prompt for any value - typing hidden for secrets - and confirm in plain words. Afterwards verify their step.
日本語の概要は準備中です。原文の説明を表示しています。
Remote API traps in Kotlin Multiplatform: Ktor clients, defensive parsing, Resource envelopes, OK responses that dropped your data, auth callbacks, retry backoff, downloads, websockets, clock sync. Use when calls succeed but data never lands.
日本語の概要は準備中です。原文の説明を表示しています。
Break large features into independently verifiable, human-reviewable slices under a feature directory in specs/. Use for risky or multi-step feature work that needs upfront questioning, API seams, browser-playable checkpoints, HTML visualizations, screenshot gates, staged implementation plans, recursive fog-of-war reslicing, or proactive research into reference implementations/best practices before slicing. Pairs with your project's verification harness and screenshot gates (the browser checkpoints), [refactor-clean](../refactor-clean/SKILL.md) (review the materialized spec so the plan describes one-owner architecture, not the feature bolted on), [screenshot-critique](../../visual/screenshot-critique/SKILL.md) and [compare-screenshots](../../visual/compare-screenshots/SKILL.md) (the visual gates), and a code-review pass (audit each slice before it lands).
日本語の概要は準備中です。原文の説明を表示しています。
Audit or rewrite AGENTS.md so it holds only lasting principles. Run it only when the user asks for it by name; never invoke it on your own.
日本語の概要は準備中です。原文の説明を表示しています。
Sets up email on the user's own domain, such as hello@yourdomain.com, a real mailbox that sends and receives, with DropTheHassle. Use when the user wants domain email, a professional email address, an inbox like info@ or hello@ on their domain, or asks "can I get email on my domain". Checks the domain is active with site_status, then hands the human a checkout.stripe.com payment link from get_email_checkout_link (main inbox €5 / $5 a month). The agent never pays and never reads the mail.
日本語の概要は準備中です。原文の説明を表示しています。
Publishes (deploys) a built website or web app to a free HTTPS link, then your own .com with no DNS. Use when the user wants to deploy a website, publish a website or host a website, or says "go live", "make it live", "put this live", "put it online", "publish my site", "deploy my website", "host my website", "share it with friends", "send my friends a link", "get a link", "make it public", "it only works on localhost" or "get a .com", or asks to deploy or host a site built with an AI tool (Claude Code, Cursor, Codex, Windsurf, Lovable, Bolt, v0, ChatGPT), or mentions DropTheHassle, and has not picked another host. Covers building first, CLI or MCP setup, deploying, Update and Restore, the claim link, the live check, linking a server part the user hosts on AWS, Google Cloud, DigitalOcean or their own server with set_backend, and domain search. The agent never spends money. The human pays.
日本語の概要は準備中です。原文の説明を表示しています。
Use when your machine does not have JuliaLang runtime
日本語の概要は準備中です。原文の説明を表示しています。
SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO: baseline, diff, and track changes to your on-page SEO. Use when user says "SEO drift", "baseline", "track changes", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", or "deployment check".
日本語の概要は準備中です。原文の説明を表示しています。
How AgentGuards enforces its guardrails in Codex — fully automatic, via hooks, with nothing for you to call. Load this if asked how AgentGuards works, whether you need to screen something yourself, or why no agentguards check_input / authorize_action tools are available.
日本語の概要は準備中です。原文の説明を表示しています。
INVOKE THIS SKILL when your LangGraph needs to persist state, remember conversations, travel through history, or configure subgraph checkpointer scoping. Covers checkpointers, thread_id, time travel, Store, and subgraph persistence modes.
日本語の概要は準備中です。原文の説明を表示しています。
INVOKE THIS SKILL when your Deep Agent needs memory, persistence, or filesystem access. Covers StateBackend (ephemeral), StoreBackend (persistent), FilesystemMiddleware, and CompositeBackend for routing.
日本語の概要は準備中です。原文の説明を表示しています。
A passive daily work journal that Claude keeps FOR you so you never have to write it yourself. Append short entries after meaningful work (what was done, what you focused on, artifacts touched) to 01-daily/journal/YYYY-MM-DD.md. Run a guided reflection at night or in the morning. Use when you run /daily-journal, say "log this to my journal", "add to today's journal", "reflect on today/yesterday", or when finishing a meaningful chunk of work in any session.
日本語の概要は準備中です。原文の説明を表示しています。
Capture durable session learnings, stage for human promotion to 05-knowledge/lizard, and propose skill/CLAUDE.md patches. Triggered by /harvest, SessionEnd hook staging, or nightly enhance. Never writes durable knowledge without your approval.
日本語の概要は準備中です。原文の説明を表示しています。
Personalize COG for your workflow - creates profile, interests, and watchlist files with guided setup (run this first!)
日本語の概要は準備中です。原文の説明を表示しています。
Review generated or changed production code before it ships, using Clean Code, SOLID, DRY, KISS, YAGNI, and LLM-specific failure-mode checks in any programming language. Best used reactively after an agent writes, edits, refactors, or fixes code, before presenting, committing, or merging the result. Use when the user asks "review this PR", "is this safe to merge?", "make this cleaner", "audit this code", "refactor this", "fix this bug", or after a coding agent produced implementation code. Can also guide writing when explicitly invoked before a risky edit. Invoke it on your own initiative the moment you finish writing, editing, or refactoring non-trivial production code, before presenting or committing — don't wait to be asked. DO NOT USE for factual/conceptual questions, CI/tooling config, git workflow, running/debugging tests, pure architecture discussion, prose writing, data analysis, or test-code review (use test-guard).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the model setup, equilibrium concept, or proof architecture is the bottleneck for an American Economic Journal: Microeconomics (AEJ: Micro) manuscript — the central skill for a theory-first paper. Builds the model to the AEJ: Micro bar (clean, general, well-motivated result); it does not check whether your theorem is correct.
日本語の概要は準備中です。原文の説明を表示しています。
Use when assembling the proof appendix and any code/data deposit for an American Economic Journal: Microeconomics (AEJ: Micro) manuscript under the AEA Data and Code Availability Policy. Covers proof appendices for pure theory plus numerical/structural/experimental code; it does not run your estimation.
日本語の概要は準備中です。原文の説明を表示しています。
Daily meeting preparation system that checks your calendar each morning, deeply researches external attendees (LinkedIn, company info, GitHub, past notes), and sends you personalized briefs via email (1 per person). Use when you want automated preparation for upcoming meetings with context about each person you're meeting.
日本語の概要は準備中です。原文の説明を表示しています。
Find quick-win SEO content opportunities by comparing your site's existing content against competitor keyword rankings. Chains site-content-catalog and seo-domain-analyzer to build a content inventory, then identifies gaps — topics competitors rank for that you don't cover yet. Outputs a prioritized list of posts to write or update. Use when a seed/Series A team wants to start winning organic traffic without guessing.
日本語の概要は準備中です。原文の説明を表示しています。
Web scraping with structured data extraction - define your output schema
日本語の概要は準備中です。原文の説明を表示しています。