2,416 件 ・ 関連度順
概要と使いどころ
Review a change for security defects such as secret exposure, injection, authentication/authorization failures, unsafe deserialization, and dependency risk. Use for an independent security perspective on a defined change set.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for a hypothetical walkthrough of a system to expose tensions, frictions, gaps, or contradictions between its expected and evidenced flow.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when a human needs to review a Deepline Play result and hand feedback, labels, or approval back to the agent for revision, evaluation, comparison, or bounded iteration. Triggers on “put this run in a Sheet,” “review these results,” “read my feedback,” “make this a standing rule,” “never regress on this case,” “compare these runs,” “keep improving,” or “add the revised run to the same spreadsheet.” Skip ordinary Play authoring or execution with no human review loop, generic spreadsheet work, and one-off CSV export.
日本語の概要は準備中です。原文の説明を表示しています。
DRAFT. Use when running a Luma-centered GTM event campaign: pull/export guests, enrich and score, draft invites and social, stage email+LI sequences paused for approval, and wire registration sync. Not installed by deepline skills.
日本語の概要は準備中です。原文の説明を表示しています。
Read, search, summarize, export, and transcribe a user's own local WeChat 4.x history on macOS or Windows; diagnose setup and re-extract the device key after a WeChat update. Use for WeChat messages, chats, contacts, and local archives. Do not use for remote accounts or devices the user is not authorized to access.
日本語の概要は準備中です。原文の説明を表示しています。
Builds or audits a literature review, producing an evidence map, the closest prior work, source clusters, a gap verdict, and a synthesis plan for the introduction. Use when the user asks whether a contribution is novel, who has studied a question, what the literature establishes, or how to organize a review, or wants a reading list, Zotero export, or pile of papers turned into one. For systematic reviews or meta-analyses it produces the protocol scaffold and routes registration (PROSPERO or OSF) and screening to dedicated tools.
日本語の概要は準備中です。原文の説明を表示しています。
Turns a raw Qualtrics conjoint export into analysis-ready long-format data: implementation identification, reshaping, choice-profile alignment, reference categories, and pilot exclusion. Use when a conjoint CSV needs cleaning, reshaping, or debugging before AMCE estimation.
日本語の概要は準備中です。原文の説明を表示しています。
Designs conjoint and factorial-vignette experiments, covering attribute architecture and randomization restrictions, effective-N power, treatment realism, the choice among AMCE, marginal-mean, and AMIE estimands, forced-choice versus rating designs, and PAP tiers. Use when the user is planning a conjoint, drafting or critiquing an attribute table, asking how many respondents or tasks are needed, whether to report AMCEs or marginal means, or how to test interactions. Reviewing an existing design goes to conjoint-diagnostics, cleaning the export to conjoint-cleaning.
日本語の概要は準備中です。原文の説明を表示しています。
Codified expertise for customs documentation, tariff classification, duty optimization, restricted party screening, and regulatory compliance across multiple jurisdictions. Informed by trade compliance specialists with 15+ years experience. Includes HS classification logic, Incoterms application, FTA utilization, and penalty mitigation. Use when handling customs clearance, tariff classification, trade compliance, import/export documentation, or duty optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Analyses sales call transcripts (and churn or renewal calls) to find why deals are won, lost, kept or churned. Reads each call across six dimensions (product, messaging, sales process, pricing, competition, customer context), pulls verbatim quotes with the speaker named, counts how often each pattern appears, and writes findings with recommendations. Works with any recorder export or pasted text. Triggers: "win/loss analysis", "why do we lose", "why do we win", "analyse these sales calls", "lost deals", "churn analysis", "objection patterns". Feeds /positioning and /messaging. Not for general meeting summaries or competitor research (use /competitor-research).
日本語の概要は準備中です。原文の説明を表示しています。
Create, refine, and manage issues. Use for creating new issues from loose ideas, refining ambiguous issues, bulk operations, or JSON export.
日本語の概要は準備中です。原文の説明を表示しています。
Upload tailored resume to cloud or attach to user session. Handles final formatting and delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Search Haskell APIs using Hoogle. Use when working with Haskell projects to look up function signatures, find functions by type, discover library documentation, or identify which module exports an item.
日本語の概要は準備中です。原文の説明を表示しています。
Work with a Grafana instance — search and read dashboards, run datasource queries (Prometheus, Loki, PostgreSQL, etc.), inspect alert rules and silences, post annotations, and manage folders. Use this whenever the user mentions a Grafana dashboard, panel, or alert; pastes a Grafana URL; asks "what does this dashboard show", "query this metric in Grafana", "is this alert firing", "silence this alert", or wants to create/export a dashboard — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
日本語の概要は準備中です。原文の説明を表示しています。
Search, read, create, update, export, and share files in Google Drive. Use this whenever the user wants to find a file in Drive, read a Google Doc or Sheet, upload a file, move something into a folder, change sharing permissions, or asks "what's in my Drive" — even if they don't say "API". Also use it for any URL under drive.google.com or docs.google.com, or a mention of a Drive file ID. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
日本語の概要は準備中です。原文の説明を表示しています。
Audit AuthCrunch security boundaries, triage vulnerability reports and scanner findings, reproduce authentication or authorization failures, and prepare evidence-backed remediation. Covers trust, credentials, redirects, concurrency, diagnostic logging, and dependency exposure.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain AuthCrunch's YAML HTTP contract, deterministic JSON/YAML exports, Scalar reference and local server. Use after HTTP-facing source/configuration changes, source-review drift, or API reference tooling changes.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain user-owned GPG and SSH public-key parsing, profile API registration, identity database persistence, format compatibility, and maintained OpenPGP dependencies. Excludes portal signing-key publication and admin private-key export.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain portal public signing-key discovery at .well-known/jwks.json, reusable admin API directive parsing, opt-in admin private-key export, KMS key serialization, asymmetric issuer selection, base-path routing, and JWT verification tests. Excludes upstream OAuth provider JWKS consumption.
日本語の概要は準備中です。原文の説明を表示しています。
Activate Specification Know-How: load the SpecBook format contract, the SpecBook schema configuration of the project, and the list of specification (SPEC) artifacts into the context, so the specification can be read, queried, explained, and edited ad-hoc in plain conversation. Use *automatically* whenever the user wants to work with the specification files -- asks what the "spec" or "specification" says, wants to "look up", "query", "check", or "explain" specification content, or wants a small ad-hoc change to it -- and no dedicated specification skill (`ase-spec-edit`, `ase-sync-import`, `ase-sync-reconcile`, `ase-sync-export`) is invoked, as those activate the know-how implicitly.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to audit or harden security in this repo — e.g. "security audit", "auditoría de seguridad", "revisa la seguridad", "is this secure", "hardening", "vulnerabilities". Audits code, config, workflows, and secrets exposure. Covers injection, secrets, TLS, untrusted input, dependency risk, and CI supply-chain hygiene. Runs when the user asks about security, not just for code reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Mobile development intelligence. 12 domains, 9 stacks, 250+ entries. Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check mobile code. Domains: pattern, package, error, perf, test, security, interface, arch, idiom, anti, tooling, dependency. Stacks: flutter, react-native, swiftui, jetpack-compose, kotlin-multiplatform, capacitor, expo, native-ios, native-android. Integrations: arch_system generator.
日本語の概要は準備中です。原文の説明を表示しています。
Convert Kai workflow data, CSV exports, audit folders, SDR package outputs, and marketing reports into dashboard-ready specs or lightweight static dashboards. Use when "data dashboard", "operator dashboard", "operator room", "HTML operators room", "sales dashboard", "SDR dashboard", "turn this data into a dashboard", "dashboard handoff", "visualize Kai data", or any request to package sourced marketing, sales, audit, or SDR data for a dashboard or presentation surface.
日本語の概要は準備中です。原文の説明を表示しています。
Icarus Figures produces publication-grade figures for scientific papers — reproducible matplotlib/seaborn data figures and original TikZ method/framework/architecture figures, held to a four-axis quality bar (depth · elegance · unimpeachable · visible-gap) and exported as editable PDF+PNG+SVG with a runnable critique gate. Use this whenever a figure is destined for a paper, journal, conference submission, thesis, or report — making a plot/chart publication- or journal-ready, building a method/architecture/framework diagram or 技术路线图 (the hero figure a paper opens with), a schematic or workflow figure, or cleaning up a matplotlib/seaborn/TikZ figure that currently looks like a homework plot. Trigger even when the user never says "publication": if the figure goes into a written scientific document, this skill applies.
日本語の概要は準備中です。原文の説明を表示しています。