1.2万 件 ・ 関連度順
概要と使いどころ
Reddit automation skill collection. Supports authentication, content publishing, search & discovery, social interactions, and compound operations. Triggered when a user asks to operate Reddit (post, search, comment, login, analyze, upvote, save).
日本語の概要は準備中です。原文の説明を表示しています。
Reddit content discovery skill. Browse subreddits, search posts, view post details, check user profiles. Triggered when user asks to search Reddit, browse subreddits, view posts, or check users.
日本語の概要は準備中です。原文の説明を表示しています。
Apply or adapt a dual-theme soft-neumorphic UI board for dashboards, workspaces, settings panels, admin tools, and design-system previews. Use when Codex should build or restyle interface work in a tactile soft-neumorphic style with both light and dark themes, shared semantic tokens, large radii, raised surfaces, inset fields, restrained accent states, and a complete preview board covering foundations, controls, navigation, data display, and feedback.
日本語の概要は準備中です。原文の説明を表示しています。
Apply or adapt a complete dual-theme UI specification board for product interfaces. Use when Codex should build or restyle dashboard, admin, workspace, settings, or system UI with both light and dark themes, shared semantic tokens, structured component states, and a full preview board covering foundations, controls, navigation, data display, and feedback patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Save important context to persistent memory for future sessions. PROACTIVELY USE THIS when you detect: - Decisions: "let's go with", "decided to", "chose", "went with" - Learnings: "I learned", "turns out", "TIL", "realized", "discovered" - Errors resolved: "fixed", "the problem was", "solution was" - Client info: names, emails, phone numbers, addresses, invoice amounts - Preferences: "I prefer", "I like", "don't like", "always use" - References: API keys locations, file paths, URLs, credentials - Patterns: "pattern", "convention", "always do", "standard approach" - Important commands run worth remembering Do NOT ask permission - just capture silently when these patterns appear.
日本語の概要は準備中です。原文の説明を表示しています。
Write meaningful Replica tests. Use when adding regression coverage, testing new behavior, or changing existing automated tests.
日本語の概要は準備中です。原文の説明を表示しています。
Review Hub feedback for reusable design themes through discovery, independent judging and synthesis. No diagnosis or optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Create and wire Replica prototype controls. Use when asked to add or change dropdowns, sliders, input fields, toggles or action buttons that configure variants, scenarios, visible UI, app state or data sources, even without canvas terminology. Covers declarations, typed bindings, defaults, conditions, resets and actions. Product UI form fields and filters alone belong to create-prototype.
日本語の概要は準備中です。原文の説明を表示しています。
Shared context template library for setup-skills. Read when discovering context documents or their ownership. This library supplies research inputs, not active product context or a separate authoring workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Safely develop, verify, and document proof-of-concept exploits and payloads for authorized targets inside isolated Workspace Containers. Use when a Hypothesis is well-founded, target authorization covers scope, and each active step will carry a durable approval — for minimal PoCs, impact verification, or reproducible exploit Evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Own the lifecycle of short-lived paid CPU/GPU hosts and attached resources, from bounded provisioning through verified permanent deletion. Use when renting, extending, retiring, or recovering billable remote resources; campaign scheduling belongs to run-ephemeral-hosts.
日本語の概要は準備中です。原文の説明を表示しています。
Passive code-review lane for authorized repositories, local checkouts, uploaded source archives, and diffs. Use when the security research agent needs deterministic candidate discovery before expensive AI investigation, scoped PR-style review, append-only evidence records, or independent revalidation of code findings.
日本語の概要は準備中です。原文の説明を表示しています。
Use common CLI, Kali, and shell tools to inspect web Targets, captured assets, logs, HAR/PCAP files, packages, and generated artifacts, then turn observations into Evidence, Security Signals, and ranked Hypotheses. Use when the user asks for web bug-hunting inspection, digital records, URL maps, crawling, endpoint discovery, JS bundle/package analysis, light forensics, or command-line investigation workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
日本語の概要は準備中です。原文の説明を表示しています。
Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.
日本語の概要は準備中です。原文の説明を表示しています。
The Rembric TUI installer contract — the single, canonical install/setup/upgrade/uninstall path (`apps/plugin/install.sh`, fronted by the repo-root `install.sh` shim). Apply when touching `install.sh`, the root shim, any per-client `install.sh`/`uninstall.sh`, `marketplace.json`, or distribution docs (README, `docs/agents.md`, plugin/client READMEs). Covers the orchestrator model, what must not break, and where the source of truth lives. For running the validation suite, use `rembric-tui-installer-e2e`.
日本語の概要は準備中です。原文の説明を表示しています。
Pragmatic testing guidance focused on confidence, behavior over implementation details, and integration-first coverage. Use when designing a test strategy, writing or reviewing tests, reducing brittle mocks, or deciding what is worth testing in an application or library.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Apply npm/pnpm supply-chain hardening when adding a dependency, editing package.json/.npmrc/pnpm-workspace.yaml, reviewing a lockfile change, or configuring CI install steps. Covers the 17 practices from lirantal/npm-security-best-practices.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically interpret a Medtronic CareLink or MiniMed 780G Daily Review download in a structured 6-step clinical workflow — covering Time in Range, insulin delivery, day/night patterns, hypo and hyperglycemia root causes, and a prioritised action plan. Trigger when a clinician uploads or shares a CareLink report, MiniMed download, 780G Daily Review, pump download, or asks to review a patient's CGM or insulin pump data.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends obtaining serum free T4 and prolactin levels within 1–2 weeks after transsphenoidal surgery (TSS) for Cushing's syndrome to screen for overt hypopituitarism. Use in postoperative Cushing's syndrome patients during the early recovery window when evaluating for new pituitary hormone deficiencies.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends re-evaluating the need for treatment of other pituitary hormone deficiencies in the postoperative period following surgical intervention for Cushing's syndrome. It is triggered when assessing a post-op CS patient for ongoing pituitary function, evaluating for hypopituitarism, or checking HPA axis recovery with morning cortisol/ACTH stimulation tests and pituitary MRI within 1–3 months.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends using biochemical tests to screen for hypercortisolism to detect recurrence in patients with ACTH-dependent Cushing's syndrome after surgical remission. It is triggered during postoperative follow-up when the HPA axis has recovered, annually, or sooner if clinical signs of hypercortisolism (e.g., weight gain, hypertension, glucose intolerance) or abnormal late-night salivary cortisol/UFC appear.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends measuring serum sodium several times during the first 5–14 days after transsphenoidal surgery to detect and manage electrolyte disturbances such as postoperative hyponatremia and diabetes insipidus. Use when managing a post-TSS Cushing’s syndrome patient in the early recovery phase; triggers include postoperative day 5–10 hyponatremia, polyuria, fluid intake‑output imbalance, or suspected diabetes insipidus.
日本語の概要は準備中です。原文の説明を表示しています。