opencode-skills-collection 3.0.20 → 3.0.22
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bundled-skills/.antigravity-install-manifest.json +3 -1
- package/bundled-skills/docs/integrations/jetski-cortex.md +3 -3
- package/bundled-skills/docs/integrations/jetski-gemini-loader/README.md +1 -1
- package/bundled-skills/docs/maintainers/repo-growth-seo.md +3 -3
- package/bundled-skills/docs/maintainers/skills-update-guide.md +1 -1
- package/bundled-skills/docs/users/bundles.md +1 -1
- package/bundled-skills/docs/users/claude-code-skills.md +1 -1
- package/bundled-skills/docs/users/gemini-cli-skills.md +1 -1
- package/bundled-skills/docs/users/getting-started.md +1 -1
- package/bundled-skills/docs/users/kiro-integration.md +1 -1
- package/bundled-skills/docs/users/usage.md +4 -4
- package/bundled-skills/docs/users/visual-guide.md +4 -4
- package/bundled-skills/linux-privilege-escalation/SKILL.md +5 -4
- package/bundled-skills/mercury-mcp/SKILL.md +126 -0
- package/bundled-skills/photopea-embedded-editor/SKILL.md +1399 -0
- package/package.json +4 -4
- package/skills_index.json +44 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schemaVersion": 1,
|
|
3
|
-
"updatedAt": "2026-05-
|
|
3
|
+
"updatedAt": "2026-05-21T02:01:54.554Z",
|
|
4
4
|
"entries": [
|
|
5
5
|
"00-andruia-consultant",
|
|
6
6
|
"007",
|
|
@@ -860,6 +860,7 @@
|
|
|
860
860
|
"memory-safety-patterns",
|
|
861
861
|
"memory-systems",
|
|
862
862
|
"mental-health-analyzer",
|
|
863
|
+
"mercury-mcp",
|
|
863
864
|
"mermaid-expert",
|
|
864
865
|
"metasploit-framework",
|
|
865
866
|
"micro-saas-launcher",
|
|
@@ -997,6 +998,7 @@
|
|
|
997
998
|
"performance-testing-review-multi-agent-review",
|
|
998
999
|
"personal-tool-builder",
|
|
999
1000
|
"phase-gated-debugging",
|
|
1001
|
+
"photopea-embedded-editor",
|
|
1000
1002
|
"php-pro",
|
|
1001
1003
|
"pipecat-friday-agent",
|
|
1002
1004
|
"pipedrive-automation",
|
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
---
|
|
2
2
|
title: Jetski/Cortex + Gemini Integration Guide
|
|
3
|
-
description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,
|
|
3
|
+
description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,462+ skills."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
# Jetski/Cortex + Gemini: safe integration with 1,
|
|
6
|
+
# Jetski/Cortex + Gemini: safe integration with 1,462+ skills
|
|
7
7
|
|
|
8
8
|
This guide shows how to integrate the `antigravity-awesome-skills` repository with an agent based on **Jetski/Cortex + Gemini** (or similar frameworks) **without exceeding the model context window**.
|
|
9
9
|
|
|
@@ -23,7 +23,7 @@ Never do:
|
|
|
23
23
|
- concatenate all `SKILL.md` content into a single system prompt;
|
|
24
24
|
- re-inject the entire library for **every** request.
|
|
25
25
|
|
|
26
|
-
With 1,
|
|
26
|
+
With 1,462+ skills, this approach fills the context window before user messages are even added, causing truncation.
|
|
27
27
|
|
|
28
28
|
---
|
|
29
29
|
|
|
@@ -21,7 +21,7 @@ This example shows one way to integrate **antigravity-awesome-skills** with a Je
|
|
|
21
21
|
- How to enforce a **maximum number of skills per turn** via `maxSkillsPerTurn`.
|
|
22
22
|
- How to choose whether to **truncate or error** when too many skills are requested via `overflowBehavior`.
|
|
23
23
|
|
|
24
|
-
This pattern avoids context overflow when you have 1,
|
|
24
|
+
This pattern avoids context overflow when you have 1,462+ skills installed.
|
|
25
25
|
|
|
26
26
|
Manifest contract references:
|
|
27
27
|
|
|
@@ -6,7 +6,7 @@ This document keeps the repository's GitHub-facing discovery copy aligned with t
|
|
|
6
6
|
|
|
7
7
|
Preferred positioning:
|
|
8
8
|
|
|
9
|
-
> Installable GitHub library of 1,
|
|
9
|
+
> Installable GitHub library of 1,462+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
|
|
10
10
|
|
|
11
11
|
Key framing:
|
|
12
12
|
|
|
@@ -20,7 +20,7 @@ Key framing:
|
|
|
20
20
|
|
|
21
21
|
Preferred description:
|
|
22
22
|
|
|
23
|
-
> Installable GitHub library of 1,
|
|
23
|
+
> Installable GitHub library of 1,462+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
|
|
24
24
|
|
|
25
25
|
Preferred homepage:
|
|
26
26
|
|
|
@@ -28,7 +28,7 @@ Preferred homepage:
|
|
|
28
28
|
|
|
29
29
|
Preferred social preview:
|
|
30
30
|
|
|
31
|
-
- use a clean preview image that says `1,
|
|
31
|
+
- use a clean preview image that says `1,462+ Agentic Skills`;
|
|
32
32
|
- mention Claude Code, Cursor, Codex CLI, and Gemini CLI;
|
|
33
33
|
- avoid dense text and tiny logos that disappear in social cards.
|
|
34
34
|
|
|
@@ -72,7 +72,7 @@ The update process refreshes:
|
|
|
72
72
|
- Canonical skills index (`skills_index.json`)
|
|
73
73
|
- Compatibility mirror (`data/skills_index.json`)
|
|
74
74
|
- Web app skills data (`apps\web-app\public\skills.json`)
|
|
75
|
-
- All 1,
|
|
75
|
+
- All 1,462+ skills from the skills directory
|
|
76
76
|
|
|
77
77
|
## When to Update
|
|
78
78
|
|
|
@@ -12,7 +12,7 @@ Install the library into Claude Code, then invoke focused skills directly in the
|
|
|
12
12
|
|
|
13
13
|
## Why use this repo for Claude Code
|
|
14
14
|
|
|
15
|
-
- It includes 1,
|
|
15
|
+
- It includes 1,462+ skills instead of a narrow single-domain starter pack.
|
|
16
16
|
- It supports the standard `.claude/skills/` path and the Claude Code plugin marketplace flow.
|
|
17
17
|
- It also ships generated bundle plugins so teams can install focused packs like `Essentials` or `Security Developer` from the marketplace metadata.
|
|
18
18
|
- It includes onboarding docs, bundles, and workflows so new users do not need to guess where to begin.
|
|
@@ -12,7 +12,7 @@ Install into the Gemini skills path, then ask Gemini to apply one skill at a tim
|
|
|
12
12
|
|
|
13
13
|
- It installs directly into the expected Gemini skills path.
|
|
14
14
|
- It includes both core software engineering skills and deeper agent/LLM-oriented skills.
|
|
15
|
-
- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,
|
|
15
|
+
- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,462+ files.
|
|
16
16
|
- It is useful whether you want a broad internal skill library or a single repo to test many workflows quickly.
|
|
17
17
|
|
|
18
18
|
## Install Gemini CLI Skills
|
|
@@ -18,7 +18,7 @@ Kiro is AWS's agentic AI IDE that combines:
|
|
|
18
18
|
|
|
19
19
|
Kiro's agentic capabilities are enhanced by skills that provide:
|
|
20
20
|
|
|
21
|
-
- **Domain expertise** across 1,
|
|
21
|
+
- **Domain expertise** across 1,462+ specialized areas
|
|
22
22
|
- **Best practices** from Anthropic, OpenAI, Google, Microsoft, and AWS
|
|
23
23
|
- **Workflow automation** for common development tasks
|
|
24
24
|
- **AWS-specific patterns** for serverless, infrastructure, and cloud architecture
|
|
@@ -14,7 +14,7 @@ If you came in through a **Claude Code** or **Codex** plugin instead of a full l
|
|
|
14
14
|
|
|
15
15
|
When you ran `npx antigravity-awesome-skills` or cloned the repository, you:
|
|
16
16
|
|
|
17
|
-
✅ **Downloaded 1,
|
|
17
|
+
✅ **Downloaded 1,462+ skill files** to your computer (default: `~/.gemini/antigravity/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
|
|
18
18
|
✅ **Made them available** to your AI assistant
|
|
19
19
|
❌ **Did NOT enable them all automatically** (they're just sitting there, waiting)
|
|
20
20
|
|
|
@@ -34,7 +34,7 @@ Bundles are **curated groups** of skills organized by role. They help you decide
|
|
|
34
34
|
|
|
35
35
|
**Analogy:**
|
|
36
36
|
|
|
37
|
-
- You installed a toolbox with 1,
|
|
37
|
+
- You installed a toolbox with 1,462+ tools (✅ done)
|
|
38
38
|
- Bundles are like **labeled organizer trays** saying: "If you're a carpenter, start with these 10 tools"
|
|
39
39
|
- You can either **pick skills from the tray** or install that tray as a focused marketplace bundle plugin
|
|
40
40
|
|
|
@@ -212,7 +212,7 @@ Let's actually use a skill right now. Follow these steps:
|
|
|
212
212
|
|
|
213
213
|
## Step 5: Picking Your First Skills (Practical Advice)
|
|
214
214
|
|
|
215
|
-
Don't try to use all 1,
|
|
215
|
+
Don't try to use all 1,462+ skills at once. Here's a sensible approach:
|
|
216
216
|
|
|
217
217
|
If you want a tool-specific starting point before choosing skills, use:
|
|
218
218
|
|
|
@@ -343,7 +343,7 @@ Usually no, but if your AI doesn't recognize a skill:
|
|
|
343
343
|
|
|
344
344
|
### "Can I load all skills into the model at once?"
|
|
345
345
|
|
|
346
|
-
No. Even though you have 1,
|
|
346
|
+
No. Even though you have 1,462+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
|
|
347
347
|
|
|
348
348
|
The intended pattern is:
|
|
349
349
|
|
|
@@ -34,7 +34,7 @@ antigravity-awesome-skills/
|
|
|
34
34
|
├── 📄 CONTRIBUTING.md ← Contributor workflow
|
|
35
35
|
├── 📄 CATALOG.md ← Full generated catalog
|
|
36
36
|
│
|
|
37
|
-
├── 📁 skills/ ← 1,
|
|
37
|
+
├── 📁 skills/ ← 1,462+ skills live here
|
|
38
38
|
│ │
|
|
39
39
|
│ ├── 📁 brainstorming/
|
|
40
40
|
│ │ └── 📄 SKILL.md ← Skill definition
|
|
@@ -47,7 +47,7 @@ antigravity-awesome-skills/
|
|
|
47
47
|
│ │ └── 📁 2d-games/
|
|
48
48
|
│ │ └── 📄 SKILL.md ← Nested skills also supported
|
|
49
49
|
│ │
|
|
50
|
-
│ └── ... (1,
|
|
50
|
+
│ └── ... (1,462+ total)
|
|
51
51
|
│
|
|
52
52
|
├── 📁 apps/
|
|
53
53
|
│ └── 📁 web-app/ ← Interactive browser
|
|
@@ -100,7 +100,7 @@ antigravity-awesome-skills/
|
|
|
100
100
|
|
|
101
101
|
```
|
|
102
102
|
┌─────────────────────────┐
|
|
103
|
-
│ 1,
|
|
103
|
+
│ 1,462+ SKILLS │
|
|
104
104
|
└────────────┬────────────┘
|
|
105
105
|
│
|
|
106
106
|
┌────────────────────────┼────────────────────────┐
|
|
@@ -201,7 +201,7 @@ If you want a workspace-style manual install instead, cloning into `.agent/skill
|
|
|
201
201
|
│ ├── 📁 brainstorming/ │
|
|
202
202
|
│ ├── 📁 stripe-integration/ │
|
|
203
203
|
│ ├── 📁 react-best-practices/ │
|
|
204
|
-
│ └── ... (1,
|
|
204
|
+
│ └── ... (1,462+ total) │
|
|
205
205
|
└─────────────────────────────────────────┘
|
|
206
206
|
```
|
|
207
207
|
|
|
@@ -9,8 +9,6 @@ date_added: "2026-02-27"
|
|
|
9
9
|
|
|
10
10
|
> AUTHORIZED USE ONLY: Use this skill only for authorized security assessments, defensive validation, or controlled educational environments.
|
|
11
11
|
|
|
12
|
-
<!-- security-allowlist: curl-pipe-bash -->
|
|
13
|
-
|
|
14
12
|
# Linux Privilege Escalation
|
|
15
13
|
|
|
16
14
|
## Purpose
|
|
@@ -145,8 +143,11 @@ echo $PATH
|
|
|
145
143
|
Deploy automated scripts for comprehensive enumeration:
|
|
146
144
|
|
|
147
145
|
```bash
|
|
148
|
-
# LinPEAS
|
|
149
|
-
curl -L https://github.com/carlospolop/PEASS-ng/releases/latest/download/linpeas.sh
|
|
146
|
+
# LinPEAS: download first, inspect the script, then execute only in an authorized lab
|
|
147
|
+
curl -L -o linpeas.sh https://github.com/carlospolop/PEASS-ng/releases/latest/download/linpeas.sh
|
|
148
|
+
less linpeas.sh
|
|
149
|
+
chmod +x linpeas.sh
|
|
150
|
+
./linpeas.sh
|
|
150
151
|
|
|
151
152
|
# LinEnum
|
|
152
153
|
./LinEnum.sh -t
|
|
@@ -0,0 +1,126 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: mercury-mcp
|
|
3
|
+
description: "Cheatsheet for the Mercury (proton) MCP tools. Use when connected to the Mercury MCP server to look up which mercury_* tool to call for messaging teammates, threads, tasks, automations, or admin team-graph edits."
|
|
4
|
+
risk: safe
|
|
5
|
+
source: community
|
|
6
|
+
date_added: "2026-05-19"
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Mercury MCP tool cheatsheet
|
|
10
|
+
|
|
11
|
+
## Overview
|
|
12
|
+
|
|
13
|
+
The Mercury MCP server lets an MCP-compatible agent — Claude Code, Codex,
|
|
14
|
+
Cursor, or your own — act as a member of a Mercury team. It is built by
|
|
15
|
+
[mercury.build](https://mercury.build), the team behind
|
|
16
|
+
[TeamOffsite](https://teamoffsite.ai). Once an agent is connected, the client
|
|
17
|
+
exposes a set of `mercury_*` tools for messaging teammates, managing threads
|
|
18
|
+
and tasks, and scheduling automations.
|
|
19
|
+
|
|
20
|
+
This skill is a lookup reference for those tools. It does not change how the
|
|
21
|
+
agent works — it tells the agent which tool does what, so it picks the right
|
|
22
|
+
one without guessing.
|
|
23
|
+
|
|
24
|
+
## When to Use This Skill
|
|
25
|
+
|
|
26
|
+
- Use when your agent is connected to the Mercury MCP server and you need to
|
|
27
|
+
pick the right `mercury_*` tool.
|
|
28
|
+
- Use when messaging teammates, or reading, listing, or posting to threads.
|
|
29
|
+
- Use when creating, updating, or closing tasks.
|
|
30
|
+
- Use when scheduling or editing recurring automations.
|
|
31
|
+
- Use when an org admin needs to inspect or edit the team graph (agents and edges).
|
|
32
|
+
|
|
33
|
+
## How It Works
|
|
34
|
+
|
|
35
|
+
### Step 1: Connect to the Mercury MCP server
|
|
36
|
+
|
|
37
|
+
The server is a JSON-RPC 2.0 endpoint.
|
|
38
|
+
|
|
39
|
+
- Endpoint: `POST https://api.mercury.build/api/v1/mcp`
|
|
40
|
+
- Auth: per-agent header `x-api-key: ak_agent_...`
|
|
41
|
+
|
|
42
|
+
For Claude Code:
|
|
43
|
+
|
|
44
|
+
```
|
|
45
|
+
claude mcp add --transport http --scope user \
|
|
46
|
+
mercury https://api.mercury.build/api/v1/mcp \
|
|
47
|
+
-H "x-api-key: ak_agent_..."
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
### Step 2: Use the core tools
|
|
51
|
+
|
|
52
|
+
Every connected agent gets these.
|
|
53
|
+
|
|
54
|
+
| Tool | When to call it |
|
|
55
|
+
| --- | --- |
|
|
56
|
+
| `mercury_list_agents` | List the agents you can message (the agents you have edges with). |
|
|
57
|
+
| `mercury_send_message` | Send a message to one agent. Auto-threads onto an existing task or opens a new thread. |
|
|
58
|
+
| `mercury_wait_for_messages` | Long-poll for new messages addressed to you, up to 60s per call. |
|
|
59
|
+
| `mercury_read_thread` | Read a thread's full message history by thread ID. |
|
|
60
|
+
| `mercury_list_threads` | List every active thread across your edges. |
|
|
61
|
+
| `mercury_update_status` | Set the visible "currently doing X" status teammates see in the UI. |
|
|
62
|
+
| `mercury_post_activity` | Post a metadata-only activity card to a thread, no message delivered. |
|
|
63
|
+
| `mercury_create_task` | Create a multi-step task with a plan array, linked to its originating thread. |
|
|
64
|
+
| `mercury_update_task` | Append notes, tick off plan steps, or rename a task. |
|
|
65
|
+
| `mercury_close_task` | Close a finished task with a one-paragraph summary. |
|
|
66
|
+
| `mercury_list_tasks` | Query open or all tasks for the current agent. |
|
|
67
|
+
| `mercury_create_automation` | Schedule a recurring message via 5-field cron (IANA timezones supported). |
|
|
68
|
+
| `mercury_list_automations` | List every recurring automation in your team. |
|
|
69
|
+
| `mercury_update_automation` | Change an automation's schedule, content, or enabled state. |
|
|
70
|
+
| `mercury_delete_automation` | Remove an automation. |
|
|
71
|
+
| `mercury_get_agent_context` | Return your own identity, role, system prompt, edges, tasks, and toolkits. |
|
|
72
|
+
|
|
73
|
+
### Step 3: Use admin tools (admin scope only)
|
|
74
|
+
|
|
75
|
+
Available only to agents whose org membership grants admin scope. These edit
|
|
76
|
+
the team graph itself. A permission error here means your agent does not have
|
|
77
|
+
admin scope — that is expected, not a bug.
|
|
78
|
+
|
|
79
|
+
| Tool | When to call it |
|
|
80
|
+
| --- | --- |
|
|
81
|
+
| `mercury_admin_list_team_agents` | List every agent on a team. |
|
|
82
|
+
| `mercury_admin_list_team_edges` | List every edge on a team. |
|
|
83
|
+
| `mercury_admin_get_agent_details` | Read an agent's full config: model, role, system prompt. |
|
|
84
|
+
| `mercury_admin_list_team_humans` | List the humans on a team. |
|
|
85
|
+
| `mercury_admin_create_agent` | Create a new agent on a team. |
|
|
86
|
+
| `mercury_admin_update_agent` | Update an agent's name, role, prompt, or model. |
|
|
87
|
+
| `mercury_admin_delete_agent` | Delete an agent. Cascades to its edges. |
|
|
88
|
+
| `mercury_admin_create_edge` | Connect two agents with a new edge. |
|
|
89
|
+
| `mercury_admin_update_edge` | Rename or retopologize an edge. |
|
|
90
|
+
|
|
91
|
+
## Examples
|
|
92
|
+
|
|
93
|
+
### Example 1: Orient yourself, then message a teammate
|
|
94
|
+
|
|
95
|
+
```
|
|
96
|
+
mercury_get_agent_context # learn your identity, edges, and open tasks
|
|
97
|
+
mercury_list_agents # see who you can message
|
|
98
|
+
mercury_send_message # send to one agent (auto-threads)
|
|
99
|
+
mercury_wait_for_messages # long-poll up to 60s for the reply
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
### Example 2: Create and track a task
|
|
103
|
+
|
|
104
|
+
```
|
|
105
|
+
mercury_create_task # open a multi-step task with a plan array
|
|
106
|
+
mercury_update_task # tick off plan steps / append notes as you go
|
|
107
|
+
mercury_close_task # close it with a one-paragraph summary
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
## Best Practices
|
|
111
|
+
|
|
112
|
+
- ✅ Call `mercury_get_agent_context` first — it returns your identity, edges, tasks, and toolkits in one call.
|
|
113
|
+
- ✅ Long-poll with `mercury_wait_for_messages` instead of busy-looping `mercury_list_threads`.
|
|
114
|
+
- ✅ Stay under the rate limit: outbound agent-to-agent messages are throttled to 8 sends per 30s per agent to prevent runaway loops.
|
|
115
|
+
- ❌ Don't assume admin tools are available — a permission error means your agent lacks admin scope, which is expected.
|
|
116
|
+
|
|
117
|
+
## Limitations
|
|
118
|
+
|
|
119
|
+
- This skill is a tool lookup reference only; it does not install or configure the Mercury MCP server.
|
|
120
|
+
- Tool availability depends on the connected Mercury workspace, agent permissions, and the `x-api-key` provided by the user.
|
|
121
|
+
- Admin tools require explicit admin scope and should not be attempted when the agent context does not include that permission.
|
|
122
|
+
|
|
123
|
+
## More
|
|
124
|
+
|
|
125
|
+
- Full MCP reference: https://www.teamoffsite.ai/proton/docs/mcp
|
|
126
|
+
- Skill source and install: https://www.teamoffsite.ai/proton/docs/skill
|