Showing 31711–31740 of 77202 skills
Integration skill for Lovable.dev projects. Activates when working with: - Lovable.dev projects with GitHub sync - Supabase Edge Functions that need deployment - Database migrations for Lovable Cloud - Projects with supabase/ directory structure - Any mention of "Lovable", "deploy edge function", "apply migration" Provides exact Lovable prompts for backend operations that can't be done via GitHub alone.
aiskillstore/marketplace
PostgreSQL database documentation - SQL queries, database design, administration, performance tuning, and advanced features. Use when working with PostgreSQL databases, writing SQL, or managing database systems.
aiskillstore/marketplace
Auto-detect network issues and force proxy usage with proxychains4. Use this skill when encountering connection timeouts, DNS failures, or blocked network access. Default proxy is http://127.0.0.1:9910
aiskillstore/marketplace
This skill should be used when analyzing binaries, executables, or bytecode to understand what they do or how they work. Triggers on "binary", "executable", "ELF", "what does this do", "reverse engineer", "disassemble", "decompile", "pyc file", "python bytecode", "analyze binary", "figure out", "marshal". Routes to sub-skills for triage, static analysis, dynamic analysis, synthesis, or tool setup.
aiskillstore/marketplace
This skill should be used to update terminal window title with context. Triggers automatically at session start via hook. Also triggers on topic changes during conversation (debugging to docs, frontend to backend). Updates title with emoji + project + current topic.
aiskillstore/marketplace
Flowcharts are composed of **nodes** (geometric shapes) and **edges** (arrows or lines). The Mermaid code defines how nodes and edges are made and accommodates different arrow types, multi-directional arrows, and any linking to and from subgraphs.
aiskillstore/marketplace
后端开发专家。精通 Node.js/Python/Go/Rust 等后端技术栈,专注于 API 设计、数据库优化、认证授权、微服务架构和性能调优。用于后端服务开发、API 设计和系统架构。
huangwb8/skills
DevOps 与运维专家。精通 CI/CD、容器化、编排、基础设施即代码、监控告警和自动化部署。用于构建高效、可靠的软件交付流水线和运维系统。
huangwb8/skills
文档专家。专注于技术文档编写、API 文档生成、README 优化和文档维护。提供清晰的文档结构、规范的格式和用户友好的内容。
huangwb8/skills
用于规划包含独立任务的实施计划、定义 Agent 角色和依赖,并通过 `parallel-vibe` 统一执行与审查;本角色不直接创建或调度子代理。
huangwb8/skills
安全专家。专注于应用安全、威胁建模、安全合规和数据保护。提供安全审查、漏洞扫描、安全配置和合规检查。用于构建安全可靠的应用系统。
huangwb8/skills
Knit/render R Markdown (.Rmd) to HTML reliably in this repo (auto-bootstrap pandoc, set correct knit_root_dir, and run rmarkdown::render via a Python wrapper).
huangwb8/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
cogni-dao/cogni
Authoritative map of Cogni's AI-agent infrastructure — the substrate that turns a LangGraph graph into a billed, observed, durably-orchestrated, deployable production agent. Use when designing/debugging the graph execution path (InProc vs LangGraph Server), the build-ship-run topology (what's in the app image, how the Temporal worker reaches a graph), evals, or deciding which spec in the sprawling agent/langgraph cluster is authoritative. Routes graph-authoring mechanics to agent-development.md and tool-authoring to tools-authoring.md; this skill owns the infrastructure altitude above them. For all dated status (what's built, InProc↔Server alignment, doc DRY/drift) see agent-infrastructure-scorecard. Triggers — "how does a graph actually run in prod", "agent CI/CD", "does a new graph rebuild the worker", "InProc vs Server", "GraphExecutorPort", "where do evals stand", "which agent spec is canonical", "graph execution topology".
cogni-dao/cogni
Use when setting up, reviewing, or changing Cogni Conductor worktree bootstrap, including .conductor/settings.toml, scripts/conductor-worktree-setup.sh, secret/auth symlinks, and AI launch-pack references for human or AI developers.
cogni-dao/cogni
Investigate ONE specific discrepancy between our wallet's position and a copy-trade target's position on Polymarket. Use whenever the user says 'why are we on the wrong side', 'why is our VWAP off', 'why didn't we mirror that fill', 'delta on market X', 'minimize delta', 'investigate copy-trade gap', '/delta-minimizer', or points at a single market/event on the dashboard and asks what happened. The copy-trade algorithm is known to have fundamental bugs; the skill's job is to find ONE bug, prove it with cited evidence, and stop.
cogni-dao/cogni
Router for 'deploy a node', 'ship my node app', 'deploy to candidate-a, preview or production', 'which nodes exist', 'check deployment status'. A node ships with one call: POST /api/v1/deploy/workloads. Routes each deploy question to the hub guide or skill that owns it.
cogni-dao/cogni
CI/CD architecture reviewer and DevOps advisor for monorepo pipelines, branch workflows, and deployment strategy. Use when reviewing GitHub Actions workflows, designing promotion pipelines, evaluating branch protection, reviewing deploy scripts, auditing CI/CD for anti-patterns, or deciding build/test/deploy strategy. Also triggers for: 'review this workflow', 'is this CI pattern correct', 'branch strategy', 'deploy pipeline design', 'release promotion', 'CI is slow', 'pipeline gap analysis', 'provision', 'deploy script', 'akash', 'where do node apps deploy'.
cogni-dao/cogni
Optimize how developer agents operate through this repo — close feedback loops, surface drift, and record a dated regrade of the Workflow Health Matrix described in `https://cognidao.org/knowledge/eng-agent-workflow-stages` as a hub contribution. Use this skill whenever the user asks to "optimize engineering", "review workflow health", "close feedback loops", "what's slowing us down", "why is the dev loop broken", "regrade the workflow matrix", "are our agents operating cleanly", or anything about agent productivity, syntropy, or drift. Also use it when the user asks how to drive the critical-path reds (validation-block recipes, self-exercise on candidate-a, Loki self-lookup, finalize `deploy_verified`, /idea+/triage rewrite) down to green. **Do NOT** trigger for individual work-item triage or individual PR review — those have `/triage` and `/review-implementation` respectively. This skill is zoomed out, not zoomed in.
cogni-dao/cogni
GitHub App + VCS operations expert for the cogni-template stack. Load this skill when working on anything involving: GitHub App permissions or installation auditing (cogni-node-template, cogni-git-review), VCS tool layer changes (VcsCapability interface, GitHubVcsAdapter, vcs-flight-candidate tool schema), operator flight dispatch debugging (workflow_dispatch permissions, Argo sync, buildSha verify), or wiring VCS flight dispatch end-to-end. Use proactively whenever the user mentions "flight", "flight dispatch", "workflow permissions", "GH_REVIEW_APP", "VcsCapability not configured", "actions:write", or asks to add a workflowRef / VCS tool parameter.
cogni-dao/cogni
Create and manage production Grafana dashboards for real-time visualization of system and application metrics. Use when building monitoring dashboards, visualizing metrics, or creating operational observability interfaces.
cogni-dao/cogni
Identity and authority navigation for Cogni nodes. Use when deciding who a caller is, what a human, AI agent or company may do on a node, or who gets paid. Covers identity, authentication, authorization, authz, login, API keys, principals, agents vs humans, credentials, grants, roles, role rows, RLS, agent tool authority, wallets, beneficiaries, DAO admins, user bindings, OpenFGA vs node SQL grants (@cogni-dao/agent-grants), and any 'who may do what' question. Triggers: 'identity', 'principal', 'agent principal', 'agent credential', 'authorization', 'authz', 'login', 'API key', 'grant', 'role row', 'RLS', 'tool authority', 'beneficiary', 'wallet', 'billing_account_id', 'user_id vs actor_id', 'user_bindings', 'node admin', 'DAO root', 'who may do X', 'agent acts as human', 'delegated access', 'add a permission'. Loads the hub identity-expert and routes to its atoms. Does not restate them.
cogni-dao/cogni
Use this skill whenever the user asks to create, refine, or spawn a lightweight public landing page in the operator Next.js app. It preserves `/` as the canonical operator homepage unless explicitly told otherwise, creates standalone public routes such as `/internship`, reuses the local UI kit and theme tokens, and adds a public form/API only when the page needs intake.
cogni-dao/cogni
Manage which deploy environments (candidate-a / preview / production) a Cogni node lives in, via the operator app: request the env_manager role, owner approves, call the env verb, merge the catalog PR, verify. Use when asked to 'give this node a preview deploy', 'take a node out of preview', 'change a node's env set', or on a 403 authz_denied / 503 authz_unavailable from POST /api/v1/nodes/{id}/envs. Triggers on 'env_manager', 'can_manage_envs', 'env-membership PR', 'catalog envs: line'. Distinct from shipping a build (POST /api/v1/deploy/workloads), provisioning an env (provision-env) and secrets (cicd-secrets-expert).
cogni-dao/cogni
Agentic node setup for Cogni forks. Orchestrates the full lifecycle: DAO formation, payment activation, repo identity, infrastructure provisioning, and deploy verification. Delegates to guide docs for step-by-step details.
cogni-dao/cogni
Take a Cogni node from not-deployed to live-and-validated on candidate-a, as a node-contributor agent: get the developer role (env_manager also works), declare the workload, call POST /api/v1/deploy/workloads with env=candidate-a, prove the served build. Use when asked to 'get my node onto candidate-a', 'deploy node X to candidate-a', 'prove a node deploys e2e'. node-setup births the node first. validate-candidate posts the proof.
cogni-dao/cogni
Use when designing, debugging, or operating the Cogni node formation wizard, node formation PRs, submodule-pinned node repos, child image builds, node deploy calls, or AI-assistant launch handoffs. Route launch execution and E2E proof to node-wizard-scorecard.
cogni-dao/cogni
Use when an agent receives a Cogni node wizard launch pack, takes over a newly published throwaway node, or must prove the node-wizard launch path end-to-end across child customization PR, child CI/image, parent pin, operator flight request, and candidate /version verification.
cogni-dao/cogni
The standard for adding observability to a Cogni node's code — what to log, the event registry, nodeId, metric labels, privacy, and the pre-ship self-check. Use whenever you add or review a route / feature / adapter and must instrument it (logs or metrics) before shipping, or when asked "how do I add proper observability / logging / metrics here", "is this instrumented right", or "review the observability on this PR". The contract lives in the operator knowledge hub, not in this file.
cogni-dao/cogni
Use whenever working on Cogni USDC credit top-ups, payment intent creation, payment activation, operator wallet funding, 0xSplits allocations, x402 outbound provider payments, Hyperbolic, EIP-3009 signatures, retired OpenRouter/Coinbase top-ups, system-tenant revenue share, repo-spec payment config, live payment rail guards, payment CI failures, or debugging money-loop behavior. Trigger on phrases like payments, payment rail, credits top-up, USDC, Split, 0xSplits, splitHash, x402, Hyperbolic, facilitator, signX402Payment, EIP-3009, OpenRouter funding, Coinbase Commerce, operator wallet, Privy wallet, markup_factor, revenue_share, system bonus, provider top-up, settlement_skipped, SPLIT_CONFIG_MISMATCH, activate payments, node payments, or "is this payment behavior validated". This skill is the launching point for future payments work and debugging.
cogni-dao/cogni