Showing 61351–61380 of 77200 skills
Search GIF providers with CLI/TUI, download results, and extract stills/sheets.
x402agent/SolanaOS
Query Google Places API (New) via the goplaces CLI for text search, place details, resolve, and reviews. Use for human-friendly place lookup or JSON output for scripts.
x402agent/SolanaOS
Host security hardening and risk-tolerance configuration for SolanaOS deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, SolanaOS cron scheduling for periodic checks, or version status checks on a machine running SolanaOS (laptop, workstation, Pi, VPS).
x402agent/SolanaOS
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.
x402agent/SolanaOS
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
x402agent/SolanaOS
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
x402agent/SolanaOS
Foodora-only CLI for checking past orders and active order status (Deliveroo WIP).
x402agent/SolanaOS
Secure Solana wallet generation using official Solana Labs libraries — Ed25519 keypairs, memory zeroization, vanity address generation, offline-only operation, and multi-language implementations (Rust, TypeScript, Bash).
x402agent/SolanaOS
PumpOS — static HTML/CSS/JS web desktop for the Pump SDK with 169 Pump-Store apps, live token dashboards, interactive DeFi tools, PWA support, and Vercel deployment.
x402agent/SolanaOS
Terminal Spotify playback/search via spogo (preferred) or spotify_player.
x402agent/SolanaOS
Manage Things 3 via the `things` CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks SolanaOS to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
x402agent/SolanaOS
Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).
x402agent/SolanaOS
Review and gate AI-generated code changes by reconstructing intent, mapping diff risk, selecting independent verification, checking security and dependency impact, and requiring evidence before merge or release. Use for coding-agent pull requests, autonomous patches, or large AI-generated diffs; do not use for ordinary implementation requests or style-only review.
CHENG-LIANG1/badass-skills
Audit or improve a code repository's AI-agent harness by making project knowledge discoverable, commands reproducible, architectural invariants executable, and feedback loops fast. Use when preparing a codebase for Codex or other coding agents, investigating inconsistent agent changes, or reviewing AGENTS.md and repository guidance; do not use for ordinary code review or a one-off task with no repository-level issue.
CHENG-LIANG1/badass-skills
Design safe, repeatable agentic automations for scheduled or event-driven work by defining triggers, permissions, idempotency, budgets, review gates, failure handling, and observable proof. Use when creating or reviewing recurring AI-agent workflows, Codex automations, or GitHub Agentic Workflows; do not use for one-off agent tasks or deterministic jobs better handled by a normal script.
CHENG-LIANG1/badass-skills
Preflight consequential agent actions by resolving exact targets, authority, reversibility, retry ambiguity, rollback, and independent verification. Use before destructive, externally visible, bulk, financial, permission, deployment, send, or publish operations; do not use for read-only work or trivial reversible local edits.
CHENG-LIANG1/badass-skills
Diagnose reproducible or intermittent failures in tests, builds, CI, dev servers, CLIs, and integrations by turning symptoms into falsifiable hypotheses and small discriminating experiments. Use when the root cause is unknown; do not use for a routine fix whose cause is already established.
CHENG-LIANG1/badass-skills
Protect AI-agent tasks from indirect prompt injection and untrusted tool output by tracing instruction provenance, separating data from authority, constraining source-to-sink flows, and confirming sensitive disclosure or action. Use when reading webpages, issues, emails, documents, logs, MCP results, or third-party skills while tools can access private data or mutate state; do not use for ordinary trusted inputs with no external-content boundary.
CHENG-LIANG1/badass-skills
Use when a parallel artifact integration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the integration staging plan containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Use when a parallel artifact integration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the integration staging plan with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Use when the parallel artifact integration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the integration staging plan with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Use when the parallel artifact integration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the integration staging plan with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Use when the parallel artifact integration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the integration staging plan with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Use when the parallel artifact integration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the integration staging plan with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Use when a decision about parallel artifact integration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the integration staging plan. Success means each material claim has a source, version/date, location, and confidence note; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Use when a delegated task cancellation propagation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the cancellation propagation check containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; all cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Use when a delegated task cancellation propagation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the cancellation propagation check with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; all cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Use when the delegated task cancellation propagation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the cancellation propagation check with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; all cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Use when the delegated task cancellation propagation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the cancellation propagation check with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; all cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Use when the delegated task cancellation propagation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the cancellation propagation check with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; all cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills