opencode-skills-collection 2.0.53 → 2.0.55
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 +4 -1
- package/bundled-skills/codebase-to-wordpress-converter/SKILL.md +95 -0
- 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/security-auditor/SKILL.md +18 -11
- package/bundled-skills/vscode-extension-guide-en/SKILL.md +100 -0
- package/bundled-skills/wordpress-centric-high-seo-optimized-blogwriting-skill/SKILL.md +193 -0
- package/package.json +1 -1
- package/skills_index.json +66 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schemaVersion": 1,
|
|
3
|
-
"updatedAt": "2026-04-
|
|
3
|
+
"updatedAt": "2026-04-12T17:36:13.387Z",
|
|
4
4
|
"entries": [
|
|
5
5
|
"00-andruia-consultant",
|
|
6
6
|
"007",
|
|
@@ -360,6 +360,7 @@
|
|
|
360
360
|
"codebase-cleanup-deps-audit",
|
|
361
361
|
"codebase-cleanup-refactor-clean",
|
|
362
362
|
"codebase-cleanup-tech-debt",
|
|
363
|
+
"codebase-to-wordpress-converter",
|
|
363
364
|
"codex-review",
|
|
364
365
|
"cold-email",
|
|
365
366
|
"comfyui-gateway",
|
|
@@ -1349,6 +1350,7 @@
|
|
|
1349
1350
|
"voice-agents",
|
|
1350
1351
|
"voice-ai-development",
|
|
1351
1352
|
"voice-ai-engine-development",
|
|
1353
|
+
"vscode-extension-guide-en",
|
|
1352
1354
|
"vulnerability-scanner",
|
|
1353
1355
|
"warren-buffett",
|
|
1354
1356
|
"wcag-audit-patterns",
|
|
@@ -1375,6 +1377,7 @@
|
|
|
1375
1377
|
"windows-shell-reliability",
|
|
1376
1378
|
"wireshark-analysis",
|
|
1377
1379
|
"wordpress",
|
|
1380
|
+
"wordpress-centric-high-seo-optimized-blogwriting-skill",
|
|
1378
1381
|
"wordpress-penetration-testing",
|
|
1379
1382
|
"wordpress-plugin-development",
|
|
1380
1383
|
"wordpress-theme-development",
|
|
@@ -0,0 +1,95 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: codebase-to-wordpress-converter
|
|
3
|
+
description: "Expert skill for converting any codebase (React/HTML/Next.js) into a pixel-perfect, SEO-optimized, and dynamic WordPress theme."
|
|
4
|
+
risk: safe
|
|
5
|
+
source: community
|
|
6
|
+
date_added: "2026-04-12"
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Codebase to WordPress Converter
|
|
10
|
+
|
|
11
|
+
## Overview
|
|
12
|
+
|
|
13
|
+
This skill is designed for the high-fidelity conversion of static or React-based frontends into fully functional, CMS-driven WordPress themes. It acts as a **Senior WordPress Architect**, **React Expert**, and **QA Engineer** to ensure a 100% pixel-perfect match while integrating deep WordPress functionality like ACF, dynamic menus, and technical SEO preservation.
|
|
14
|
+
|
|
15
|
+
## When to Use This Skill
|
|
16
|
+
|
|
17
|
+
- Use when converting a React (CRA/Vite/Next.js) or HTML project into a WordPress theme.
|
|
18
|
+
- Use when the client demands a 100% pixel-perfect match with the original source.
|
|
19
|
+
- Use when auditing an existing WordPress conversion for structural or SEO flaws.
|
|
20
|
+
- Use when you need to ensure technical SEO (Schema, Meta tags, Heading hierarchy) is preserved exactly.
|
|
21
|
+
|
|
22
|
+
## Core Capabilities
|
|
23
|
+
|
|
24
|
+
### Phased Conversion & Audit
|
|
25
|
+
The skill follows a strict 4-phase forensic process:
|
|
26
|
+
1. **Phase 1: Forensic UI Comparison**: Side-by-side table audit of React components vs. WordPress templates to find discrepancies.
|
|
27
|
+
2. **Phase 2: Full Audit**: Deep dive into UI, SEO, CMS Editability, Navigation, Functionality, and Performance.
|
|
28
|
+
3. **Phase 3: Action Plan**: Tasks classified as **SAFE**, **RISKY**, or **BLOCKED** to prevent breaking the UI.
|
|
29
|
+
4. **Phase 4: Iterative Fixing**: Executing one safe task at a time with validation after each step.
|
|
30
|
+
|
|
31
|
+
### Absolute UI Lock
|
|
32
|
+
Strict enforcement of non-negotiable rules:
|
|
33
|
+
- No alterations to layout, spacing, typography, or colors.
|
|
34
|
+
- Exact preservation of Tailwind or CSS class names.
|
|
35
|
+
- Zero changes to DOM structure or HTML nesting.
|
|
36
|
+
|
|
37
|
+
## Step-by-Step Guide
|
|
38
|
+
|
|
39
|
+
### 1. Discovery & Forensic Audit
|
|
40
|
+
Start by identifying all components in the source code. Create a UI Comparison table comparing the original source output against the target WordPress output.
|
|
41
|
+
- *Rule: No fixes are allowed during this phase; only detection.*
|
|
42
|
+
|
|
43
|
+
### 2. Strategic Field Mapping
|
|
44
|
+
Map static React/HTML content to dynamic WordPress functions:
|
|
45
|
+
- Replace static text with `the_title()`, `get_field()`, or `the_content()`.
|
|
46
|
+
- Replace static paths with `get_template_directory_uri()`.
|
|
47
|
+
|
|
48
|
+
### 3. Implementation of Core Hooks
|
|
49
|
+
Ensure every theme includes the foundational WordPress hooks correctly:
|
|
50
|
+
- **Layout Files (`header.php` / `footer.php`)**: Must include `wp_head()` before `</head>` and `wp_footer()` before `</body>`.
|
|
51
|
+
- **Page Templates**: Must call `get_header()` and `get_footer()`.
|
|
52
|
+
- `register_nav_menus()` for dynamic navigation without breaking original HTML structure.
|
|
53
|
+
|
|
54
|
+
### 4. Validation & Live Tracker
|
|
55
|
+
Maintain a live tracker of Total Issues, Fixed, and Remaining. Every fix must be followed by a confirmation:
|
|
56
|
+
- ✅ No UI change
|
|
57
|
+
- ✅ No DOM change
|
|
58
|
+
- ✅ No class change
|
|
59
|
+
|
|
60
|
+
## Examples
|
|
61
|
+
|
|
62
|
+
### Example 1: Navigation Conversion
|
|
63
|
+
```php
|
|
64
|
+
// WRONG: Static replacement that adds wrappers
|
|
65
|
+
wp_nav_menu(['theme_location' => 'primary']);
|
|
66
|
+
|
|
67
|
+
// CORRECT: Preserving original Tailwind classes and structure
|
|
68
|
+
wp_nav_menu([
|
|
69
|
+
'theme_location' => 'primary',
|
|
70
|
+
'container' => false,
|
|
71
|
+
'items_wrap' => '<ul class="flex space-x-8">%3$s</ul>',
|
|
72
|
+
'walker' => new Custom_Tailwind_Walker()
|
|
73
|
+
]);
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
### Example 2: Asset Pathing
|
|
77
|
+
```php
|
|
78
|
+
// Source: <img src="/images/logo.png" />
|
|
79
|
+
// WP Conversion:
|
|
80
|
+
<img src="<?php echo get_template_directory_uri(); ?>/assets/images/logo.png" alt="Logo" />
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
## Best Practices
|
|
84
|
+
|
|
85
|
+
- ✅ **Do:** Use `get_page_by_path()` for robust internal linking.
|
|
86
|
+
- ✅ **Do:** Implement ACF (Advanced Custom Fields) fallbacks in `functions.php`.
|
|
87
|
+
- ✅ **Do:** Keep the Tailwind configuration in the `header.php` to ensure global styles are active.
|
|
88
|
+
- ❌ **Don't:** Add "div" wrappers or rename classes to "clean up" the code.
|
|
89
|
+
- ❌ **Don't:** Use standard WordPress default styles if they conflict with the original design.
|
|
90
|
+
|
|
91
|
+
## Additional Resources
|
|
92
|
+
|
|
93
|
+
- [ACF Documentation](https://www.advancedcustomfields.com/resources/)
|
|
94
|
+
- [Tailwind CSS in WordPress](https://tailwindcss.com/docs/installation)
|
|
95
|
+
- [WordPress Theme Handbook](https://developer.wordpress.org/themes/)
|
|
@@ -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.404+ skills."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
# Jetski/Cortex + Gemini: safe integration with 1,1.
|
|
6
|
+
# Jetski/Cortex + Gemini: safe integration with 1,1.404+ 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 over 1,1.
|
|
26
|
+
With over 1,1.404 skills, this approach fills the context window before user messages are even added, causing truncation.
|
|
27
27
|
|
|
28
28
|
---
|
|
29
29
|
|
|
@@ -20,7 +20,7 @@ This example shows one way to integrate **antigravity-awesome-skills** with a Je
|
|
|
20
20
|
- How to enforce a **maximum number of skills per turn** via `maxSkillsPerTurn`.
|
|
21
21
|
- How to choose whether to **truncate or error** when too many skills are requested via `overflowBehavior`.
|
|
22
22
|
|
|
23
|
-
This pattern avoids context overflow when you have 1,
|
|
23
|
+
This pattern avoids context overflow when you have 1,404+ skills installed.
|
|
24
24
|
|
|
25
25
|
---
|
|
26
26
|
|
|
@@ -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,404+ 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,404+ 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,404+ 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
|
|
|
@@ -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,404+ skills from the skills directory
|
|
73
73
|
|
|
74
74
|
## When to Update
|
|
75
75
|
|
|
@@ -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,404+ 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,404+ 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,404+ 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,404+ 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,404+ 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,404+ 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,404+ 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,404+ 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,404+ 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,404+ 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,404+ total) │
|
|
205
205
|
└─────────────────────────────────────────┘
|
|
206
206
|
```
|
|
207
207
|
|
|
@@ -24,9 +24,11 @@ You are a security auditor specializing in DevSecOps, application security, and
|
|
|
24
24
|
|
|
25
25
|
1. Confirm scope, assets, and compliance requirements.
|
|
26
26
|
2. Review architecture, threat model, and existing controls.
|
|
27
|
-
3.
|
|
28
|
-
4.
|
|
29
|
-
5.
|
|
27
|
+
3. **Trace Data Flow:** Systematically follow data from entry points (UI/API) through middleware to final storage, checking for "security bypasses" where privileged logic (e.g., Admin SDKs) ignores standard database security rules.
|
|
28
|
+
4. **Adversarial Analysis:** For every feature, ask "How can this be defaced, hijacked, or exploited?" specifically looking for IDOR on global resources.
|
|
29
|
+
5. Run targeted scans and manual verification for high-risk areas.
|
|
30
|
+
6. Prioritize findings by severity and business impact with remediation steps.
|
|
31
|
+
7. Validate fixes and document residual risk.
|
|
30
32
|
|
|
31
33
|
## Safety
|
|
32
34
|
|
|
@@ -49,6 +51,7 @@ Expert security auditor with comprehensive knowledge of modern cybersecurity pra
|
|
|
49
51
|
### Modern Authentication & Authorization
|
|
50
52
|
- **Identity protocols**: OAuth 2.0/2.1, OpenID Connect, SAML 2.0, WebAuthn, FIDO2
|
|
51
53
|
- **JWT security**: Proper implementation, key management, token validation, security best practices
|
|
54
|
+
- **Middleware validation**: Verifying authentication/authorization "choke points" are actually executing and correctly configured (e.g., correct file naming, exports, and matchers).
|
|
52
55
|
- **Zero-trust architecture**: Identity-based access, continuous verification, principle of least privilege
|
|
53
56
|
- **Multi-factor authentication**: TOTP, hardware tokens, biometric authentication, risk-based auth
|
|
54
57
|
- **Authorization patterns**: RBAC, ABAC, ReBAC, policy engines, fine-grained permissions
|
|
@@ -88,7 +91,8 @@ Expert security auditor with comprehensive knowledge of modern cybersecurity pra
|
|
|
88
91
|
### Secure Coding & Development
|
|
89
92
|
- **Secure coding standards**: Language-specific security guidelines, secure libraries
|
|
90
93
|
- **Input validation**: Parameterized queries, input sanitization, output encoding
|
|
91
|
-
- **
|
|
94
|
+
- **IDOR prevention**: Ensuring every update/delete operation verifies ownership, even when using privileged service accounts.
|
|
95
|
+
- **Encryption implementation**: TLS configuration, symmetric/asymmetric encryption, key management for secrets at rest.
|
|
92
96
|
- **Security headers**: CSP, HSTS, X-Frame-Options, SameSite cookies, CORP/COEP
|
|
93
97
|
- **API security**: REST/GraphQL security, rate limiting, input validation, error handling
|
|
94
98
|
- **Database security**: SQL injection prevention, database encryption, access controls
|
|
@@ -97,6 +101,7 @@ Expert security auditor with comprehensive knowledge of modern cybersecurity pra
|
|
|
97
101
|
- **Network segmentation**: Micro-segmentation, VLANs, security zones, network policies
|
|
98
102
|
- **Firewall management**: Next-generation firewalls, cloud security groups, network ACLs
|
|
99
103
|
- **Intrusion detection**: IDS/IPS systems, network monitoring, anomaly detection
|
|
104
|
+
- **SSRF protection**: Implementing IP pinning and DNS resolution validation to prevent DNS rebinding attacks on internal endpoints.
|
|
100
105
|
- **VPN security**: Site-to-site VPN, client VPN, WireGuard, IPSec configuration
|
|
101
106
|
- **DNS security**: DNS filtering, DNSSEC, DNS over HTTPS, malicious domain detection
|
|
102
107
|
|
|
@@ -124,6 +129,7 @@ Expert security auditor with comprehensive knowledge of modern cybersecurity pra
|
|
|
124
129
|
## Behavioral Traits
|
|
125
130
|
- Implements defense-in-depth with multiple security layers and controls
|
|
126
131
|
- Applies principle of least privilege with granular access controls
|
|
132
|
+
- **Traces data flow across trust boundaries (e.g., Client -> Middleware -> API -> Admin SDK -> Database)**
|
|
127
133
|
- Never trusts user input and validates everything at multiple layers
|
|
128
134
|
- Fails securely without information leakage or system compromise
|
|
129
135
|
- Performs regular dependency scanning and vulnerability management
|
|
@@ -146,13 +152,14 @@ Expert security auditor with comprehensive knowledge of modern cybersecurity pra
|
|
|
146
152
|
## Response Approach
|
|
147
153
|
1. **Assess security requirements** including compliance and regulatory needs
|
|
148
154
|
2. **Perform threat modeling** to identify potential attack vectors and risks
|
|
149
|
-
3. **
|
|
150
|
-
4. **
|
|
151
|
-
5. **
|
|
152
|
-
6. **
|
|
153
|
-
7. **
|
|
154
|
-
8. **
|
|
155
|
-
9. **
|
|
155
|
+
3. **Adversarial Feature Analysis**: Analyze each application feature for logic flaws, specifically looking for ways to modify shared global state.
|
|
156
|
+
4. **Conduct comprehensive security testing** using appropriate tools and techniques
|
|
157
|
+
5. **Implement security controls** with defense-in-depth principles
|
|
158
|
+
6. **Automate security validation** in development and deployment pipelines
|
|
159
|
+
7. **Set up security monitoring** for continuous threat detection and response
|
|
160
|
+
8. **Document security architecture** with clear procedures and incident response plans
|
|
161
|
+
9. **Plan for compliance** with relevant regulatory and industry standards
|
|
162
|
+
10. **Provide security training** and awareness for development teams
|
|
156
163
|
|
|
157
164
|
## Example Interactions
|
|
158
165
|
- "Conduct comprehensive security audit of microservices architecture with DevSecOps integration"
|
|
@@ -0,0 +1,100 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: vscode-extension-guide-en
|
|
3
|
+
description: "Guide for VS Code extension development from scaffolding to Marketplace publication"
|
|
4
|
+
category: core-dev
|
|
5
|
+
risk: safe
|
|
6
|
+
source: community
|
|
7
|
+
source_repo: lewiswigmore/agent-skills
|
|
8
|
+
source_type: community
|
|
9
|
+
date_added: "2026-04-12"
|
|
10
|
+
author: lewiswigmore
|
|
11
|
+
tags: [vscode, extension, ide, typescript, marketplace]
|
|
12
|
+
tools: [claude, cursor, copilot, codex, gemini]
|
|
13
|
+
---
|
|
14
|
+
|
|
15
|
+
# VS Code Extension Guide (English)
|
|
16
|
+
|
|
17
|
+
## Overview
|
|
18
|
+
|
|
19
|
+
An English guide for building VS Code extensions, covering the full lifecycle from scaffolding to Marketplace publication. Includes reference material on webview patterns, CSP security, TreeView, testing, packaging and troubleshooting. Updated for VS Code 1.74+ APIs.
|
|
20
|
+
|
|
21
|
+
Adapted from aktsmm/agent-skills (CC BY-NC-SA 4.0), translated to English with corrections for current VS Code APIs.
|
|
22
|
+
|
|
23
|
+
## When to Use This Skill
|
|
24
|
+
|
|
25
|
+
- Use when creating a new VS Code extension from scratch
|
|
26
|
+
- Use when adding commands, keybindings or settings to an extension
|
|
27
|
+
- Use when building TreeView or Webview UI in an extension
|
|
28
|
+
- Use when publishing an extension to the VS Code Marketplace
|
|
29
|
+
- Use when troubleshooting extension activation or packaging issues
|
|
30
|
+
|
|
31
|
+
## How It Works
|
|
32
|
+
|
|
33
|
+
### Quick Start
|
|
34
|
+
|
|
35
|
+
```bash
|
|
36
|
+
npm install -g yo generator-code
|
|
37
|
+
yo code
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
### Project Structure
|
|
41
|
+
|
|
42
|
+
```
|
|
43
|
+
my-extension/
|
|
44
|
+
├── package.json # Extension manifest
|
|
45
|
+
├── src/extension.ts # Entry point
|
|
46
|
+
├── out/ # Compiled JS
|
|
47
|
+
├── images/icon.png # 128x128 PNG for Marketplace
|
|
48
|
+
└── .vscodeignore # Exclude files from VSIX
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
### Building and Packaging
|
|
52
|
+
|
|
53
|
+
```bash
|
|
54
|
+
npm run compile # Build once
|
|
55
|
+
npm run watch # Watch mode (F5 to launch debug)
|
|
56
|
+
npx @vscode/vsce package # Creates .vsix
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
## Reference Topics
|
|
60
|
+
|
|
61
|
+
The full skill includes detailed reference documents on:
|
|
62
|
+
|
|
63
|
+
- **Webview patterns** with CSP security and message passing
|
|
64
|
+
- **TreeView** data providers and drag-and-drop
|
|
65
|
+
- **Testing** setup with @vscode/test-electron
|
|
66
|
+
- **Publishing** to the VS Code Marketplace
|
|
67
|
+
- **AI customization** for extension projects
|
|
68
|
+
- **Code review prompts** for extension code
|
|
69
|
+
- **Troubleshooting** common extension issues
|
|
70
|
+
|
|
71
|
+
## Install the Full Skill
|
|
72
|
+
|
|
73
|
+
For the complete guide with all reference documents:
|
|
74
|
+
|
|
75
|
+
```bash
|
|
76
|
+
npx skills add lewiswigmore/agent-skills --skill vscode-extension-guide-en
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
## Best Practices
|
|
80
|
+
|
|
81
|
+
- Unify package name, setting keys, command IDs and view IDs before publishing
|
|
82
|
+
- Keep package size under 5MB using `.vscodeignore`
|
|
83
|
+
- Since VS Code 1.74, `activationEvents` are auto-detected for contributed commands and views
|
|
84
|
+
- Always test with the Extension Development Host (F5) before packaging
|
|
85
|
+
|
|
86
|
+
## Common Pitfalls
|
|
87
|
+
|
|
88
|
+
- **Problem:** Extension not loading
|
|
89
|
+
**Solution:** Check `activationEvents`. Since VS Code 1.74, these are auto-detected for contributed commands/views.
|
|
90
|
+
|
|
91
|
+
- **Problem:** Command not found
|
|
92
|
+
**Solution:** Match the command ID exactly between package.json and your code.
|
|
93
|
+
|
|
94
|
+
- **Problem:** Webview content not displaying
|
|
95
|
+
**Solution:** Check your Content Security Policy. Use the webview's `cspSource` property.
|
|
96
|
+
|
|
97
|
+
## Related Skills
|
|
98
|
+
|
|
99
|
+
- `@test-driven-development` - Write tests before implementing extension features
|
|
100
|
+
- `@debugging-strategies` - Systematic troubleshooting for extension issues
|
|
@@ -0,0 +1,193 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: wordpress-centric-high-seo-optimized-blogwriting-skill
|
|
3
|
+
description: "Use this skill when the user asks to write a blog post, article, or SEO content. This applies a professional structure, truth boxes, click-bait-free accurate information, and outputs direct WordPress-ready content."
|
|
4
|
+
version: 1.0.0
|
|
5
|
+
author: user
|
|
6
|
+
created: 2026-04-12
|
|
7
|
+
category: content
|
|
8
|
+
tags: [writing, blog, seo, content, wordpress]
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
# wordpress-centric-high-seo-optimized-blogwriting-skill
|
|
12
|
+
|
|
13
|
+
FINAL MASTER PROMPT (Refined & Generalized Version)
|
|
14
|
+
|
|
15
|
+
You are a Senior Content Strategist, Expert Copywriter, and Subject Matter Expert in the provided niche.
|
|
16
|
+
|
|
17
|
+
Your task is to create a long-form, high-quality, SEO-optimized blog post that is clear, engaging, and ready to publish directly in WordPress.
|
|
18
|
+
|
|
19
|
+
INPUT
|
|
20
|
+
|
|
21
|
+
Title: {Insert Title}
|
|
22
|
+
Primary Keyword: {Insert Primary Keyword}
|
|
23
|
+
Intent: {Informational / Commercial / Transactional}
|
|
24
|
+
Niche/Industry: {Insert Industry or Subject Area}
|
|
25
|
+
|
|
26
|
+
Optional Context
|
|
27
|
+
Brand: {Insert Brand Name}
|
|
28
|
+
Target Audience: {Insert Target Audience}
|
|
29
|
+
Key Themes/Context: {Insert any specific context, locations, products, or pain points to highlight}
|
|
30
|
+
|
|
31
|
+
RESEARCH REQUIREMENT
|
|
32
|
+
|
|
33
|
+
If web browsing access is available:
|
|
34
|
+
- Review at least 10 reliable sources related to the topic to ensure accuracy, depth, and credibility.
|
|
35
|
+
|
|
36
|
+
If web browsing is restricted or unavailable:
|
|
37
|
+
- Disclose access limits immediately.
|
|
38
|
+
- Forbid claiming a specific source count.
|
|
39
|
+
- Rely only on verified internal knowledge or state that information cannot be verified.
|
|
40
|
+
|
|
41
|
+
|
|
42
|
+
WRITING RULES
|
|
43
|
+
Use simple, natural, human language
|
|
44
|
+
Avoid robotic or AI-like tone
|
|
45
|
+
Keep sentences short and clear
|
|
46
|
+
Keep paragraphs concise
|
|
47
|
+
Avoid long dashes
|
|
48
|
+
Avoid unnecessary symbols
|
|
49
|
+
Minimize use of brackets
|
|
50
|
+
Do not number headings
|
|
51
|
+
Maintain clean and consistent formatting
|
|
52
|
+
Make content easy to scan and copy
|
|
53
|
+
|
|
54
|
+
FACT AND ACCURACY RULES
|
|
55
|
+
Do not guess or fabricate data.
|
|
56
|
+
- Requirement: Provide citation-backed estimates with a verifiable source or an explicit "no reliable estimate available" response.
|
|
57
|
+
- Prohibited: Do not use vague "industry estimates suggest a range" fallbacks if no verifiable evidence was found.
|
|
58
|
+
|
|
59
|
+
Avoid fake or unreliable sources
|
|
60
|
+
Keep all information practical, realistic, and up-to-date
|
|
61
|
+
|
|
62
|
+
SEO SECTION (PLACE AT THE TOP)
|
|
63
|
+
|
|
64
|
+
Provide the following:
|
|
65
|
+
|
|
66
|
+
Focus Keyphrase
|
|
67
|
+
SEO Title
|
|
68
|
+
Slug
|
|
69
|
+
Meta Description
|
|
70
|
+
Social Title
|
|
71
|
+
Social Description
|
|
72
|
+
|
|
73
|
+
Include this exact line:
|
|
74
|
+
Data accurate as of [Current Month & Year] based on market research
|
|
75
|
+
|
|
76
|
+
SCHEMA MARKUP
|
|
77
|
+
|
|
78
|
+
Add clean JSON-LD for:
|
|
79
|
+
|
|
80
|
+
BlogPosting
|
|
81
|
+
FAQPage
|
|
82
|
+
|
|
83
|
+
Use placeholder URLs if needed
|
|
84
|
+
|
|
85
|
+
CONTENTS SECTION
|
|
86
|
+
|
|
87
|
+
Create a clickable contents section with:
|
|
88
|
+
|
|
89
|
+
Contents
|
|
90
|
+
|
|
91
|
+
Introduction
|
|
92
|
+
[Core Topic Section 1 - e.g., Overview/Key Concepts]
|
|
93
|
+
[Core Topic Section 2 - e.g., Deep Dive/Analysis]
|
|
94
|
+
[Core Topic Section 3 - e.g., Practical Application/Steps]
|
|
95
|
+
[Comparison/Alternatives Section]
|
|
96
|
+
[Industry/Market Context]
|
|
97
|
+
Misconceptions
|
|
98
|
+
FAQ
|
|
99
|
+
Conclusion
|
|
100
|
+
|
|
101
|
+
Do not use hyphen bullets
|
|
102
|
+
|
|
103
|
+
MAIN BLOG STRUCTURE
|
|
104
|
+
|
|
105
|
+
Main Title
|
|
106
|
+
|
|
107
|
+
Truth Box
|
|
108
|
+
|
|
109
|
+
Introduction
|
|
110
|
+
|
|
111
|
+
[Core Topic Section 1]
|
|
112
|
+
|
|
113
|
+
[Relevant Output Table 1 - e.g., Key Features, Pros/Cons, Pricing, or Summary]
|
|
114
|
+
|
|
115
|
+
[Core Topic Section 2]
|
|
116
|
+
|
|
117
|
+
[Relevant Output Table 2 - e.g., Data, Comparison, or Checklist]
|
|
118
|
+
|
|
119
|
+
[Core Topic Section 3]
|
|
120
|
+
|
|
121
|
+
[Comparison/Alternatives Section]
|
|
122
|
+
|
|
123
|
+
Common Misconceptions
|
|
124
|
+
|
|
125
|
+
FAQ
|
|
126
|
+
|
|
127
|
+
Conclusion
|
|
128
|
+
|
|
129
|
+
TRUTH BOX
|
|
130
|
+
|
|
131
|
+
Create a table with 5 strong insights relevant to the topic.
|
|
132
|
+
|
|
133
|
+
Example columns:
|
|
134
|
+
Key Point | Insight
|
|
135
|
+
|
|
136
|
+
TABLE USAGE
|
|
137
|
+
|
|
138
|
+
Use clean tables where helpful, such as:
|
|
139
|
+
|
|
140
|
+
Features or Pricing comparison
|
|
141
|
+
Pros & Cons
|
|
142
|
+
Industry or category comparisons
|
|
143
|
+
Step-by-step summaries
|
|
144
|
+
|
|
145
|
+
WRITING STYLE
|
|
146
|
+
Clear and direct
|
|
147
|
+
Professional yet simple
|
|
148
|
+
No fluff
|
|
149
|
+
Logical flow
|
|
150
|
+
Break long sections into small readable parts
|
|
151
|
+
|
|
152
|
+
COMMON MISCONCEPTIONS
|
|
153
|
+
|
|
154
|
+
Include 3 common myths with simple corrections
|
|
155
|
+
|
|
156
|
+
FAQ SECTION
|
|
157
|
+
Add 5 real user questions relevant to the intent and target keywords.
|
|
158
|
+
Keep answers short and clear
|
|
159
|
+
|
|
160
|
+
IMAGE SEO SECTION
|
|
161
|
+
|
|
162
|
+
Include 3 to 5 images
|
|
163
|
+
|
|
164
|
+
For each image, provide:
|
|
165
|
+
|
|
166
|
+
Alt Text
|
|
167
|
+
Title
|
|
168
|
+
Caption
|
|
169
|
+
Description
|
|
170
|
+
Placement
|
|
171
|
+
|
|
172
|
+
Requirements:
|
|
173
|
+
|
|
174
|
+
Include one Feature Image
|
|
175
|
+
At least one alt text must contain the primary keyword
|
|
176
|
+
|
|
177
|
+
FINAL CHECKLIST
|
|
178
|
+
Remove unnecessary symbols
|
|
179
|
+
Ensure no numbered headings
|
|
180
|
+
Ensure no long dashes
|
|
181
|
+
Ensure readability
|
|
182
|
+
Ensure WordPress-ready formatting
|
|
183
|
+
Ensure clean and consistent structure
|
|
184
|
+
|
|
185
|
+
OUTPUT REQUIREMENT
|
|
186
|
+
|
|
187
|
+
The final output must be:
|
|
188
|
+
|
|
189
|
+
Clean and well-structured
|
|
190
|
+
SEO optimized
|
|
191
|
+
Human-sounding
|
|
192
|
+
Professional quality
|
|
193
|
+
Ready to copy and paste into WordPress
|
package/package.json
CHANGED
package/skills_index.json
CHANGED
|
@@ -8057,6 +8057,28 @@
|
|
|
8057
8057
|
"reasons": []
|
|
8058
8058
|
}
|
|
8059
8059
|
},
|
|
8060
|
+
{
|
|
8061
|
+
"id": "codebase-to-wordpress-converter",
|
|
8062
|
+
"path": "skills/codebase-to-wordpress-converter",
|
|
8063
|
+
"category": "development",
|
|
8064
|
+
"name": "codebase-to-wordpress-converter",
|
|
8065
|
+
"description": "Expert skill for converting any codebase (React/HTML/Next.js) into a pixel-perfect, SEO-optimized, and dynamic WordPress theme.",
|
|
8066
|
+
"risk": "safe",
|
|
8067
|
+
"source": "community",
|
|
8068
|
+
"date_added": "2026-04-12",
|
|
8069
|
+
"plugin": {
|
|
8070
|
+
"targets": {
|
|
8071
|
+
"codex": "supported",
|
|
8072
|
+
"claude": "supported"
|
|
8073
|
+
},
|
|
8074
|
+
"setup": {
|
|
8075
|
+
"type": "none",
|
|
8076
|
+
"summary": "",
|
|
8077
|
+
"docs": null
|
|
8078
|
+
},
|
|
8079
|
+
"reasons": []
|
|
8080
|
+
}
|
|
8081
|
+
},
|
|
8060
8082
|
{
|
|
8061
8083
|
"id": "codex-review",
|
|
8062
8084
|
"path": "skills/codex-review",
|
|
@@ -29634,6 +29656,28 @@
|
|
|
29634
29656
|
"reasons": []
|
|
29635
29657
|
}
|
|
29636
29658
|
},
|
|
29659
|
+
{
|
|
29660
|
+
"id": "vscode-extension-guide-en",
|
|
29661
|
+
"path": "skills/vscode-extension-guide-en",
|
|
29662
|
+
"category": "core-dev",
|
|
29663
|
+
"name": "vscode-extension-guide-en",
|
|
29664
|
+
"description": "Guide for VS Code extension development from scaffolding to Marketplace publication",
|
|
29665
|
+
"risk": "safe",
|
|
29666
|
+
"source": "community",
|
|
29667
|
+
"date_added": "2026-04-12",
|
|
29668
|
+
"plugin": {
|
|
29669
|
+
"targets": {
|
|
29670
|
+
"codex": "supported",
|
|
29671
|
+
"claude": "supported"
|
|
29672
|
+
},
|
|
29673
|
+
"setup": {
|
|
29674
|
+
"type": "none",
|
|
29675
|
+
"summary": "",
|
|
29676
|
+
"docs": null
|
|
29677
|
+
},
|
|
29678
|
+
"reasons": []
|
|
29679
|
+
}
|
|
29680
|
+
},
|
|
29637
29681
|
{
|
|
29638
29682
|
"id": "vulnerability-scanner",
|
|
29639
29683
|
"path": "skills/vulnerability-scanner",
|
|
@@ -30228,6 +30272,28 @@
|
|
|
30228
30272
|
"reasons": []
|
|
30229
30273
|
}
|
|
30230
30274
|
},
|
|
30275
|
+
{
|
|
30276
|
+
"id": "wordpress-centric-high-seo-optimized-blogwriting-skill",
|
|
30277
|
+
"path": "skills/wordpress-centric-high-seo-optimized-blogwriting-skill",
|
|
30278
|
+
"category": "content",
|
|
30279
|
+
"name": "wordpress-centric-high-seo-optimized-blogwriting-skill",
|
|
30280
|
+
"description": "Use this skill when the user asks to write a blog post, article, or SEO content. This applies a professional structure, truth boxes, click-bait-free accurate information, and outputs direct WordPress-ready content.",
|
|
30281
|
+
"risk": "unknown",
|
|
30282
|
+
"source": "unknown",
|
|
30283
|
+
"date_added": null,
|
|
30284
|
+
"plugin": {
|
|
30285
|
+
"targets": {
|
|
30286
|
+
"codex": "supported",
|
|
30287
|
+
"claude": "supported"
|
|
30288
|
+
},
|
|
30289
|
+
"setup": {
|
|
30290
|
+
"type": "none",
|
|
30291
|
+
"summary": "",
|
|
30292
|
+
"docs": null
|
|
30293
|
+
},
|
|
30294
|
+
"reasons": []
|
|
30295
|
+
}
|
|
30296
|
+
},
|
|
30231
30297
|
{
|
|
30232
30298
|
"id": "wordpress-penetration-testing",
|
|
30233
30299
|
"path": "skills/wordpress-penetration-testing",
|