944 件 ・ 関連度順
概要と使いどころ
Verify a BibTeX file for hallucinated or fabricated references by cross-checking every entry against CrossRef, arXiv, and DBLP. Reports each reference as verified, suspect, or not found, with field-level mismatch details (title, authors, year, DOI). Use when the user wants to check a .bib file for fake citations, validate references in a paper, or audit bibliography entries for accuracy.
日本語の概要は準備中です。原文の説明を表示しています。
Assess whether Government of India approval is required for foreign investment in an Indian company under Foreign Exchange Management Act, 1999 and the Non-Debt Instruments Rules, 2019. The skill systematically gathers transaction details, evaluates sectoral entry routes and caps, assesses land border country restrictions under applicable laws, and delivers a preliminary compliance note. Produces clear guidance on whether the investment falls within Automatic Route or requires Government approval.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a litigation chronology from the disclosure bundle itself — every entry attributed to its source document, behind a CPR 31.22 implied-undertaking check, because documents disclosed in English proceedings may only be used for those proceedings. Adds a privilege screen and case-theory significance tagging, so the output is court-facing work product, not a loose timeline. Use when the user asks to build a chronology or timeline from a disclosure bundle, a matter file, or witness statements, or says 'build the chron', 'what happened when', or needs a Statement of Facts ready timeline.
日本語の概要は準備中です。原文の説明を表示しています。
Turn one sentence of intent into tasteful, produced motion. Given a natural-language request like "make a good-looking animated landing page", "add a delightful like animation", or "make a silky release video", this skill classifies the intent, picks the most suitable recipes from the motion-anything library while honoring MOTION-SPEC.md (timing, easing, and the restraint budget), and produces the output. The universal entry point to motion-anything. Works on web pages, slides, app-showcase pages, and video.
日本語の概要は準備中です。原文の説明を表示しています。
Consolidated expert library for professional Godot 4.7+ game and application development. Orchestrates 92 Domain Skills through architectural workflows, anti-pattern catalogs, performance budgets, and Server API patterns. Use when: (1) starting a new Godot project, (2) designing game or app architecture, (3) building entity/component systems, (4) debugging performance or physics issues, (5) choosing between 2D/3D approaches, (6) implementing multiplayer, (7) optimizing draw calls or script time, (8) porting between platforms, (9) migrating from 4.6 to 4.7. Primary entry point for ALL Godot development tasks. Keywords: Godot 4.7, AreaLight3D, HDR, Asset Store, godot-master.
日本語の概要は準備中です。原文の説明を表示しています。
Consolidated expert library for professional Godot 4.7+ game and application development. Orchestrates 92 Domain Skills through architectural workflows, anti-pattern catalogs, performance budgets, and Server API patterns. Use when: (1) starting a new Godot project, (2) designing game or app architecture, (3) building entity/component systems, (4) debugging performance or physics issues, (5) choosing between 2D/3D approaches, (6) implementing multiplayer, (7) optimizing draw calls or script time, (8) porting between platforms, (9) migrating from 4.6 to 4.7. Primary entry point for ALL Godot development tasks. Keywords: Godot 4.7, AreaLight3D, HDR, Asset Store, godot-master.
日本語の概要は準備中です。原文の説明を表示しています。
Best-practices reference for preparing and instrumenting applications on Temps. Covers the app runtime contract (`.temps.yaml` health, HOST/PORT, readiness, SIGTERM, replicas, migrations) and production observability (errors, traces, metrics, logs, analytics, privacy, sampling, cardinality, credential boundaries). Use whenever building or reviewing an app for Temps, configuring health checks, adding telemetry, diagnosing missing/noisy signals, or checking OTLP/Sentry/analytics ingestion. Triggers include "temps best practices", "prepare this app for Temps", ".temps.yaml health", "temps health check", "ignore health checks in otel", "temps observability", "wire up telemetry", and "instrument this app for temps". Prefer focused setup skills for a single SDK. Use temps-cli for executing deploy and resource-management commands.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a project's infrastructure and SaaS stack, then produce a cost report showing what the user currently pays and what they would save by consolidating onto Temps (self-hosted or Temps Cloud). Detects hosting platforms (Vercel, Netlify, Railway, Render, Heroku, Fly.io), analytics (PostHog, Plausible, Mixpanel, Amplitude, Fathom), error tracking (Sentry, Bugsnag, Rollbar, Honeybadger), session replay (LogRocket, FullStory, Hotjar, Highlight), uptime monitoring (Pingdom, UptimeRobot, Better Stack, Checkly), managed databases (Supabase, Neon, PlanetScale, MongoDB Atlas, Upstash, RDS), and transactional email (SendGrid, Postmark, Resend, Mailgun) from dependencies, config files, and env var names. Use when the user wants to: (1) Know how much they would save by switching to Temps, (2) Audit their SaaS/infrastructure spend, (3) Compare their current stack's cost against self-hosting, (4) Decide whether Temps is worth it, (5) Build a business case for consolidating tools. Triggers: "how much would I save", "temps savings", "cost comparison", "audit my stack", "am I overpaying", "saas spend", "calculate savings", "is temps cheaper".
日本語の概要は準備中です。原文の説明を表示しています。
Deep market analysis for iOS/macOS apps including market sizing (TAM/SAM/SOM), growth trends, market maturity, entry barriers, distribution channels, and revenue potential. Use when user asks for market research, market size, market opportunity, growth potential, TAM/SAM/SOM, or market trends.
日本語の概要は準備中です。原文の説明を表示しています。
Generates protocol-based error/crash monitoring with swappable providers (Sentry, Crashlytics). Use when user wants to add crash reporting, error tracking, or production monitoring.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive product research and opportunity analysis for Amazon sellers. Analyzes demand, competition, profit potential, market entry barriers, and validates product ideas. Covers product sourcing, pricing strategy, and go-to-market planning. Use when the user asks about researching a product to sell, validating product ideas, product opportunity analysis, market research for Amazon, competition analysis, profit potential, should I sell this product, product viability, or any general product research questions.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description.
日本語の概要は準備中です。原文の説明を表示しています。
Startup diagnostic router. Use FIRST when a founder doesn't know where to start, has multiple overlapping problems, or asks a vague question like 'what's wrong with my startup', 'why aren't people buying', 'what should I focus on', 'where do I even begin', 'nothing is working'. Routes to the right framework from the 15 available skills — or tells you when no framework fits and you just need to go talk to people. This is the entry point. Use it before reaching for any specific skill.
日本語の概要は準備中です。原文の説明を表示しています。
Write "Top N best..." listicle articles for affiliate marketing with mini-reviews, pricing, pros/cons, and CTAs per entry. Triggers on: "write a best of list", "top 10 [category] tools", "best [product category] article", "roundup post", "listicle about [category]", "write a top tools article", "best [N] alternatives to [product]", "product roundup", "write a tools comparison list", "best software for [use case]", "top picks for [category]".
日本語の概要は準備中です。原文の説明を表示しています。
Check American Airlines AAdvantage balance, elite status, and loyalty points via Patchright. Handles email 2FA with 6-box code entry. Uses persistent browser profiles to skip 2FA on subsequent runs.
日本語の概要は準備中です。原文の説明を表示しています。
First-run setup. Detects configured API keys, points to the local setup-keys script for secure key entry, and shows sample prompts scaled to available tools.
日本語の概要は準備中です。原文の説明を表示しています。
Release a new version of the DevoxxGenie IntelliJ plugin — prompt for the target version, bump it in the build files, write a curated CHANGELOG.md entry and plugin.xml change-notes from the git/PR history since the last tag, build to verify, then commit, tag, and publish a matching GitHub release. Use this whenever the user wants to cut, ship, publish, or tag a new plugin release, bump the version for a release, or asks to "release vX.Y.Z" / "do a release" / "make a new version".
日本語の概要は準備中です。原文の説明を表示しています。
Advanced distributed patterns - event sourcing, CQRS, saga, stream processing, append-only log, exactly-once delivery, sequencer, double-entry ledger, erasure coding, order book, watermarks
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "organize the project rules", "clean up scattered documentation", "把规则迁移到 skills 目录", "优化 skill 路由", "提高 description 命中率", or "减少薄壳重复维护". Activate when a SKILL.md is too large, rules are duplicated across agent entry files, task routing or trigger_examples miss natural user language, or templates / thin shells / validation scripts need drift-resistant maintenance.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly, browser only when a source refuses to be fetched. Counts unpublished calendar entries per property by folding the published ledger against the calendar, and where every property is above its runway threshold it records the counts and exits, which is the normal run. Where a property is low it researches the next block from rank evidence, the topic map, and live result sets, refuses any keyword already targeted, and appends fully specified entries after the last existing block. It is the only writer of the calendar and it never modifies, reorders, or renumbers an existing entry.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, browser only when the property has no publishing route but a screen. Takes the oldest ready draft, resolves its property, and publishes it by that property's own route: a post file plus a registry entry plus a sitemap update plus a build plus a push, or a publishing surface driven through the flow file it owns. It verifies the live URL by loading it, records the published line, and leaves the draft ready on any failure so tomorrow retries it. It publishes one article to one named property and does nothing else outward, ever.
日本語の概要は準備中です。原文の説明を表示しています。
Dung khi can tra loi duoc tai sao khach chon MINH chu khong chon nguoi khac — positioning statement theo Promise + Proof + Path, ma tran khac biet so voi doi thu, category entry points, thap thong diep 3 tang va huong tagline. Kich hoat khi user nhac 'dinh vi thuong hieu', 'positioning', 'USP', 'khac biet voi doi thu', 'tai sao khach chon minh', 'tai dinh vi', 'noi gi de khach nho', 'san pham giong het thi truong'. Khong dung cho — soi doi thu dang lam gi thi dung skill 08-nghien-cuu-doi-thu; giong noi va tu vung khi viet thi dung skill 35-brand-voice; viet cau slogan / headline poster hai lop thi dung skill 74-copy-hai-lop; dong goi goi ban thi dung skill 31-offer-design; ke hoach ra mat san pham thi dung skill 59-go-to-market.
日本語の概要は準備中です。原文の説明を表示しています。
Use when positioning needs defining or sharpening — a statement built on Promise, Proof, and Path, a differentiation matrix against competitors, category entry points, a three-level message hierarchy, and tagline directions. Trigger on 'positioning', 'positioning statement', 'what makes us different', 'USP', 'why should customers choose us over them', 'we sound the same as everyone else'. Also use when the user can list features but not a reason to pick them. Not for — competitor teardown research, see `08-competitor-research-global`; how the brand sounds in writing, see `35-brand-voice-global`; the offer and its value stack, see `31-offer-design-global`; the launch built on it, see `59-go-to-market-global`.
日本語の概要は準備中です。原文の説明を表示しています。
The Atlas engine — turn any goal into a validated PRD and an executable, verified task graph. Brand-name entrypoint; a thin alias for the `go` orchestrator. Use when the user types /prd:atlas, says "I want to build", or asks for a PRD / task-driven build.
日本語の概要は準備中です。原文の説明を表示しています。