GITHUB AGENT SKILLS / 技能收录

给你的 AI 助手
装上专业技能

我们从 GitHub 持续收录、审核并分类优质的 Agent Skills,按职业与使用场景整理,复制一行命令即可安装到 Claude Code、Cursor 等智能体。

01 /

按职业浏览 Agent Skills

为不同岗位挑选的高频技能

全部职业
02 /

按使用场景浏览 Agent Skills

从你要完成的任务出发

全部场景
03 /

按创作者浏览 Agent Skills

按 GitHub Stars 排序的优秀创作者

全部创作者

全部 Skills 482556

joshuamschultz
joshuamschultz/Arc

readwise_reader

When and how to use the Readwise Reader connector — searching saved documents and highlights, walking a location or tag, and why saving a URL is treated as sending data out. TRIGGER when a request mentions the reading list, something saved to Reader, a highlight, or an article to save for later. SKIP for live web search; this connection reads a saved library.

★ 3
joshuamschultz
joshuamschultz/Arc

postgresql

Use the PostgreSQL/Supabase connector to inspect approved schemas and make bounded typed reads. Trigger for connected database questions; skip for writes, migrations, or raw SQL.

后端与接口
★ 3
joshuamschultz
joshuamschultz/Arc

onepassword

When and how to use the 1Password connector — listing what credentials exist, reading an item's non-secret fields, and resolving a single op:// reference when a secret value is genuinely needed. TRIGGER when a request needs to know which credential exists, or needs one specific secret to complete a task the operator asked for. SKIP for storing, changing, or deleting anything; this connection only reads, and only one vault.

★ 3
joshuamschultz
joshuamschultz/Arc

microsoft365

When and how to use the Microsoft 365 connector — reading Outlook mail, answering calendar questions with a time window, finding OneDrive files, and treating sending mail or inviting attendees as outbound acts. TRIGGER when a request names Outlook, an Exchange mailbox, a Teams-adjacent calendar, or a OneDrive file. SKIP for Google Workspace, and for the rest of Microsoft Graph, which this connection does not expose.

★ 3
joshuamschultz
joshuamschultz/Arc

jira

When and how to use the Jira connector — writing JQL that finds the issue, reading one issue by key, and treating issue creation and comments as things other people will see. TRIGGER when a request names a Jira ticket, a project, a sprint, an assignee's workload, or asks to file or comment on an issue. SKIP for Confluence pages and for Jira administration, which this connection does not expose.

★ 3
joshuamschultz
joshuamschultz/Arc

google_workspace

When and how to use the Google Workspace connector's verbs — which one answers a Gmail, Drive, or Calendar question, how --account routes between connected Google accounts, and why drafting is the default instead of sending. TRIGGER when a request names email, a Google Doc or Drive file, a meeting, or somebody's availability. SKIP for non-Google mail and files, and for anything the connector has no verb for.

★ 3
joshuamschultz
joshuamschultz/Arc

github

When and how to use the GitHub connector's read verbs — which listing answers a question about pull requests, issues, releases, or CI, and how to use the search argument instead of fetching everything. TRIGGER when a request names a repository, a PR, an issue, a release, or whether CI is green. SKIP for anything that writes to GitHub; this connection has no write verbs.

★ 3
joshuamschultz
joshuamschultz/Arc

dropbox

How to browse, read, and write a connected Dropbox account — listing and searching by path, downloading a file's text, and the four writes (upload, create-folder, move, delete) that change the account. TRIGGER when a request asks what is in Dropbox, to read a Dropbox file, or to put, move, or remove one. SKIP when no Dropbox connection is granted, or for binary files whose bytes are not text.

★ 3
joshuamschultz
joshuamschultz/Arc

confluence

When and how to use the Confluence connector — writing CQL that finds the page, reading a page's body, and why publishing or replacing a page is publication to that space's audience. TRIGGER when a request names a wiki page, a space, documentation, or asks to write something up. SKIP for Jira issues and for Confluence administration, which this connection does not expose.

★ 3
joshuamschultz
joshuamschultz/Arc

composio

When and how to use the Composio connector — searching Composio's catalog of integrations, listing toolkits and triggers, and reading one tool's schema. TRIGGER when a request asks what integrations or actions are available through Composio, or to look up a Composio tool by name. SKIP for actually performing an action in a third-party app (this connection grants discovery verbs only) and for connectors Arc integrates directly.

★ 3
joshuamschultz
joshuamschultz/Arc

strategy

Hold the long arc as an auditable record of bets and beliefs — append-only markdown cards under workspace/strategy/ for theses, assumptions, decisions, and signals, cross-linked by [[slug]] so a thesis resolves to the assumptions holding it up and the signals pressing on it. TRIGGER: a strategic bet stated or revised, an assumption named, a competitor or market signal noticed, a consequential decision made, or a request to review the strategy book. SKIP: operational commitments with an owner and a due date (that is ops) and day-to-day choices with no horizon.

★ 3
joshuamschultz
joshuamschultz/Arc

decision-brief

Turn a pending choice into a decision brief — what would have to be true, the strongest case against, reversibility, and a named recommendation with its cost. TRIGGER: a decision is on the table ('should we move upmarket', 'do we take the raise', 'pick between A and B'). SKIP: auditing whether existing beliefs still hold (use assumption-audit) or reading what competitors did (use competitive-read).

★ 3
joshuamschultz
joshuamschultz/Arc

competitive-read

Synthesize accumulated market and competitor signals into what actually changed, which placed bets it presses on, and what it would take to be wrong. TRIGGER: 'what are competitors doing', 'what changed in the market', or a batch of signals worth reading together. SKIP: deciding a specific pending choice (use decision-brief) or auditing internal beliefs against evidence (use assumption-audit).

★ 3
joshuamschultz
joshuamschultz/Arc

assumption-audit

Sweep every active thesis for assumptions that have been contradicted, never tested, or quietly expired, and report which bets are now resting on nothing. TRIGGER: a strategy review, a quarterly planning session, or 'is what we believe still true'. SKIP: deciding a specific pending choice (use decision-brief) or logging what a competitor just did (use competitive-read).

★ 3
joshuamschultz
joshuamschultz/Arc

pre-call-brief

Assemble a one-page pre-call brief for a sales conversation from CRM memory — who is on the call, the deal's state, history, open commitments, and the one outcome to drive. TRIGGER: the executive has a call/meeting coming up ('prep me for the Acme call', 'what do I need before the Northwind QBR', 'brief me on Jane'). SKIP: reviewing a deal's health for forecasting (use deal-review) or sweeping overdue follow-ups across the book (use follow-up-sweep).

★ 3
joshuamschultz
joshuamschultz/Arc

follow-up-sweep

Sweep the whole book for dropped balls — commitments due or overdue, deals with no scheduled next step, and champions gone quiet — and return a ranked action list. Powers the morning briefing. TRIGGER: 'what am I forgetting?', 'what's overdue?', the daily briefing, or a weekly pipeline hygiene pass. SKIP: prepping one specific call (use pre-call-brief) or judging a single deal's health in depth (use deal-review).

★ 3
joshuamschultz
joshuamschultz/Arc

deal-review

Assess one deal's health and produce a candid verdict — is it real, where is the risk, and what is the single next action to de-risk it. Scores momentum, multi-threading, and stage fit against the account history in memory. TRIGGER: 'is the Northwind deal real?', 'review my pipeline', forecast prep, or a deal that has gone quiet. SKIP: preparing for a specific upcoming call (use pre-call-brief) or listing overdue follow-ups across every account (use follow-up-sweep).

★ 3
joshuamschultz
joshuamschultz/Arc

crm

Maintain the revenue book of business — contacts, companies, deals, meetings, commitments — as append-only cards under workspace/crm/, and read the open pipeline back. Card writing runs through scripts/crm.py so slugs, timestamps, links and append semantics are exact; this skill supplies the judgement about what to log. TRIGGER: any mention of a person, account, deal, meeting outcome, or promise made either way ('log this', 'we agreed to', 'they moved to procurement'), and any request for the pipeline. SKIP: judging whether a deal is healthy (use deal-review), preparing for a specific call (use pre-call-brief), or listing what is overdue across accounts (use follow-up-sweep) — those READ these cards, they do not write them.

★ 3