Showing 5131–5160 of 10205 skills
Leads Puck lanes: briefs, agent and model choice, landing, branch and worktree cleanup, GPU and build scheduling, settle windows, owner questions, routing findings; review-passes runs reviews.
ByteTerrace/Puck
Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection. Use for research storytelling, contribution framing, paper comparison, figure planning, or research retrospectives. Not an acceptance predictor or a routine grammar/citation formatter.
Adkid-Zephyr/oral-paper-skill
Use when the task involves finding companies, building a target account or TAM list, lookalikes of existing customers, ICP research, company enrichment (firmographics, tech stack, growth), or finding decision-maker contacts at companies. Also use when the user mentions DiscoLike, "companies like X", "find businesses that", prospect lists, or B2B data. Covers MCP server, CLI, Python SDK, and creating the account from the agent, and routes each job to its own skill.
discolike/discolike-skills
Use when the user asks to "find VP Sales contacts at these companies", "get validated work emails", or deliver contacts at scale. Follow the discolike skill's access and spend rules.
discolike/discolike-skills
Create well-formed Agent Skills following the agentskills.io specification. Scaffold directories, write SKILL.md files, bundle scripts, and structure instructions for progressive disclosure. Use when creating a new skill, reviewing skill structure, optimizing a skill description, or setting up evals for skill quality.
urmzd/dotfiles
Chezmoi dotfiles conventions and patterns. Use when modifying dotfiles, adding new managed files, working with chezmoi templates, or syncing agent skills and subagents through agentspec. Do NOT use for installing tools, running doctor, or updating a machine through the `dotfiles` CLI; use manage-machine.
urmzd/dotfiles
Orchestrate multiple agent CLIs (Claude, Codex, Antigravity) via tmux with a shared fleet store, dispatching one guardian subagent per pane. Survey-first: inspects and adopts existing tmux sessions, windows, and agent panes before creating anything new. Use when running a multi-agent session, dispatching parallel work, or coordinating subagents across panes.
urmzd/dotfiles
Scan a folder of git repos and report each repo's local dirty/clean state, ahead/behind divergence from upstream, recent activity, and latest CI run status. Read-only: never commits, pushes, or edits. Defaults to the folder argument or your repo root. Use when checking "what's live", "which repos are dirty", or "repo status across my projects". Sibling skills overlap on folder scanning: do NOT use for "what should I work on next" prioritization (use get-work); do NOT use for a recent-activity-only overview without dirty/CI detail (use status). repo-status is the local dirty/ahead/behind + CI-state report.
urmzd/dotfiles
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
bg-szy/TOP-SKILLS
Build or fix decision-complete code directly, or execute an approved spec with verification; unresolved product/architecture decisions require spec. Keep the current request in this skill; route new requests by their own scope.
leszekgruchala/buddy
Rule independently on a spec's choices or a diff's irreversible-change signals; confirm, overturn, request evidence, or ask the user only for an unrequested breaking, irreversible change or when no option meets the binding constraints. Keep the current request in this skill; route new requests by their own scope.
leszekgruchala/buddy
Creates and edits emails for the Mindbox email editor from a text description. Use when the user asks to create or change an email, describes an email template, or says 'сделай рассылку' / 'make a campaign'. The technical layout is handed over for preview and saving through the companion skill email-ops.
mindbox-cloud/agent-skills
DiscoLike feedback — file a bug report or product feedback with the DiscoLike team as a GitHub issue. Use when the user wants to report a problem with DiscoLike, the skills, the CLI, the MCP server, or the SDK, or says "send feedback", "report this", or "this should work differently".
discolike/discolike-skills
DiscoLike setup — connect the agent to DiscoLike. Use when no DiscoLike MCP tools are visible and `discolike` is not on PATH, when `discolike auth status` or `account usage` fails on auth, when the CLI on PATH is older than 0.4.1, or when the user asks to set up, connect, or log in to DiscoLike. Signs in, or opens an account when there is none.
discolike/discolike-skills
升级pi-agent-core和pi-ai到最新版本
maotoumao/Cebian
在 Codex 桌面端回复中使用大肥鱼、DeepSeek娘及 dsh-meme 图库表情包。安装后首次使用、查看或切换频率、点播斗图或已允许主动配图时使用;授权后默认高频,支持自然语言调档和按需缓存,不用于生图。
CheshireJCat/dafeiyu-skill
The operating doctrine for a Loom worker session — a session dispatched by a manager to implement ONE assigned task on an isolated worktree branch. Load at the start of any worker (Dev / Bugfix / Deep-Dive / etc.) agent. Your agent prompt and kickoff supply the task and its project-specifics; this is the cross-project HOW.
DanielC000/loom
PavedPath Code is the code-focused edition of PavedPath. It helps agents solve software engineering problems by finding proven implementation paths from GitHub repositories, issues, pull requests, discussions, code examples, release notes, and open-source evidence.
Jia-Ethan/pavedpath-code
Deep code review skill. When triggered by '/code-review', '코드 리뷰', 'review this code', or '코드 품질 점검', this skill performs a thorough code quality review with structured findings, severity ratings, and actionable recommendations.
johnfkoo951/cmdspace-plugins
Task decomposition skill. When triggered by '/decompose', '작업 분해', 'break down this task', or '서브태스크로 나눠줘', this skill takes a complex task and recursively decomposes it into atomic, testable subtasks with tier assignments and parallelization opportunities.
johnfkoo951/cmdspace-plugins
Multi-strategy deep code search skill. When triggered by '/deepsearch', '깊은 검색', 'deep search', or '코드 찾아줘', this skill applies multiple search strategies — structural (AST-like pattern), textual (regex), semantic (by meaning), and historical (git history) — to find code that simple grep can't.
johnfkoo951/cmdspace-plugins
Task estimation skill. When triggered by '/estimate', '추정해줘', 'estimate effort', or '이거 얼마나 복잡해?', this skill analyzes a development task and estimates complexity, agent tier distribution, and provides a confidence level for the estimate.
johnfkoo951/cmdspace-plugins
Deep focus mode using a single high-tier agent for complex problems requiring sustained reasoning. When triggered by '/focus', 'focus mode', '집중 모드', or '깊이 생각해줘', this skill dedicates a single Opus-tier agent to one problem without context switching, multi-agent coordination, or parallelization.
johnfkoo951/cmdspace-plugins
Status display and session overview skill. When triggered by '/hud', '상태 표시', 'show status', or '현재 상황', this skill displays a dashboard-style overview of the current project state, active tasks, agent usage, and tier distribution.
johnfkoo951/cmdspace-plugins
Implementation planning skill. When triggered by '/plan', '계획 세워줘', 'create a plan', or '구현 계획', this skill analyzes a development request and produces a structured execution plan with task decomposition, tier assignments, dependency graphs, and time/cost estimates.
johnfkoo951/cmdspace-plugins
Generate AI assistant configuration files for a repository — CLAUDE.md, AGENTS.md, and Cursor rules (.cursor/rules/*.mdc) — from codebase analysis. Use whenever the user wants to create or update CLAUDE.md, AGENTS.md, agent rules, Cursor rules, AI coding assistant configuration, or "onboard AI tools" to a project, even if they only mention one of the file types.
divar-ir/ai-doc-gen
Post-call from Sales Skills by Arrows. Run right after a sales call: finds your most recent call on its own, then drafts the follow-up email in your voice and the CRM update from what was said (next step, stage, competitors mentioned, follow-up tasks with dates) using your CRM's own field names. Nothing goes into the CRM until you approve the exact changes; without CRM write access you get a copy-paste version. Adds resources to send only when the buyer asked for something. Use whenever someone says 'Run my Arrows post-call', 'Run post-call on [company]', 'write the follow-up from my last call', 'update the CRM from that meeting', 'log my call', or wants a recap email, CRM notes or follow-up tasks after a meeting.
ArrowsHQ/arrows-sales-skills
Sales methodology from Sales Skills by Arrows. Puts a team's methodology into Claude (MEDDIC or MEDDPICC, BANT, SPICED, Challenger, Sandler, or their own), or helps pick one, then checks the team against it. Reads the CRM, calls and email and saves arrows-methodology.md for every Sales Skill: each element, what counts as proof, its CRM field, what each stage needs, and what reps should ask. Then a visual report: which wins followed the methodology and which losses didn't, the win rate with and without it, how each part is done on open deals, deals moved ahead without what their stage needs, and a view by rep. Use whenever someone says 'Set up our sales methodology', 'add MEDDPICC to Claude', 'we use BANT, check deals against it', 'we don't have a methodology, help me pick one', 'how is my team doing against MEDDPICC', 'are reps following our methodology', or asks what reps should ask at each stage. For follow-ups and quiet deals, use the process gaps report.
ArrowsHQ/arrows-sales-skills
Setup for Sales Skills by Arrows. Reads the person's CRM, call recordings, email and calendar, then builds the sales profile every Sales Skill uses: their voice (how they write and talk, with real examples by situation), their sales process (stages, methodology, why they win and lose), their buyers and competitors, and how they work. Sales leaders also get team files their reps can add. About 5–10 minutes, two quick replies. Use this whenever someone says 'Build my sales profile', 'Refresh my sales profile' or 'Set up Sales Skills by Arrows', asks how to get Claude set up for themselves or their sales team, asks Claude to learn how they sell or write to buyers, wants the sales skills personalized to them or their team, or wants their team's sales process captured for Claude.
ArrowsHQ/arrows-sales-skills
Win-loss analysis from Sales Skills by Arrows. A deep read of closed deals (every won and lost deal counted, about 25 of each read end to end, calls and email) that answers why the team wins and why it loses: which segments win (size, source, industry, new vs. existing customers), the 3–5 moves that show up on wins and not on losses (with counts) and what's noise, where and why deals really die compared with what the CRM says, who was missing from the buying group on losses, which parts of the sales methodology predict a win, a rep comparison for leaders, and the 3 things to change this quarter. A shareable visual report. Use whenever someone says 'Run my Arrows win-loss analysis', 'why do we win and why do we lose', 'why are we losing deals', 'what do our wins have in common', 'what are our real loss reasons', 'win rate by segment', or wants a win-loss review for a quarterly or board meeting. For open deals slipping right now, use the process gaps report instead.
ArrowsHQ/arrows-sales-skills