opencode-skills-collection 3.1.7 → 3.1.9
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 +10 -1
- package/bundled-skills/ai-loop/SKILL.md +136 -0
- package/bundled-skills/arrowspace/SKILL.md +116 -0
- package/bundled-skills/cron-doctor/SKILL.md +244 -0
- package/bundled-skills/cron-doctor/scripts/cli.js +75 -0
- package/bundled-skills/cron-doctor/scripts/cron-engine.js +638 -0
- package/bundled-skills/docs/contributors/quality-bar.md +1 -0
- package/bundled-skills/docs/contributors/skill-anatomy.md +19 -3
- 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/categorization-implementation.md +14 -24
- 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/maintainers/smart-auto-categorization.md +24 -25
- 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 +5 -5
- 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/local-config.md +11 -11
- package/bundled-skills/docs/users/specialized-plugin-roadmap.md +3 -3
- package/bundled-skills/docs/users/usage.md +4 -4
- package/bundled-skills/docs/users/visual-guide.md +4 -4
- package/bundled-skills/docs/vietnamese/BUNDLES.vi.md +1 -1
- package/bundled-skills/docs/vietnamese/CONTRIBUTING.vi.md +15 -9
- package/bundled-skills/docs/vietnamese/FAQ.vi.md +30 -20
- package/bundled-skills/docs/vietnamese/GETTING_STARTED.vi.md +22 -14
- package/bundled-skills/docs/vietnamese/QUALITY_BAR.vi.md +9 -4
- package/bundled-skills/docs/vietnamese/README.vi.md +29 -30
- package/bundled-skills/docs/vietnamese/SKILLS_README.vi.md +3 -3
- package/bundled-skills/docs/vietnamese/SKILL_ANATOMY.vi.md +33 -5
- package/bundled-skills/docs/vietnamese/TRANSLATION_PLAN.vi.md +1 -1
- package/bundled-skills/docs/vietnamese/VISUAL_GUIDE.vi.md +17 -18
- package/bundled-skills/gh-image/SKILL.md +122 -0
- package/bundled-skills/github-actions-debugger/SKILL.md +99 -0
- package/bundled-skills/loki-mode/examples/todo-app-generated/frontend/package-lock.json +9 -9
- package/bundled-skills/loki-mode/examples/todo-app-generated/frontend/package.json +2 -2
- package/bundled-skills/premium-3d-website/SKILL.md +133 -0
- package/bundled-skills/sql-sentinel/SKILL.md +131 -0
- package/bundled-skills/web-project-brainstorming/SKILL.md +149 -0
- package/package.json +1 -1
- package/skills_index.json +176 -0
|
@@ -0,0 +1,149 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: web-project-brainstorming
|
|
3
|
+
description: Masterclass framework for brainstorming web development projects and page designs. Outlines structural phases for concept, UX flow, styling aesthetics, technical architecture, and SEO.
|
|
4
|
+
category: consulting
|
|
5
|
+
risk: safe
|
|
6
|
+
source: self
|
|
7
|
+
source_type: self
|
|
8
|
+
date_added: "2026-06-26"
|
|
9
|
+
author: Rsmiyani
|
|
10
|
+
tags: [brainstorming, project-planning, web-development, product-scoping, design-system, architecture]
|
|
11
|
+
tools: [claude, cursor, gemini]
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
# Web Project Brainstorming
|
|
15
|
+
|
|
16
|
+
## Overview
|
|
17
|
+
|
|
18
|
+
This skill provides a structured, masterclass-level framework for brainstorming web projects, web applications, or individual page designs at their inception. It guides developers and designers through scoping the core product concept, mapping user flows, defining visual styling aesthetics, selecting the technical stack, and planning for search engine optimization (SEO) and performance.
|
|
19
|
+
|
|
20
|
+
## When to Use This Skill
|
|
21
|
+
|
|
22
|
+
- Use at the start of any new web development project or page redesign.
|
|
23
|
+
- Use when scoping feature sets, user roles, and interaction patterns for web applications.
|
|
24
|
+
- Use when establishing design systems, color tokens, and layout guidelines.
|
|
25
|
+
- Use when evaluating tech stacks (e.g., Next.js vs. Vanilla JS, CSS Grid vs. Tailwind).
|
|
26
|
+
|
|
27
|
+
## How It Works
|
|
28
|
+
|
|
29
|
+
Execute web project brainstorming sequentially across six structured phases. Ask the user questions one phase at a time to maintain focus and ensure thorough alignment.
|
|
30
|
+
|
|
31
|
+
### Phase 1: Core Concept & Scoping
|
|
32
|
+
Define the product's primary value proposition and scope:
|
|
33
|
+
- **Target Audience**: Who is using the website or application?
|
|
34
|
+
- **Core Value**: What problem does it solve for users?
|
|
35
|
+
- **Key Features**: What are the top 3–5 mandatory features?
|
|
36
|
+
|
|
37
|
+
### Phase 2: User Experience (UX) & Information Architecture
|
|
38
|
+
Map how users navigate and interact:
|
|
39
|
+
- **Page Hierarchy**: What is the sitemap and page structure?
|
|
40
|
+
- **User Journeys**: What step-by-step flows do users take to complete key goals?
|
|
41
|
+
- **Responsive Layout**: Is the interface mobile-first, desktop-first, or balanced?
|
|
42
|
+
|
|
43
|
+
### Phase 3: Visual Styling & Design System
|
|
44
|
+
Establish the visual guidelines and aesthetic parameters:
|
|
45
|
+
- **Design Aesthetic**: Modern, minimalist, brutalist, glassmorphism, or luxury?
|
|
46
|
+
- **Color Palette**: What are the primary, secondary, and accent colors? (Prefer tailorable HSL/RGB models over static color keywords).
|
|
47
|
+
- **Typography**: Which Google Fonts or system fonts fit the theme? (e.g., Inter, Outfit, Syne).
|
|
48
|
+
- **Interactive States**: How do hovers, clicks, transitions, and loading states behave?
|
|
49
|
+
|
|
50
|
+
### Phase 4: Technical Stack & Architecture
|
|
51
|
+
Select the technologies and integration systems:
|
|
52
|
+
- **Frontend Framework**: React, Next.js, Vite, Astro, Svelte, or Vanilla HTML/JS?
|
|
53
|
+
- **Styling Method**: Vanilla CSS, Tailwind CSS, or CSS Modules?
|
|
54
|
+
- **Data & Backend**: REST API, GraphQL, tRPC, Firebase, Supabase, or SQLite?
|
|
55
|
+
- **State Management**: Zustand, Context API, Redux, or local React state?
|
|
56
|
+
|
|
57
|
+
### Phase 5: SEO, Accessibility (A11y), and Performance
|
|
58
|
+
Plan for discoverability and fast loading times:
|
|
59
|
+
- **SEO Elements**: Title tag structure, meta descriptions, and semantic HTML tag hierarchy.
|
|
60
|
+
- **Accessibility**: ARIA labels, semantic tags, keyboard navigation, and color contrast.
|
|
61
|
+
- **Performance**: Preloading assets, lazy loading images, server-side rendering (SSR), and CDN delivery.
|
|
62
|
+
|
|
63
|
+
### Phase 6: MVP Scope & Project Phases
|
|
64
|
+
Break the work down into manageable increments:
|
|
65
|
+
- **Phase 1 (MVP)**: The absolute minimum viable product needed to deploy.
|
|
66
|
+
- **Phase 2 (Enhancements)**: Nice-to-have features, micro-animations, and advanced integrations.
|
|
67
|
+
|
|
68
|
+
## Examples
|
|
69
|
+
|
|
70
|
+
### Interactive Questionnaire Prompt Template
|
|
71
|
+
Use this prompt layout when initiating a brainstorming session with a client or team member:
|
|
72
|
+
|
|
73
|
+
```markdown
|
|
74
|
+
👋 Let's brainstorm your new web project! We will walk through 6 quick phases.
|
|
75
|
+
|
|
76
|
+
---
|
|
77
|
+
### Phase 1: Core Concept & Scoping
|
|
78
|
+
1. What is the main title or working name of this project?
|
|
79
|
+
2. Who are the primary target users (e.g., tech-savvy professionals, shoppers, children)?
|
|
80
|
+
3. What are the 3 core tasks a user must be able to perform?
|
|
81
|
+
---
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
### Brainstorming Output Document Template
|
|
85
|
+
Once all phases are complete, generate a markdown blueprint for the project using this template:
|
|
86
|
+
|
|
87
|
+
```markdown
|
|
88
|
+
# Project Blueprint: [Project Name]
|
|
89
|
+
|
|
90
|
+
## 1. Product Concept
|
|
91
|
+
- **Value Proposition**: [Summary]
|
|
92
|
+
- **Key Features**:
|
|
93
|
+
1. [Feature 1]
|
|
94
|
+
2. [Feature 2]
|
|
95
|
+
|
|
96
|
+
## 2. Information Architecture & UX
|
|
97
|
+
- **Pages**: `/index.html`, `/dashboard.html`
|
|
98
|
+
- **Primary User Flow**: User signs up -> completes onboarding -> views dashboard.
|
|
99
|
+
|
|
100
|
+
## 3. Styling & Aesthetics
|
|
101
|
+
- **Aesthetic**: Sleek Glassmorphism Dark Mode
|
|
102
|
+
- **Color Tokens**:
|
|
103
|
+
- Background: `hsl(222, 47%, 11%)`
|
|
104
|
+
- Accent/Primary: `hsl(217, 91%, 60%)`
|
|
105
|
+
- **Typography**: Inter (Body), Outfit (Headings)
|
|
106
|
+
|
|
107
|
+
## 4. Technical Architecture
|
|
108
|
+
- **Framework**: Next.js (App Router)
|
|
109
|
+
- **Styling**: Tailwind CSS
|
|
110
|
+
- **Database**: PostgreSQL with Prisma ORM
|
|
111
|
+
|
|
112
|
+
## 5. SEO & Performance
|
|
113
|
+
- **Primary Title**: "[Brand] | [Tagline]"
|
|
114
|
+
- **Performance Strategy**: Dynamic image optimization, caching pages via Cloudflare.
|
|
115
|
+
|
|
116
|
+
## 6. MVP vs Phase 2 Roadmap
|
|
117
|
+
- **MVP**: Authentication + core dashboard view.
|
|
118
|
+
- **Phase 2**: Real-time notifications and PDF reporting.
|
|
119
|
+
```
|
|
120
|
+
|
|
121
|
+
## Best Practices
|
|
122
|
+
|
|
123
|
+
- ✅ Ask questions incrementally—never dump all six phases in a single response to avoid cognitive overload.
|
|
124
|
+
- ✅ Propose logical defaults (e.g., recommending responsive Tailwind/CSS Grid and standard semantic HTML) if the user is unsure.
|
|
125
|
+
- ✅ Ensure semantic HTML layout hierarchy (one `<h1>` per page, sequential `<section>`, `<article>`, `<header>`, `<footer>` elements) is planned from the start.
|
|
126
|
+
- ✅ Document explicit non-goals to prevent feature creep.
|
|
127
|
+
|
|
128
|
+
## Limitations
|
|
129
|
+
|
|
130
|
+
- This skill focuses on conceptual mapping, architecture, and feature planning; it does not replace the writing of implementation code or system configuration.
|
|
131
|
+
- Brainstorming outcomes should be treated as flexible blueprints and refined as technical constraints are discovered during development.
|
|
132
|
+
|
|
133
|
+
## Security & Safety Notes
|
|
134
|
+
|
|
135
|
+
- During Phase 4 (Architecture), flag any security requirements (e.g., SSL certificates, CORS policies, secure authentication storage, environment variables protection) early.
|
|
136
|
+
- Do not store actual API tokens, passwords, or credentials in design or blueprint documents.
|
|
137
|
+
|
|
138
|
+
## Common Pitfalls
|
|
139
|
+
|
|
140
|
+
- **Problem**: Scope Creep (the project expands too quickly before building an MVP).
|
|
141
|
+
**Solution**: Enforce Phase 6 strictly. Push nice-to-have features into Phase 2.
|
|
142
|
+
- **Problem**: Ignoring mobile design until late in development.
|
|
143
|
+
**Solution**: Brainstorm responsive patterns in Phase 2 before deciding on layout style in Phase 3.
|
|
144
|
+
|
|
145
|
+
## Related Skills
|
|
146
|
+
|
|
147
|
+
- `@writing-plans` - Organizing structural step-by-step engineering plans.
|
|
148
|
+
- `@architecture-decision-records` - Documenting architectural decisions.
|
|
149
|
+
- `@ux-flow` - Designing deep user experience flows and interaction details.
|
package/package.json
CHANGED
package/skills_index.json
CHANGED
|
@@ -1107,6 +1107,28 @@
|
|
|
1107
1107
|
]
|
|
1108
1108
|
}
|
|
1109
1109
|
},
|
|
1110
|
+
{
|
|
1111
|
+
"id": "ai-loop",
|
|
1112
|
+
"path": "skills/ai-loop",
|
|
1113
|
+
"category": "workflow",
|
|
1114
|
+
"name": "ai-loop",
|
|
1115
|
+
"description": "Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.",
|
|
1116
|
+
"risk": "safe",
|
|
1117
|
+
"source": "community",
|
|
1118
|
+
"date_added": "2026-06-27",
|
|
1119
|
+
"plugin": {
|
|
1120
|
+
"targets": {
|
|
1121
|
+
"codex": "supported",
|
|
1122
|
+
"claude": "supported"
|
|
1123
|
+
},
|
|
1124
|
+
"setup": {
|
|
1125
|
+
"type": "none",
|
|
1126
|
+
"summary": "",
|
|
1127
|
+
"docs": null
|
|
1128
|
+
},
|
|
1129
|
+
"reasons": []
|
|
1130
|
+
}
|
|
1131
|
+
},
|
|
1110
1132
|
{
|
|
1111
1133
|
"id": "ai-ml",
|
|
1112
1134
|
"path": "skills/ai-ml",
|
|
@@ -2702,6 +2724,28 @@
|
|
|
2702
2724
|
"reasons": []
|
|
2703
2725
|
}
|
|
2704
2726
|
},
|
|
2727
|
+
{
|
|
2728
|
+
"id": "arrowspace",
|
|
2729
|
+
"path": "skills/arrowspace",
|
|
2730
|
+
"category": "data",
|
|
2731
|
+
"name": "arrowspace",
|
|
2732
|
+
"description": "Spectral vector search using graph Laplacian eigenstructure. Use when cosine/L2 similarity misses latent structure in your embeddings.",
|
|
2733
|
+
"risk": "safe",
|
|
2734
|
+
"source": "community",
|
|
2735
|
+
"date_added": "2026-06-25",
|
|
2736
|
+
"plugin": {
|
|
2737
|
+
"targets": {
|
|
2738
|
+
"codex": "supported",
|
|
2739
|
+
"claude": "supported"
|
|
2740
|
+
},
|
|
2741
|
+
"setup": {
|
|
2742
|
+
"type": "none",
|
|
2743
|
+
"summary": "",
|
|
2744
|
+
"docs": null
|
|
2745
|
+
},
|
|
2746
|
+
"reasons": []
|
|
2747
|
+
}
|
|
2748
|
+
},
|
|
2705
2749
|
{
|
|
2706
2750
|
"id": "article-illustrations",
|
|
2707
2751
|
"path": "skills/article-illustrations",
|
|
@@ -10272,6 +10316,28 @@
|
|
|
10272
10316
|
"reasons": []
|
|
10273
10317
|
}
|
|
10274
10318
|
},
|
|
10319
|
+
{
|
|
10320
|
+
"id": "cron-doctor",
|
|
10321
|
+
"path": "skills/cron-doctor",
|
|
10322
|
+
"category": "devops",
|
|
10323
|
+
"name": "cron-doctor",
|
|
10324
|
+
"description": "Diagnose and validate cron expressions before they ship. Catches the five silent death-traps: impossible dates that never fire, OR-semantics that fire too often, midnight spikes, uneven step drift, and leap-year February 29.",
|
|
10325
|
+
"risk": "safe",
|
|
10326
|
+
"source": "community",
|
|
10327
|
+
"date_added": "2026-06-26",
|
|
10328
|
+
"plugin": {
|
|
10329
|
+
"targets": {
|
|
10330
|
+
"codex": "supported",
|
|
10331
|
+
"claude": "supported"
|
|
10332
|
+
},
|
|
10333
|
+
"setup": {
|
|
10334
|
+
"type": "none",
|
|
10335
|
+
"summary": "",
|
|
10336
|
+
"docs": null
|
|
10337
|
+
},
|
|
10338
|
+
"reasons": []
|
|
10339
|
+
}
|
|
10340
|
+
},
|
|
10275
10341
|
{
|
|
10276
10342
|
"id": "crossframe",
|
|
10277
10343
|
"path": "skills/crossframe",
|
|
@@ -15648,6 +15714,28 @@
|
|
|
15648
15714
|
"reasons": []
|
|
15649
15715
|
}
|
|
15650
15716
|
},
|
|
15717
|
+
{
|
|
15718
|
+
"id": "gh-image",
|
|
15719
|
+
"path": "skills/gh-image",
|
|
15720
|
+
"category": "developer-tools",
|
|
15721
|
+
"name": "gh-image",
|
|
15722
|
+
"description": "Upload local images to GitHub and get canonical user-attachments embed URLs; use when asked to attach a screenshot to a PR, issue, or comment, or to embed before/after images in a README.",
|
|
15723
|
+
"risk": "safe",
|
|
15724
|
+
"source": "community",
|
|
15725
|
+
"date_added": "2026-06-25",
|
|
15726
|
+
"plugin": {
|
|
15727
|
+
"targets": {
|
|
15728
|
+
"codex": "supported",
|
|
15729
|
+
"claude": "supported"
|
|
15730
|
+
},
|
|
15731
|
+
"setup": {
|
|
15732
|
+
"type": "none",
|
|
15733
|
+
"summary": "",
|
|
15734
|
+
"docs": null
|
|
15735
|
+
},
|
|
15736
|
+
"reasons": []
|
|
15737
|
+
}
|
|
15738
|
+
},
|
|
15651
15739
|
{
|
|
15652
15740
|
"id": "gh-review-requests",
|
|
15653
15741
|
"path": "skills/gh-review-requests",
|
|
@@ -15890,6 +15978,28 @@
|
|
|
15890
15978
|
"reasons": []
|
|
15891
15979
|
}
|
|
15892
15980
|
},
|
|
15981
|
+
{
|
|
15982
|
+
"id": "github-actions-debugger",
|
|
15983
|
+
"path": "skills/github-actions-debugger",
|
|
15984
|
+
"category": "devops",
|
|
15985
|
+
"name": "github-actions-debugger",
|
|
15986
|
+
"description": "Specialized skill for diagnosing, analyzing, and fixing failing GitHub Actions workflows by parsing run logs and pipeline definitions.",
|
|
15987
|
+
"risk": "safe",
|
|
15988
|
+
"source": "community",
|
|
15989
|
+
"date_added": "2026-06-25",
|
|
15990
|
+
"plugin": {
|
|
15991
|
+
"targets": {
|
|
15992
|
+
"codex": "supported",
|
|
15993
|
+
"claude": "supported"
|
|
15994
|
+
},
|
|
15995
|
+
"setup": {
|
|
15996
|
+
"type": "none",
|
|
15997
|
+
"summary": "",
|
|
15998
|
+
"docs": null
|
|
15999
|
+
},
|
|
16000
|
+
"reasons": []
|
|
16001
|
+
}
|
|
16002
|
+
},
|
|
15893
16003
|
{
|
|
15894
16004
|
"id": "github-actions-templates",
|
|
15895
16005
|
"path": "skills/github-actions-templates",
|
|
@@ -25689,6 +25799,28 @@
|
|
|
25689
25799
|
"reasons": []
|
|
25690
25800
|
}
|
|
25691
25801
|
},
|
|
25802
|
+
{
|
|
25803
|
+
"id": "premium-3d-website",
|
|
25804
|
+
"path": "skills/premium-3d-website",
|
|
25805
|
+
"category": "frontend",
|
|
25806
|
+
"name": "premium-3d-website",
|
|
25807
|
+
"description": "Guidelines for building premium 3D websites, focusing on custom WebGL shaders, post-processing, physics-based interactions, smooth animations, preloaders, and device optimization.",
|
|
25808
|
+
"risk": "safe",
|
|
25809
|
+
"source": "self",
|
|
25810
|
+
"date_added": "2026-06-25",
|
|
25811
|
+
"plugin": {
|
|
25812
|
+
"targets": {
|
|
25813
|
+
"codex": "supported",
|
|
25814
|
+
"claude": "supported"
|
|
25815
|
+
},
|
|
25816
|
+
"setup": {
|
|
25817
|
+
"type": "none",
|
|
25818
|
+
"summary": "",
|
|
25819
|
+
"docs": null
|
|
25820
|
+
},
|
|
25821
|
+
"reasons": []
|
|
25822
|
+
}
|
|
25823
|
+
},
|
|
25692
25824
|
{
|
|
25693
25825
|
"id": "price-psychology-strategist",
|
|
25694
25826
|
"path": "skills/price-psychology-strategist",
|
|
@@ -31281,6 +31413,28 @@
|
|
|
31281
31413
|
"reasons": []
|
|
31282
31414
|
}
|
|
31283
31415
|
},
|
|
31416
|
+
{
|
|
31417
|
+
"id": "sql-sentinel",
|
|
31418
|
+
"path": "skills/sql-sentinel",
|
|
31419
|
+
"category": "data",
|
|
31420
|
+
"name": "sql-sentinel",
|
|
31421
|
+
"description": "Audit SQL for the cost & performance anti-patterns that burn warehouse credits. Scores warehouse health 0-100 and outputs a prioritized cost-reduction plan for BigQuery, Snowflake, Redshift, and Postgres.",
|
|
31422
|
+
"risk": "safe",
|
|
31423
|
+
"source": "community",
|
|
31424
|
+
"date_added": "2026-06-26",
|
|
31425
|
+
"plugin": {
|
|
31426
|
+
"targets": {
|
|
31427
|
+
"codex": "supported",
|
|
31428
|
+
"claude": "supported"
|
|
31429
|
+
},
|
|
31430
|
+
"setup": {
|
|
31431
|
+
"type": "none",
|
|
31432
|
+
"summary": "",
|
|
31433
|
+
"docs": null
|
|
31434
|
+
},
|
|
31435
|
+
"reasons": []
|
|
31436
|
+
}
|
|
31437
|
+
},
|
|
31284
31438
|
{
|
|
31285
31439
|
"id": "sqlmap-database-pentesting",
|
|
31286
31440
|
"path": "skills/sqlmap-database-pentesting",
|
|
@@ -35603,6 +35757,28 @@
|
|
|
35603
35757
|
"reasons": []
|
|
35604
35758
|
}
|
|
35605
35759
|
},
|
|
35760
|
+
{
|
|
35761
|
+
"id": "web-project-brainstorming",
|
|
35762
|
+
"path": "skills/web-project-brainstorming",
|
|
35763
|
+
"category": "consulting",
|
|
35764
|
+
"name": "web-project-brainstorming",
|
|
35765
|
+
"description": "Masterclass framework for brainstorming web development projects and page designs. Outlines structural phases for concept, UX flow, styling aesthetics, technical architecture, and SEO.",
|
|
35766
|
+
"risk": "safe",
|
|
35767
|
+
"source": "self",
|
|
35768
|
+
"date_added": "2026-06-26",
|
|
35769
|
+
"plugin": {
|
|
35770
|
+
"targets": {
|
|
35771
|
+
"codex": "supported",
|
|
35772
|
+
"claude": "supported"
|
|
35773
|
+
},
|
|
35774
|
+
"setup": {
|
|
35775
|
+
"type": "none",
|
|
35776
|
+
"summary": "",
|
|
35777
|
+
"docs": null
|
|
35778
|
+
},
|
|
35779
|
+
"reasons": []
|
|
35780
|
+
}
|
|
35781
|
+
},
|
|
35606
35782
|
{
|
|
35607
35783
|
"id": "web-scraper",
|
|
35608
35784
|
"path": "skills/web-scraper",
|