opencode-skills-antigravity 1.0.9 → 1.0.11
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/cpp-pro/references/build-tooling.md +440 -0
- package/bundled-skills/cpp-pro/references/concurrency.md +437 -0
- package/bundled-skills/cpp-pro/references/memory-performance.md +397 -0
- package/bundled-skills/cpp-pro/references/modern-cpp.md +304 -0
- package/bundled-skills/cpp-pro/references/templates.md +357 -0
- package/bundled-skills/cpp-pro/resources/implementation-playbook.md +43 -0
- package/bundled-skills/docs/integrations/jetski-cortex.md +3 -3
- package/bundled-skills/docs/integrations/jetski-gemini-loader/README.md +4 -4
- package/bundled-skills/docs/integrations/jetski-gemini-loader/{loader.ts → loader.mjs} +38 -50
- package/bundled-skills/docs/maintainers/repo-growth-seo.md +3 -3
- package/bundled-skills/docs/maintainers/security-findings-triage-2026-03-15.csv +1 -1
- package/bundled-skills/docs/maintainers/security-findings-triage-2026-03-15.md +1 -1
- package/bundled-skills/docs/maintainers/security-findings-triage-2026-03-18-addendum.md +1 -1
- package/bundled-skills/docs/maintainers/skills-update-guide.md +1 -1
- package/bundled-skills/docs/users/agent-overload-recovery.md +54 -0
- 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/faq.md +8 -0
- package/bundled-skills/docs/users/gemini-cli-skills.md +1 -1
- package/bundled-skills/docs/users/getting-started.md +4 -1
- package/bundled-skills/docs/users/kiro-integration.md +1 -1
- package/bundled-skills/docs/users/usage.md +5 -5
- package/bundled-skills/docs/users/visual-guide.md +4 -4
- package/bundled-skills/gdb-cli/SKILL.md +239 -0
- package/bundled-skills/jobgpt/SKILL.md +100 -0
- package/bundled-skills/moyu/SKILL.md +267 -0
- package/bundled-skills/windows-shell-reliability/SKILL.md +107 -0
- package/package.json +1 -1
- package/bundled-skills/goldrush-api/SKILL.md +0 -109
|
@@ -33,7 +33,7 @@
|
|
|
33
33
|
| 8 | medium | Symlinked file copy in Microsoft skill sync can leak host data | `tools/scripts/sync_microsoft_skills.py` | duplicate of another finding | filesystem-trust-boundary | Same origin/main behavior as finding 7: the Microsoft sync path trusted resolved symlink targets and copied files from them. | Fix once in sync_microsoft_skills.py by constraining resolved paths to the clone root. | codex/security-filesystem-trust-boundary |
|
|
34
34
|
| 9 | medium | Committed Python bytecode can hide malicious logic | `skills/ui-ux-pro-max/scripts/__pycache__/core.cpython-314.pyc | skills/ui-ux-pro-max/scripts/__pycache__/design_system.cpython-314.pyc` | still present but low practical risk | robustness | On origin/main, tracked __pycache__ artifacts were still present under skills/ui-ux-pro-max/scripts, which is review-hostile but not independently exploitable. | Remove tracked bytecode artifacts and rely on source-only review plus .gitignore. | codex/security-robustness |
|
|
35
35
|
| 10 | medium | Symlinked SKILL.md can leak host files via index script | `tools/scripts/generate_index.py` | still present but low practical risk | filesystem-trust-boundary | On origin/main, generate_index.py opened every SKILL.md it found via os.walk and did not skip symlinked SKILL.md files, so a malicious local symlink could exfiltrate another file into index metadata generation. | Skip symlinked SKILL.md files during indexing. | codex/security-filesystem-trust-boundary |
|
|
36
|
-
| 11 | low | Example loader trusts manifest paths, enabling file read | `docs/integrations/jetski-gemini-loader/loader.
|
|
36
|
+
| 11 | low | Example loader trusts manifest paths, enabling file read | `docs/integrations/jetski-gemini-loader/loader.mjs` | obsolete/not reproducible on current HEAD | n/a | On origin/main, the loader example resolves the requested file and rejects any path whose path.relative escapes the configured skills root, so the reported direct file read no longer reproduces. | n/a | n/a |
|
|
37
37
|
| 12 | low | TLS certificate verification disabled in new scrapers | `skills/junta-leiloeiros/scripts/scraper/base_scraper.py | skills/junta-leiloeiros/scripts/web_scraper_fallback.py` | still present but low practical risk | auth-integrity | On origin/main, both the base scraper and the direct fallback client instantiated HTTP clients with verify=False / ignore_https_errors=True, which weakens transport integrity but is a local-run scraper risk rather than an application RCE. | Enable TLS verification by default and require an explicit environment opt-out for insecure targets. | codex/security-auth-integrity |
|
|
38
38
|
| 13 | low | Complete bundle omits valid skill categories | `tools/lib/skill-filter.js | tools/scripts/build-catalog.js | data/bundles.json` | obsolete/not reproducible on current HEAD | n/a | On origin/main, shipped bundle data is generated by tools/scripts/build-catalog.js into data/bundles.json; the reported omission in tools/lib/skill-filter.js does not drive current shipped catalog data. | n/a | n/a |
|
|
39
39
|
| 14 | low | Malformed frontmatter delimiter breaks YAML parsing for skills | `skills/alpha-vantage/SKILL.md | tools/lib/skill-utils.js` | still present but low practical risk | robustness | On origin/main, skills/alpha-vantage/SKILL.md still contained an extra delimiter token (--- Unknown), which caused parser warnings and broken metadata interpretation. | Repair the malformed frontmatter so the file is a valid YAML frontmatter document. | codex/security-robustness |
|
|
@@ -6,7 +6,7 @@ This addendum supersedes the previous Jetski loader assessment in
|
|
|
6
6
|
## Correction
|
|
7
7
|
|
|
8
8
|
- Finding: `Example loader trusts manifest paths, enabling file read`
|
|
9
|
-
- Path: `docs/integrations/jetski-gemini-loader/loader.
|
|
9
|
+
- Path: `docs/integrations/jetski-gemini-loader/loader.mjs`
|
|
10
10
|
- Previous triage status on 2026-03-15: `obsolete/not reproducible on current HEAD`
|
|
11
11
|
- Corrected assessment: the loader was still reproducible via a symlinked
|
|
12
12
|
`SKILL.md` that resolved outside `skillsRoot`. A local proof read the linked
|
|
@@ -69,7 +69,7 @@ For manual updates, you need:
|
|
|
69
69
|
The update process refreshes:
|
|
70
70
|
- Skills index (`skills_index.json`)
|
|
71
71
|
- Web app skills data (`apps\web-app\public\skills.json`)
|
|
72
|
-
- All 1,
|
|
72
|
+
- All 1,309+ skills from the skills directory
|
|
73
73
|
|
|
74
74
|
## When to Update
|
|
75
75
|
|
|
@@ -0,0 +1,54 @@
|
|
|
1
|
+
# Antigravity Recovery for Context Overload and Truncation
|
|
2
|
+
|
|
3
|
+
Use this guide when Antigravity loads too many skills for the current task and starts failing with truncation, context, or trajectory-conversion errors.
|
|
4
|
+
|
|
5
|
+
Typical symptoms:
|
|
6
|
+
|
|
7
|
+
- the agent crashes only when a large skills folder is present
|
|
8
|
+
- the error mentions truncation, context conversion, or a trajectory/message that cannot be converted
|
|
9
|
+
- the problem shows up more often on large repositories or long-running tasks
|
|
10
|
+
|
|
11
|
+
## Linux and macOS fast path
|
|
12
|
+
|
|
13
|
+
Use the activation scripts to keep the full library archived while exposing only the bundles or skills you need in the live Antigravity directory.
|
|
14
|
+
|
|
15
|
+
1. Fully close Antigravity.
|
|
16
|
+
2. Clone this repository somewhere local if you do not already have a clone.
|
|
17
|
+
3. Run the activation script from the cloned repository.
|
|
18
|
+
|
|
19
|
+
Examples:
|
|
20
|
+
|
|
21
|
+
```bash
|
|
22
|
+
./scripts/activate-skills.sh "Web Wizard" "Integration & APIs"
|
|
23
|
+
./scripts/activate-skills.sh --clear
|
|
24
|
+
./scripts/activate-skills.sh brainstorming systematic-debugging
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
What the script does:
|
|
28
|
+
|
|
29
|
+
- syncs the repository `skills/` tree into `~/.gemini/antigravity/skills_library`
|
|
30
|
+
- preserves your full library in the backing store
|
|
31
|
+
- activates only the requested bundles or skill ids into `~/.gemini/antigravity/skills`
|
|
32
|
+
- `--clear` archives the current live directory first, then restores the selected set
|
|
33
|
+
|
|
34
|
+
Optional environment overrides:
|
|
35
|
+
|
|
36
|
+
```bash
|
|
37
|
+
AG_BASE_DIR=/custom/antigravity ./scripts/activate-skills.sh --clear Essentials
|
|
38
|
+
AG_REPO_SKILLS_DIR=/path/to/repo/skills ./scripts/activate-skills.sh brainstorming
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
## Windows recovery
|
|
42
|
+
|
|
43
|
+
If Antigravity is stuck in a restart loop on Windows, use the Windows-specific recovery guide instead:
|
|
44
|
+
|
|
45
|
+
- [windows-truncation-recovery.md](windows-truncation-recovery.md)
|
|
46
|
+
|
|
47
|
+
That guide covers the browser/app storage cleanup needed when the host keeps reopening the same broken session.
|
|
48
|
+
|
|
49
|
+
## Prevention tips
|
|
50
|
+
|
|
51
|
+
- start with 3-5 skills from a bundle instead of exposing the full library at once
|
|
52
|
+
- use bundle activation before opening very large repositories
|
|
53
|
+
- keep role-specific stacks active and archive the rest
|
|
54
|
+
- if a host stores broken session state, clear that host state before restoring a smaller active set
|
|
@@ -6,7 +6,7 @@ Antigravity Awesome Skills gives Claude Code users an installable library of `SK
|
|
|
6
6
|
|
|
7
7
|
## Why use this repo for Claude Code
|
|
8
8
|
|
|
9
|
-
- It includes 1,
|
|
9
|
+
- It includes 1,309+ skills instead of a narrow single-domain starter pack.
|
|
10
10
|
- It supports the standard `.claude/skills/` path and the Claude Code plugin marketplace flow.
|
|
11
11
|
- It includes onboarding docs, bundles, and workflows so new users do not need to guess where to begin.
|
|
12
12
|
- It covers both everyday engineering tasks and specialized work like security reviews, infrastructure, product planning, and documentation.
|
|
@@ -154,6 +154,14 @@ It includes:
|
|
|
154
154
|
- the default Antigravity Windows paths to back up first
|
|
155
155
|
- an optional batch script adapted from [issue #274](https://github.com/sickn33/antigravity-awesome-skills/issues/274)
|
|
156
156
|
|
|
157
|
+
### I hit context overload on Linux or macOS. What should I do?
|
|
158
|
+
|
|
159
|
+
If Antigravity becomes unstable only when the full skills library is active, switch to the activation flow instead of exposing every skill at once:
|
|
160
|
+
|
|
161
|
+
- [agent-overload-recovery.md](agent-overload-recovery.md)
|
|
162
|
+
|
|
163
|
+
That guide shows how to run `scripts/activate-skills.sh` from a cloned copy of this repository so only the bundles or skill ids you need stay active in `~/.gemini/antigravity/skills`.
|
|
164
|
+
|
|
157
165
|
### How do I update skills?
|
|
158
166
|
|
|
159
167
|
Navigate to your skills directory and pull the latest changes:
|
|
@@ -8,7 +8,7 @@ Antigravity Awesome Skills supports Gemini CLI through the `.gemini/skills/` pat
|
|
|
8
8
|
|
|
9
9
|
- It installs directly into the expected Gemini skills path.
|
|
10
10
|
- It includes both core software engineering skills and deeper agent/LLM-oriented skills.
|
|
11
|
-
- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,
|
|
11
|
+
- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,309+ files.
|
|
12
12
|
- It is useful whether you want a broad internal skill library or a single repo to test many workflows quickly.
|
|
13
13
|
|
|
14
14
|
## Install Gemini CLI Skills
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# Getting Started with Antigravity Awesome Skills (V8.
|
|
1
|
+
# Getting Started with Antigravity Awesome Skills (V8.7.1)
|
|
2
2
|
|
|
3
3
|
**New here? This guide will help you supercharge your AI Agent in 5 minutes.**
|
|
4
4
|
|
|
@@ -142,6 +142,9 @@ A: Yes! Use the **@skill-creator** skill to build your own.
|
|
|
142
142
|
**Q: What if Antigravity on Windows gets stuck in a truncation crash loop?**
|
|
143
143
|
A: Follow the recovery steps in [windows-truncation-recovery.md](windows-truncation-recovery.md). It explains which Antigravity storage folders to back up and clear, and includes an optional batch helper adapted from [issue #274](https://github.com/sickn33/antigravity-awesome-skills/issues/274).
|
|
144
144
|
|
|
145
|
+
**Q: What if Antigravity overloads on Linux or macOS when too many skills are active?**
|
|
146
|
+
A: Use the activation flow in [agent-overload-recovery.md](agent-overload-recovery.md). It shows how to run `scripts/activate-skills.sh` from a cloned repo so you can keep the full library archived and activate only the bundles or skills you need in the live Antigravity directory.
|
|
147
|
+
|
|
145
148
|
**Q: Is this free?**
|
|
146
149
|
A: Yes. Original code and tooling are MIT-licensed, and original documentation/non-code written content is CC BY 4.0. See [../../LICENSE](../../LICENSE) and [../../LICENSE-CONTENT](../../LICENSE-CONTENT).
|
|
147
150
|
|
|
@@ -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,309+ 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
|
|
@@ -12,7 +12,7 @@ Great question! Here's what just happened and what to do next:
|
|
|
12
12
|
|
|
13
13
|
When you ran `npx antigravity-awesome-skills` or cloned the repository, you:
|
|
14
14
|
|
|
15
|
-
✅ **Downloaded 1,
|
|
15
|
+
✅ **Downloaded 1,309+ skill files** to your computer (default: `~/.gemini/antigravity/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
|
|
16
16
|
✅ **Made them available** to your AI assistant
|
|
17
17
|
❌ **Did NOT enable them all automatically** (they're just sitting there, waiting)
|
|
18
18
|
|
|
@@ -32,7 +32,7 @@ Bundles are **recommended lists** of skills grouped by role. They help you decid
|
|
|
32
32
|
|
|
33
33
|
**Analogy:**
|
|
34
34
|
|
|
35
|
-
- You installed a toolbox with 1,
|
|
35
|
+
- You installed a toolbox with 1,309+ tools (✅ done)
|
|
36
36
|
- Bundles are like **labeled organizer trays** saying: "If you're a carpenter, start with these 10 tools"
|
|
37
37
|
- You don't install bundles—you **pick skills from them**
|
|
38
38
|
|
|
@@ -40,7 +40,7 @@ Bundles are **recommended lists** of skills grouped by role. They help you decid
|
|
|
40
40
|
|
|
41
41
|
❌ Separate installations
|
|
42
42
|
❌ Different download commands
|
|
43
|
-
❌ Something
|
|
43
|
+
❌ Something most users need to activate during normal install
|
|
44
44
|
|
|
45
45
|
### Example: The "Web Wizard" Bundle
|
|
46
46
|
|
|
@@ -192,7 +192,7 @@ Let's actually use a skill right now. Follow these steps:
|
|
|
192
192
|
|
|
193
193
|
## Step 5: Picking Your First Skills (Practical Advice)
|
|
194
194
|
|
|
195
|
-
Don't try to use all 1,
|
|
195
|
+
Don't try to use all 1,309+ skills at once. Here's a sensible approach:
|
|
196
196
|
|
|
197
197
|
If you want a tool-specific starting point before choosing skills, use:
|
|
198
198
|
|
|
@@ -323,7 +323,7 @@ Usually no, but if your AI doesn't recognize a skill:
|
|
|
323
323
|
|
|
324
324
|
### "Can I load all skills into the model at once?"
|
|
325
325
|
|
|
326
|
-
No. Even though you have 1,
|
|
326
|
+
No. Even though you have 1,309+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
|
|
327
327
|
|
|
328
328
|
The intended pattern is:
|
|
329
329
|
|
|
@@ -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,309+ 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,309+ 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,309+ 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,309+ total) │
|
|
205
205
|
└─────────────────────────────────────────┘
|
|
206
206
|
```
|
|
207
207
|
|
|
@@ -0,0 +1,239 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: gdb-cli
|
|
3
|
+
description: "GDB debugging assistant for AI agents - analyze core dumps, debug live processes, investigate crashes and deadlocks with source code correlation"
|
|
4
|
+
category: development
|
|
5
|
+
risk: critical
|
|
6
|
+
source: community
|
|
7
|
+
date_added: "2026-03-22"
|
|
8
|
+
author: Cerdore
|
|
9
|
+
tags:
|
|
10
|
+
- debugging
|
|
11
|
+
- gdb
|
|
12
|
+
- core-dump
|
|
13
|
+
- crash-analysis
|
|
14
|
+
- c++
|
|
15
|
+
- c
|
|
16
|
+
tools:
|
|
17
|
+
- claude-code
|
|
18
|
+
- cursor
|
|
19
|
+
- gemini-cli
|
|
20
|
+
- codex-cli
|
|
21
|
+
- antigravity
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
# GDB Debugging Assistant
|
|
25
|
+
|
|
26
|
+
## Overview
|
|
27
|
+
|
|
28
|
+
A GDB debugging skill designed for AI agents. Combines **source code analysis** with **runtime state inspection** using gdb-cli to provide intelligent debugging assistance for C/C++ programs.
|
|
29
|
+
|
|
30
|
+
## When to Use This Skill
|
|
31
|
+
|
|
32
|
+
- Analyze core dumps or crash dumps
|
|
33
|
+
- Debug running processes with GDB attach
|
|
34
|
+
- Investigate crashes, deadlocks, or memory issues
|
|
35
|
+
- Get intelligent debugging assistance with source code context
|
|
36
|
+
- Debug multi-threaded applications
|
|
37
|
+
|
|
38
|
+
## Do Not Use This Skill When
|
|
39
|
+
|
|
40
|
+
- The task is unrelated to C/C++ debugging
|
|
41
|
+
- The user needs general-purpose assistance without debugging
|
|
42
|
+
- No GDB is available (GDB 9.0+ with Python support required)
|
|
43
|
+
|
|
44
|
+
## Prerequisites
|
|
45
|
+
|
|
46
|
+
```bash
|
|
47
|
+
# Install gdb-cli
|
|
48
|
+
pip install gdb-cli
|
|
49
|
+
|
|
50
|
+
# Or from GitHub
|
|
51
|
+
pip install git+https://github.com/Cerdore/gdb-cli.git
|
|
52
|
+
|
|
53
|
+
# Verify GDB has Python support
|
|
54
|
+
gdb -nx -q -batch -ex "python print('OK')"
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
**Requirements:**
|
|
58
|
+
- Python 3.6.8+
|
|
59
|
+
- GDB 9.0+ with Python support enabled
|
|
60
|
+
- Linux OS
|
|
61
|
+
|
|
62
|
+
## How It Works
|
|
63
|
+
|
|
64
|
+
### Step 1: Initialize Debug Session
|
|
65
|
+
|
|
66
|
+
**For core dump analysis:**
|
|
67
|
+
```bash
|
|
68
|
+
gdb-cli load --binary <binary_path> --core <core_path> [--gdb-path <gdb_path>]
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
**For live process debugging:**
|
|
72
|
+
```bash
|
|
73
|
+
gdb-cli attach --pid <pid> [--binary <binary_path>]
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
**Output:** A session_id like `"session_id": "a1b2c3"`. Store this for subsequent commands.
|
|
77
|
+
|
|
78
|
+
### Step 2: Gather Initial Information
|
|
79
|
+
|
|
80
|
+
```bash
|
|
81
|
+
SESSION="<session_id>"
|
|
82
|
+
|
|
83
|
+
# List all threads
|
|
84
|
+
gdb-cli threads -s $SESSION
|
|
85
|
+
|
|
86
|
+
# Get backtrace (with local variables)
|
|
87
|
+
gdb-cli bt -s $SESSION --full
|
|
88
|
+
|
|
89
|
+
# Get registers
|
|
90
|
+
gdb-cli registers -s $SESSION
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
### Step 3: Correlate Source Code (CRITICAL)
|
|
94
|
+
|
|
95
|
+
For each frame in the backtrace:
|
|
96
|
+
1. **Extract frame info**: `{file}:{line} in {function}`
|
|
97
|
+
2. **Read source context**: Get ±20 lines around the crash point
|
|
98
|
+
3. **Get local variables**: `gdb-cli locals-cmd -s $SESSION --frame <N>`
|
|
99
|
+
4. **Analyze**: Correlate code logic with variable values
|
|
100
|
+
|
|
101
|
+
**Example correlation:**
|
|
102
|
+
```
|
|
103
|
+
Frame #0: process_data() at src/worker.c:87
|
|
104
|
+
Source code shows:
|
|
105
|
+
85: Node* node = get_node(id);
|
|
106
|
+
86: if (node == NULL) return;
|
|
107
|
+
87: node->data = value; <- Crash here
|
|
108
|
+
|
|
109
|
+
Variables show:
|
|
110
|
+
node = 0x0 (NULL)
|
|
111
|
+
|
|
112
|
+
Analysis: The NULL check on line 86 didn't catch the issue.
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
### Step 4: Deep Investigation
|
|
116
|
+
|
|
117
|
+
```bash
|
|
118
|
+
# Examine variables
|
|
119
|
+
gdb-cli eval-cmd -s $SESSION "variable_name"
|
|
120
|
+
gdb-cli eval-cmd -s $SESSION "ptr->field"
|
|
121
|
+
gdb-cli ptype -s $SESSION "struct_name"
|
|
122
|
+
|
|
123
|
+
# Memory inspection
|
|
124
|
+
gdb-cli memory -s $SESSION "0x7fffffffe000" --size 64
|
|
125
|
+
|
|
126
|
+
# Disassembly
|
|
127
|
+
gdb-cli disasm -s $SESSION --count 20
|
|
128
|
+
|
|
129
|
+
# Check all threads (for deadlock analysis)
|
|
130
|
+
gdb-cli thread-apply -s $SESSION bt --all
|
|
131
|
+
|
|
132
|
+
# View shared libraries
|
|
133
|
+
gdb-cli sharedlibs -s $SESSION
|
|
134
|
+
```
|
|
135
|
+
|
|
136
|
+
### Step 5: Session Management
|
|
137
|
+
|
|
138
|
+
```bash
|
|
139
|
+
# List active sessions
|
|
140
|
+
gdb-cli sessions
|
|
141
|
+
|
|
142
|
+
# Check session status
|
|
143
|
+
gdb-cli status -s $SESSION
|
|
144
|
+
|
|
145
|
+
# Stop session (cleanup)
|
|
146
|
+
gdb-cli stop -s $SESSION
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
## Common Debugging Patterns
|
|
150
|
+
|
|
151
|
+
### Pattern: Null Pointer Dereference
|
|
152
|
+
|
|
153
|
+
**Indicators:**
|
|
154
|
+
- Crash on memory access instruction
|
|
155
|
+
- Pointer variable is 0x0
|
|
156
|
+
|
|
157
|
+
**Investigation:**
|
|
158
|
+
```bash
|
|
159
|
+
gdb-cli registers -s $SESSION # Check RIP
|
|
160
|
+
gdb-cli eval-cmd -s $SESSION "ptr" # Check pointer value
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
### Pattern: Deadlock
|
|
164
|
+
|
|
165
|
+
**Indicators:**
|
|
166
|
+
- Multiple threads stuck in lock functions
|
|
167
|
+
- `pthread_mutex_lock` in backtrace
|
|
168
|
+
|
|
169
|
+
**Investigation:**
|
|
170
|
+
```bash
|
|
171
|
+
gdb-cli thread-apply -s $SESSION bt --all
|
|
172
|
+
# Look for circular wait patterns
|
|
173
|
+
```
|
|
174
|
+
|
|
175
|
+
### Pattern: Memory Corruption
|
|
176
|
+
|
|
177
|
+
**Indicators:**
|
|
178
|
+
- Crash in malloc/free
|
|
179
|
+
- Garbage values in variables
|
|
180
|
+
|
|
181
|
+
**Investigation:**
|
|
182
|
+
```bash
|
|
183
|
+
gdb-cli memory -s $SESSION "&variable" --size 128
|
|
184
|
+
gdb-cli registers -s $SESSION
|
|
185
|
+
```
|
|
186
|
+
|
|
187
|
+
## Examples
|
|
188
|
+
|
|
189
|
+
### Example 1: Core Dump Analysis
|
|
190
|
+
|
|
191
|
+
```bash
|
|
192
|
+
# Load core dump
|
|
193
|
+
gdb-cli load --binary ./myapp --core /tmp/core.1234
|
|
194
|
+
|
|
195
|
+
# Get crash location
|
|
196
|
+
gdb-cli bt -s a1b2c3 --full
|
|
197
|
+
|
|
198
|
+
# Examine crash frame
|
|
199
|
+
gdb-cli locals-cmd -s a1b2c3 --frame 0
|
|
200
|
+
```
|
|
201
|
+
|
|
202
|
+
### Example 2: Live Process Debugging
|
|
203
|
+
|
|
204
|
+
```bash
|
|
205
|
+
# Attach to stuck server
|
|
206
|
+
gdb-cli attach --pid 12345
|
|
207
|
+
|
|
208
|
+
# Check all threads
|
|
209
|
+
gdb-cli threads -s b2c3d4
|
|
210
|
+
|
|
211
|
+
# Get all backtraces
|
|
212
|
+
gdb-cli thread-apply -s b2c3d4 bt --all
|
|
213
|
+
```
|
|
214
|
+
|
|
215
|
+
## Best Practices
|
|
216
|
+
|
|
217
|
+
- Always read source code before drawing conclusions from variable values
|
|
218
|
+
- Use `--range` for pagination on large thread counts or deep backtraces
|
|
219
|
+
- Use `ptype` to understand complex data structures before examining values
|
|
220
|
+
- Check all threads for multi-threaded issues
|
|
221
|
+
- Cross-reference types with source code definitions
|
|
222
|
+
|
|
223
|
+
## Security & Safety Notes
|
|
224
|
+
|
|
225
|
+
- This skill requires GDB access to processes and core dumps
|
|
226
|
+
- Attaching to processes may require appropriate permissions (sudo, ptrace_scope)
|
|
227
|
+
- Core dumps may contain sensitive data - handle with care
|
|
228
|
+
- Only debug processes you have authorization to analyze
|
|
229
|
+
|
|
230
|
+
## Related Skills
|
|
231
|
+
|
|
232
|
+
- `@systematic-debugging` - General debugging methodology
|
|
233
|
+
- `@test-driven-development` - Write tests before implementation
|
|
234
|
+
|
|
235
|
+
## Links
|
|
236
|
+
|
|
237
|
+
- **Repository**: https://github.com/Cerdore/gdb-cli
|
|
238
|
+
- **PyPI**: https://pypi.org/project/gdb-cli/
|
|
239
|
+
- **Documentation**: https://github.com/Cerdore/gdb-cli#readme
|
|
@@ -0,0 +1,100 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: jobgpt
|
|
3
|
+
description: "Job search automation, auto apply, resume generation, application tracking, salary intelligence, and recruiter outreach using the JobGPT MCP server."
|
|
4
|
+
risk: safe
|
|
5
|
+
source: community
|
|
6
|
+
date_added: "2026-03-23"
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# JobGPT - Job Search Automation
|
|
10
|
+
|
|
11
|
+
## Overview
|
|
12
|
+
|
|
13
|
+
JobGPT connects your AI assistant to a complete job search automation platform via the JobGPT MCP server. It provides 34 tools covering job search, auto-apply, resume generation, application tracking, salary intelligence, and recruiter outreach so you can manage your entire job hunt from your AI coding assistant.
|
|
14
|
+
|
|
15
|
+
Built by [6figr.com](https://6figr.com/jobgpt-ai), the platform supports 150+ countries with salary data, job matching, and automated applications.
|
|
16
|
+
|
|
17
|
+
## When to Use This Skill
|
|
18
|
+
|
|
19
|
+
- You want to **search for jobs** with filters like titles, locations, salary, remote, and H1B sponsorship
|
|
20
|
+
- You want to **auto-apply** to jobs automatically
|
|
21
|
+
- You want to **generate a tailored resume** for a specific job application
|
|
22
|
+
- You want to **track your job applications** across multiple job hunts
|
|
23
|
+
- You want to **find recruiters or referrers** at target companies and send outreach emails
|
|
24
|
+
- You want to **import a job** from LinkedIn, Greenhouse, Lever, Workday, or any job board URL
|
|
25
|
+
- You want to **check your salary** and compare compensation across roles
|
|
26
|
+
|
|
27
|
+
## Setup
|
|
28
|
+
|
|
29
|
+
This skill requires the JobGPT MCP server:
|
|
30
|
+
|
|
31
|
+
1. **Create an account** - Sign up at [6figr.com/jobgpt-ai](https://6figr.com/jobgpt-ai)
|
|
32
|
+
2. **Get an API key** - Go to [6figr.com/account](https://6figr.com/account), scroll to MCP Integrations, and click Generate API Key. The key starts with `mcp_`.
|
|
33
|
+
3. **Add the MCP server:**
|
|
34
|
+
- Claude Code: `claude mcp add jobgpt -t http -u https://mcp.6figr.com/mcp --header "Authorization: <api-key>"`
|
|
35
|
+
- Other tools: Add `jobgpt-mcp-server` as an MCP server with env var `JOBGPT_API_KEY` set. Install via `npx jobgpt-mcp-server`.
|
|
36
|
+
|
|
37
|
+
Set the `JOBGPT_API_KEY` environment variable when you are running the local `npx jobgpt-mcp-server` path.
|
|
38
|
+
|
|
39
|
+
## Examples
|
|
40
|
+
|
|
41
|
+
### Find Remote Jobs
|
|
42
|
+
|
|
43
|
+
> "Find remote senior React jobs paying over $150k"
|
|
44
|
+
|
|
45
|
+
The skill uses `search_jobs` with title, remote, and salary filters to find matching positions, then presents results with company, title, location, salary range, and key skills.
|
|
46
|
+
|
|
47
|
+
### Auto-Apply to Jobs
|
|
48
|
+
|
|
49
|
+
> "Auto-apply to the top 5 matches from my job hunt"
|
|
50
|
+
|
|
51
|
+
The skill checks that your resume is uploaded, uses `match_jobs` to find new matches, saves the selected matches with `add_job_to_applications`, then triggers `apply_to_job` for each resulting application. It monitors progress with `get_application_stats`.
|
|
52
|
+
|
|
53
|
+
### Generate a Tailored Resume
|
|
54
|
+
|
|
55
|
+
> "Generate a tailored resume for this Google application"
|
|
56
|
+
|
|
57
|
+
The skill calls `generate_resume_for_job` to create an AI-optimized resume targeting the specific job's requirements, then provides the download link via `get_generated_resume`.
|
|
58
|
+
|
|
59
|
+
### Import and Apply from a URL
|
|
60
|
+
|
|
61
|
+
> "Apply to this job for me - https://boards.greenhouse.io/company/jobs/12345"
|
|
62
|
+
|
|
63
|
+
The skill uses `import_job_by_url` to import the job from any supported platform (LinkedIn, Greenhouse, Lever, Workday), adds it to applications, and optionally triggers auto-apply.
|
|
64
|
+
|
|
65
|
+
### Recruiter Outreach
|
|
66
|
+
|
|
67
|
+
> "Find recruiters for this job and draft an outreach email"
|
|
68
|
+
|
|
69
|
+
The skill finds recruiters with `get_job_recruiters` and helps craft a personalized message. The draft is presented to the user for review; `send_outreach` is only called after explicit user confirmation.
|
|
70
|
+
|
|
71
|
+
### Check Application Stats
|
|
72
|
+
|
|
73
|
+
> "Show my application stats for the last 7 days"
|
|
74
|
+
|
|
75
|
+
The skill uses `get_application_stats` for an aggregated overview - total counts by status, auto-apply metrics, and pipeline progress.
|
|
76
|
+
|
|
77
|
+
## Best Practices
|
|
78
|
+
|
|
79
|
+
- **Check credits first** - Auto-apply and resume generation consume credits. Use `get_credits` before batch operations.
|
|
80
|
+
- **Complete your profile** - Run `get_profile` first and fill in missing fields with `update_profile` for better job matches.
|
|
81
|
+
- **Upload a resume before applying** - Use `list_resumes` to check, and `upload_resume` if needed.
|
|
82
|
+
- **Use job hunts for ongoing searches** - Create a job hunt with `create_job_hunt` to save filters and get continuous matches.
|
|
83
|
+
- **Use `get_application` for saved jobs** - If a user asks about a job they've already saved, use `get_application` instead of `get_job`.
|
|
84
|
+
|
|
85
|
+
## Troubleshooting
|
|
86
|
+
|
|
87
|
+
| Problem | Solution |
|
|
88
|
+
|---------|----------|
|
|
89
|
+
| "Missing Authorization header" | For Claude Code and other remote HTTP MCP setups, confirm the `Authorization` header is configured on the MCP server entry |
|
|
90
|
+
| "Missing API key" | For the local `npx jobgpt-mcp-server` setup, ensure `JOBGPT_API_KEY` is set to your API key |
|
|
91
|
+
| "Insufficient credits" | Check balance with `get_credits`. Purchase more at 6figr.com/account |
|
|
92
|
+
| Auto-apply not working | Ensure a resume is uploaded and the job hunt has auto-apply enabled |
|
|
93
|
+
| No job matches found | Broaden your search filters (fewer titles, more locations, wider salary range) |
|
|
94
|
+
|
|
95
|
+
## Additional Resources
|
|
96
|
+
|
|
97
|
+
- [JobGPT Platform](https://6figr.com/jobgpt-ai) - Sign up and manage your account
|
|
98
|
+
- [MCP Server Repo](https://github.com/6figr-com/jobgpt-mcp-server) - Source code and setup guides
|
|
99
|
+
- [Skills Repo](https://github.com/6figr-com/skills) - This skill's source
|
|
100
|
+
- [npm Package](https://www.npmjs.com/package/jobgpt-mcp-server) - Install via npm
|