opencode-skills-collection 3.0.13 → 3.0.14
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 +7 -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/mcp-tool-developer/SKILL.md +132 -0
- package/bundled-skills/news-sentiment-engine/SKILL.md +104 -0
- package/bundled-skills/options-flow-analyzer/SKILL.md +96 -0
- package/bundled-skills/tokenwise/SKILL.md +81 -0
- package/bundled-skills/wechat-official-account-strategist/SKILL.md +124 -0
- package/bundled-skills/x-twitter-scraper/SKILL.md +22 -3
- package/bundled-skills/xiaohongshu-content-strategist/SKILL.md +117 -0
- package/package.json +1 -1
- package/skills_index.json +133 -1
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schemaVersion": 1,
|
|
3
|
-
"updatedAt": "2026-05-
|
|
3
|
+
"updatedAt": "2026-05-14T01:58:40.764Z",
|
|
4
4
|
"entries": [
|
|
5
5
|
"00-andruia-consultant",
|
|
6
6
|
"007",
|
|
@@ -855,6 +855,7 @@
|
|
|
855
855
|
"maxia",
|
|
856
856
|
"mcp-builder",
|
|
857
857
|
"mcp-builder-ms",
|
|
858
|
+
"mcp-tool-developer",
|
|
858
859
|
"memory-forensics",
|
|
859
860
|
"memory-safety-patterns",
|
|
860
861
|
"memory-systems",
|
|
@@ -915,6 +916,7 @@
|
|
|
915
916
|
"network-engineer",
|
|
916
917
|
"networkx",
|
|
917
918
|
"new-rails-project",
|
|
919
|
+
"news-sentiment-engine",
|
|
918
920
|
"nextjs-app-router-patterns",
|
|
919
921
|
"nextjs-best-practices",
|
|
920
922
|
"nextjs-supabase-auth",
|
|
@@ -968,6 +970,7 @@
|
|
|
968
970
|
"one-drive-automation",
|
|
969
971
|
"openapi-spec-generation",
|
|
970
972
|
"openclaw-github-repo-commander",
|
|
973
|
+
"options-flow-analyzer",
|
|
971
974
|
"oral-health-analyzer",
|
|
972
975
|
"orchestrate-batch-refactor",
|
|
973
976
|
"os-scripting",
|
|
@@ -1326,6 +1329,7 @@
|
|
|
1326
1329
|
"tiktok-automation",
|
|
1327
1330
|
"tmux",
|
|
1328
1331
|
"todoist-automation",
|
|
1332
|
+
"tokenwise",
|
|
1329
1333
|
"tool-design",
|
|
1330
1334
|
"tool-use-guardian",
|
|
1331
1335
|
"top-web-vulnerabilities",
|
|
@@ -1409,6 +1413,7 @@
|
|
|
1409
1413
|
"web3-testing",
|
|
1410
1414
|
"webapp-testing",
|
|
1411
1415
|
"webflow-automation",
|
|
1416
|
+
"wechat-official-account-strategist",
|
|
1412
1417
|
"weightloss-analyzer",
|
|
1413
1418
|
"wellally-tech",
|
|
1414
1419
|
"whatsapp-automation",
|
|
@@ -1438,6 +1443,7 @@
|
|
|
1438
1443
|
"x-article-publisher-skill",
|
|
1439
1444
|
"x-twitter-scraper",
|
|
1440
1445
|
"x402-express-wrapper",
|
|
1446
|
+
"xiaohongshu-content-strategist",
|
|
1441
1447
|
"xlsx-official",
|
|
1442
1448
|
"xss-html-injection",
|
|
1443
1449
|
"xvary-stock-research",
|
|
@@ -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,459+ skills."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
# Jetski/Cortex + Gemini: safe integration with 1,
|
|
6
|
+
# Jetski/Cortex + Gemini: safe integration with 1,459+ 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,459+ 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,459+ 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,459+ 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,459+ 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,459+ 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,459+ 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,459+ 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,459+ 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,459+ 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,459+ 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,459+ 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,459+ 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,459+ 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,459+ 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,459+ 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,459+ 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,459+ total) │
|
|
205
205
|
└─────────────────────────────────────────┘
|
|
206
206
|
```
|
|
207
207
|
|
|
@@ -0,0 +1,132 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: mcp-tool-developer
|
|
3
|
+
description: "Build Model Context Protocol (MCP) servers and tools from scratch. Full-stack MCP development with TypeScript/Python, testing, deployment, and registry publishing."
|
|
4
|
+
category: developer-tools
|
|
5
|
+
risk: safe
|
|
6
|
+
source: community
|
|
7
|
+
source_repo: demo112/yunqu-ai-skills
|
|
8
|
+
source_type: community
|
|
9
|
+
date_added: "2026-05-13"
|
|
10
|
+
author: yundu-ai
|
|
11
|
+
tags: [mcp, ai-agent, tool-development, typescript, python, llm, model-context-protocol]
|
|
12
|
+
tools: [claude, cursor, gemini]
|
|
13
|
+
---
|
|
14
|
+
|
|
15
|
+
# MCP Tool Developer
|
|
16
|
+
|
|
17
|
+
## Overview
|
|
18
|
+
|
|
19
|
+
Expert at building Model Context Protocol (MCP) servers that give AI agents new capabilities. Covers the full MCP development lifecycle: specification, implementation, testing, deployment, and registry publishing. Supports both TypeScript and Python with production-ready patterns.
|
|
20
|
+
|
|
21
|
+
This skill understands MCP specification primitives (tools, resources, prompts, sampling), transport options (stdio, SSE, Streamable HTTP), and the tool design patterns that make MCP servers reliable and composable.
|
|
22
|
+
|
|
23
|
+
## When to Use This Skill
|
|
24
|
+
|
|
25
|
+
- Use when building a new MCP server from scratch
|
|
26
|
+
- Use when wrapping an existing API as an MCP tool
|
|
27
|
+
- Use when debugging MCP server issues
|
|
28
|
+
- Use when designing the tool schema for an MCP server
|
|
29
|
+
- Use when publishing an MCP server to a registry
|
|
30
|
+
|
|
31
|
+
## How It Works
|
|
32
|
+
|
|
33
|
+
### Step 1: Define the MCP Server Scope
|
|
34
|
+
|
|
35
|
+
Identify what capabilities the server should expose:
|
|
36
|
+
- **Tools** - Functions the LLM can call (primary use case)
|
|
37
|
+
- **Resources** - Data the LLM can read (files, APIs, databases)
|
|
38
|
+
- **Prompts** - Reusable prompt templates
|
|
39
|
+
|
|
40
|
+
Choose the transport:
|
|
41
|
+
- **stdio** - For local CLI tools (Claude Code, Cursor)
|
|
42
|
+
- **SSE (Server-Sent Events)** - For remote/hosted tools
|
|
43
|
+
- **Streamable HTTP** - New in MCP spec for modern deployments
|
|
44
|
+
|
|
45
|
+
### Step 2: Design the Tool Schema
|
|
46
|
+
|
|
47
|
+
Define input/output schemas before writing implementation:
|
|
48
|
+
|
|
49
|
+
```typescript
|
|
50
|
+
{
|
|
51
|
+
name: "tool_name",
|
|
52
|
+
description: "What this tool does (visible to the LLM)",
|
|
53
|
+
inputSchema: {
|
|
54
|
+
type: "object",
|
|
55
|
+
properties: { ... },
|
|
56
|
+
required: [ ... ]
|
|
57
|
+
}
|
|
58
|
+
}
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
### Step 3: Implement the Server
|
|
62
|
+
|
|
63
|
+
Create the server with proper error handling, validation, and logging. Use the official MCP SDK for TypeScript (@modelcontextprotocol/sdk) or Python (mcp).
|
|
64
|
+
|
|
65
|
+
### Step 4: Test and Deploy
|
|
66
|
+
|
|
67
|
+
Test with the MCP Inspector, validate tool schemas, handle edge cases, then deploy locally or remotely.
|
|
68
|
+
|
|
69
|
+
## Examples
|
|
70
|
+
|
|
71
|
+
### Example 1: TypeScript MCP Server
|
|
72
|
+
|
|
73
|
+
```typescript
|
|
74
|
+
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
|
|
75
|
+
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
|
|
76
|
+
import { z } from "zod";
|
|
77
|
+
|
|
78
|
+
const server = new McpServer({ name: "my-tools", version: "1.0.0" });
|
|
79
|
+
|
|
80
|
+
server.tool("greet", "Greet someone by name",
|
|
81
|
+
{ name: z.string().describe("Person's name") },
|
|
82
|
+
async ({ name }) => ({ content: [{ type: "text", text: `Hello, ${name}!` }] })
|
|
83
|
+
);
|
|
84
|
+
|
|
85
|
+
const transport = new StdioServerTransport();
|
|
86
|
+
await server.connect(transport);
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
### Example 2: API Wrapper Pattern
|
|
90
|
+
|
|
91
|
+
Wrap an external API as an MCP tool with auth, rate limiting, and error handling:
|
|
92
|
+
- Map API endpoints to tools
|
|
93
|
+
- Handle auth via environment variables
|
|
94
|
+
- Transform API responses to LLM-friendly format
|
|
95
|
+
- Add retry logic with exponential backoff
|
|
96
|
+
|
|
97
|
+
## Best Practices
|
|
98
|
+
|
|
99
|
+
- Build small, focused tools that can be chained rather than monolithic tools
|
|
100
|
+
- Return structured errors, not crashes - tools should fail gracefully
|
|
101
|
+
- Define schemas before implementation
|
|
102
|
+
- Include descriptions that help the LLM understand when and how to use each tool
|
|
103
|
+
- Validate all inputs against the schema
|
|
104
|
+
- Add rate limiting for external API calls
|
|
105
|
+
- Use environment variables for secrets, never hardcode credentials
|
|
106
|
+
|
|
107
|
+
## Limitations
|
|
108
|
+
|
|
109
|
+
- This skill provides guidance and code generation; actual runtime testing requires a development environment
|
|
110
|
+
- MCP specification is evolving; always check the latest spec version
|
|
111
|
+
- Security review is essential before deploying tools that handle sensitive data
|
|
112
|
+
|
|
113
|
+
## Security and Safety Notes
|
|
114
|
+
|
|
115
|
+
- Never hardcode API keys or credentials in tool implementations
|
|
116
|
+
- Use environment variables or secret managers for all authentication
|
|
117
|
+
- Validate and sanitize all inputs to prevent injection attacks
|
|
118
|
+
- Rate limit external API calls to prevent abuse
|
|
119
|
+
- Review tool permissions carefully - tools can access files, networks, and execute code
|
|
120
|
+
|
|
121
|
+
## Common Pitfalls
|
|
122
|
+
|
|
123
|
+
- **Problem:** LLM calls tools with wrong parameters
|
|
124
|
+
**Solution:** Improve tool descriptions and add examples in the description field. The LLM reads descriptions to decide how to call tools.
|
|
125
|
+
|
|
126
|
+
- **Problem:** Tool times out on large inputs
|
|
127
|
+
**Solution:** Add input size validation and pagination. Stream large responses instead of buffering.
|
|
128
|
+
|
|
129
|
+
## Related Skills
|
|
130
|
+
|
|
131
|
+
- `api-integration-architect` - For API design patterns used in MCP tools
|
|
132
|
+
- `security-audit-code-reviewer` - For reviewing MCP server code security
|
|
@@ -0,0 +1,104 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: news-sentiment-engine
|
|
3
|
+
description: Multi-source RSS news aggregation with Claude-powered sentiment analysis and structured briefing output
|
|
4
|
+
category: research
|
|
5
|
+
risk: safe
|
|
6
|
+
source: community
|
|
7
|
+
source_repo: tellmefrankie/news-engine
|
|
8
|
+
source_type: community
|
|
9
|
+
date_added: "2026-05-13"
|
|
10
|
+
author: tellmefrankie
|
|
11
|
+
tags: [news, rss, sentiment-analysis, briefing, research]
|
|
12
|
+
tools: [claude, websearch]
|
|
13
|
+
---
|
|
14
|
+
# News Sentiment Engine (Free)
|
|
15
|
+
|
|
16
|
+
Collect and analyze AI/tech news from multiple sources with Claude-powered sentiment analysis. Open source lite version.
|
|
17
|
+
|
|
18
|
+
## When to Use
|
|
19
|
+
|
|
20
|
+
- Use when preparing a concise AI or technology news briefing from multiple RSS sources.
|
|
21
|
+
- Use when you need ranked article summaries with sentiment, tags, and impact scoring.
|
|
22
|
+
- Use when monitoring industry changes across product launches, policy moves, and infrastructure shifts.
|
|
23
|
+
- Use when deduplicating overlapping coverage before writing a daily or weekly briefing.
|
|
24
|
+
|
|
25
|
+
## What it does
|
|
26
|
+
|
|
27
|
+
- Collects news from 4+ RSS feeds (TechCrunch, The Verge, Ars Technica, Hacker News)
|
|
28
|
+
- Deduplicates articles across sources
|
|
29
|
+
- Ranks by importance (industry impact, technology trends, policy changes)
|
|
30
|
+
- Generates structured briefing with sentiment tags
|
|
31
|
+
- Outputs formatted briefing card
|
|
32
|
+
|
|
33
|
+
## Usage
|
|
34
|
+
|
|
35
|
+
```
|
|
36
|
+
Collect latest AI/tech news from RSS feeds.
|
|
37
|
+
Rank top 5 by importance to the tech industry.
|
|
38
|
+
For each: summary (2-3 sentences), sentiment (positive/negative/neutral),
|
|
39
|
+
impact score (1-5), industry tags, one-sentence commentary.
|
|
40
|
+
Output as a structured briefing card.
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
## Example Output
|
|
44
|
+
|
|
45
|
+
```
|
|
46
|
+
AI/Tech News Briefing — 2026-05-13
|
|
47
|
+
|
|
48
|
+
1. OpenAI announces GPT-5 with 2M context window
|
|
49
|
+
Source: TechCrunch | Impact: 5/5
|
|
50
|
+
Tags: #AI #LLM #OpenAI
|
|
51
|
+
Sentiment: Positive
|
|
52
|
+
|
|
53
|
+
Summary: OpenAI unveiled GPT-5 with a 2M token context window and
|
|
54
|
+
improved reasoning. Enterprise pricing starts at $0.03/1k tokens.
|
|
55
|
+
|
|
56
|
+
Commentary: Direct competitive pressure on Anthropic Claude 3.5.
|
|
57
|
+
Enterprise deals may shift in H2 2026.
|
|
58
|
+
|
|
59
|
+
2. EU AI Act enforcement begins for high-risk systems
|
|
60
|
+
Source: The Verge | Impact: 4/5
|
|
61
|
+
Tags: #Regulation #EU #Compliance
|
|
62
|
+
Sentiment: Neutral
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
## Output Format
|
|
66
|
+
|
|
67
|
+
For each article:
|
|
68
|
+
- Title + source + publish date
|
|
69
|
+
- Summary (2-3 sentences)
|
|
70
|
+
- Industry tags: [AI, Semiconductor, Cloud, etc.]
|
|
71
|
+
- Sentiment: Positive/Negative/Neutral
|
|
72
|
+
- Impact score: 1-5
|
|
73
|
+
- Commentary: 1-sentence industry perspective
|
|
74
|
+
|
|
75
|
+
## Setup
|
|
76
|
+
|
|
77
|
+
```bash
|
|
78
|
+
git clone https://github.com/tellmefrankie/news-engine
|
|
79
|
+
cd news-engine
|
|
80
|
+
pnpm install
|
|
81
|
+
cp .env.example .env
|
|
82
|
+
# Requires: ANTHROPIC_API_KEY
|
|
83
|
+
pnpm dev -- --collect-only
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
No paid APIs required for free tier. Anthropic API key only.
|
|
87
|
+
|
|
88
|
+
## Limitations
|
|
89
|
+
|
|
90
|
+
- RSS feeds can lag, disappear, throttle, or duplicate syndicated coverage.
|
|
91
|
+
- Sentiment and impact scores are briefing aids, not authoritative market or policy analysis.
|
|
92
|
+
- The example setup runs third-party code; review the repository and environment variables before use.
|
|
93
|
+
- Outputs should be cross-checked against original article sources before publication or investment use.
|
|
94
|
+
|
|
95
|
+
## Pro Version
|
|
96
|
+
|
|
97
|
+
Free tier covers news collection and basic analysis.
|
|
98
|
+
|
|
99
|
+
**Full bundle — $29 one-time**: Investment-grade analysis (portfolio impact scoring, options flow correlation, earnings catalyst detection), Telegram auto-delivery.
|
|
100
|
+
→ https://jaehyunpark.gumroad.com/l/tcyahy
|
|
101
|
+
|
|
102
|
+
## Author
|
|
103
|
+
|
|
104
|
+
Core module from a production news analysis engine processing 50+ articles daily since 2026.
|
|
@@ -0,0 +1,96 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: options-flow-analyzer
|
|
3
|
+
description: Real vs lottery call separation for options P/C ratio analysis — prevents signal inversion from deep OTM noise
|
|
4
|
+
category: finance
|
|
5
|
+
risk: safe
|
|
6
|
+
source: community
|
|
7
|
+
source_type: community
|
|
8
|
+
date_added: "2026-05-13"
|
|
9
|
+
author: tellmefrankie
|
|
10
|
+
tags: [options, sentiment-analysis, trading, polygon, market-analysis]
|
|
11
|
+
tools: [websearch]
|
|
12
|
+
---
|
|
13
|
+
# Options Flow Analyzer
|
|
14
|
+
|
|
15
|
+
Analyze options chain data with real vs lottery call separation — the key insight that prevents P/C ratio misinterpretation. Uses Polygon.io API.
|
|
16
|
+
|
|
17
|
+
## When to Use
|
|
18
|
+
|
|
19
|
+
- Use when raw put/call ratios appear bullish or bearish but may be distorted by cheap deep OTM contracts.
|
|
20
|
+
- Use when comparing options flow across watchlists, holdings, sectors, or event-driven names.
|
|
21
|
+
- Use when you need to separate institutional hedging from speculative lottery-ticket activity.
|
|
22
|
+
- Use when tracking options anomalies against a recent baseline.
|
|
23
|
+
|
|
24
|
+
## What it does
|
|
25
|
+
|
|
26
|
+
Standard P/C ratio analysis is misleading. A P/C of 0.35 looks "extremely bullish" but may be 84% lottery calls ($0.01-$0.09 OTM options).
|
|
27
|
+
|
|
28
|
+
This skill separates:
|
|
29
|
+
- **Real calls**: Strike price within 5% of stock price, meaningful premium
|
|
30
|
+
- **Lottery calls**: Deep OTM, cheap premium, speculative bets
|
|
31
|
+
- **Real puts**: Actual hedging activity
|
|
32
|
+
- **Lottery puts**: Cheap downside bets
|
|
33
|
+
|
|
34
|
+
## Analysis Output
|
|
35
|
+
|
|
36
|
+
For each ticker:
|
|
37
|
+
- Real P/C ratio (excludes lottery noise)
|
|
38
|
+
- Lottery percentage (what % of volume is speculation)
|
|
39
|
+
- Per-expiry breakdown (weekly vs monthly vs LEAPS)
|
|
40
|
+
- Anomaly detection: P/C shifts >0.3, Call OI surges >30%, IV spikes >20%
|
|
41
|
+
- Sentiment classification: Bullish/Bearish/Neutral with confidence
|
|
42
|
+
|
|
43
|
+
## Example Output
|
|
44
|
+
|
|
45
|
+
```
|
|
46
|
+
Options Flow Summary — 2026-05-13
|
|
47
|
+
|
|
48
|
+
HOLDINGS:
|
|
49
|
+
CEG $299.69 | Raw P/C: 1.06 | Lottery: 61% | Adj P/C: 2.72 BEARISH (was neutral raw)
|
|
50
|
+
IREN $55.15 | Raw P/C: 0.83 | Lottery: 34% | Adj P/C: 0.55 BULLISH
|
|
51
|
+
KTOS $56.99 | Raw P/C: 0.53 | Lottery: 28% | Adj P/C: 0.38 EXTREME BULLISH
|
|
52
|
+
RXRX $3.26 | Raw P/C: 0.38 | Lottery: 84% | Adj P/C: 2.37 BEARISH (was extreme bullish raw)
|
|
53
|
+
|
|
54
|
+
SECTORS:
|
|
55
|
+
XLI | Raw P/C: 5.32 | Lottery: 8% | Adj P/C: 4.89 INSTITUTIONAL HEDGE
|
|
56
|
+
|
|
57
|
+
ANOMALIES:
|
|
58
|
+
XLI: P/C 5.32 vs 30-day baseline 0.87 — 4.5 std deviations above normal
|
|
59
|
+
RXRX: 84% lottery calls — raw P/C signal completely inverted after filtering
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
## Configuration
|
|
63
|
+
|
|
64
|
+
```
|
|
65
|
+
Analyze options flow for my watchlist:
|
|
66
|
+
Holdings: CEG, IREN, KTOS, RXRX, TEM
|
|
67
|
+
Sectors: SPY, QQQ, XLI, XLK
|
|
68
|
+
Separate real vs lottery calls (threshold: premium < $0.10, delta < 0.05).
|
|
69
|
+
Flag anomalies vs 30-day baseline.
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
## Requirements
|
|
73
|
+
|
|
74
|
+
- Polygon.io API key (free tier covers basic data; paid tier for full chain)
|
|
75
|
+
- WebSearch for cross-verification
|
|
76
|
+
|
|
77
|
+
## Limitations
|
|
78
|
+
|
|
79
|
+
- Options data can be delayed, incomplete, or unavailable depending on the Polygon.io plan.
|
|
80
|
+
- Heuristics such as premium and delta thresholds need adjustment for ticker price, volatility, and expiry.
|
|
81
|
+
- Sentiment classifications are analytical signals, not financial advice or trade recommendations.
|
|
82
|
+
- Always cross-check unusual flow against price action, news catalysts, liquidity, and risk controls.
|
|
83
|
+
|
|
84
|
+
## Key Discovery
|
|
85
|
+
|
|
86
|
+
This real/lottery separation was discovered during live portfolio management when RXRX showed P/C 0.35 (looks extremely bullish) but was actually 84% lottery calls at $0.01-$0.09. The "bullish signal" was noise. This skill prevents that mistake.
|
|
87
|
+
|
|
88
|
+
## Pricing
|
|
89
|
+
|
|
90
|
+
Free: Basic P/C ratio for 3 tickers
|
|
91
|
+
**Full bundle — $29 one-time**: Real/lottery separation + anomaly detection + per-expiry + unlimited tickers
|
|
92
|
+
→ https://jaehyunpark.gumroad.com/l/tcyahy
|
|
93
|
+
|
|
94
|
+
## Author
|
|
95
|
+
|
|
96
|
+
Built from a real trading mistake that cost money. The real/lottery discovery is documented and battle-tested across 17 tickers over 2+ months.
|
|
@@ -0,0 +1,81 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: tokenwise
|
|
3
|
+
description: "Measurement-driven model router for Claude Code. Routes Haiku/Sonnet/Opus per task class, logs every routed task with real $ numbers, and A/B tests cheaper tiers before you trust the savings."
|
|
4
|
+
category: developer-tools
|
|
5
|
+
risk: safe
|
|
6
|
+
source: community
|
|
7
|
+
source_repo: CodeShuX/tokenwise
|
|
8
|
+
source_type: community
|
|
9
|
+
date_added: "2026-05-12"
|
|
10
|
+
author: CodeShuX
|
|
11
|
+
tags: [model-routing, token-optimization, cost-reduction, anthropic, haiku, sonnet, opus, claude-code, ab-testing, measurement]
|
|
12
|
+
tools: [claude]
|
|
13
|
+
license: "MIT"
|
|
14
|
+
license_source: "https://github.com/CodeShuX/tokenwise/blob/main/LICENSE"
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
# TokenWise — Measurement-Driven Model Router
|
|
18
|
+
|
|
19
|
+
## Overview
|
|
20
|
+
|
|
21
|
+
A Claude Code skill that auto-routes subtasks to the cheapest model that can handle them (Haiku for grunt work, Sonnet for scoped reasoning, Opus only for synthesis), then logs every routed task to a local NDJSON with real token + cost numbers. Includes an A/B test subcommand that runs the same task across multiple tiers and scores quality, so the routing decisions are verified against the user's real workload — not estimated.
|
|
22
|
+
|
|
23
|
+
Anthropic's own bug tracker (Issue #27665) reports 93.8% of Max-subscriber Claude Code tokens flow to Opus. Existing routers (claude-router, wshobson, VoltAgent) either pin models statically or route by vibes-based heuristics with no measurement. TokenWise fills the measurement gap.
|
|
24
|
+
|
|
25
|
+
## When to use
|
|
26
|
+
|
|
27
|
+
- Cutting Claude Code token spend without sacrificing output quality
|
|
28
|
+
- Validating whether Haiku/Sonnet is "good enough" for a specific task class before trusting auto-routing
|
|
29
|
+
- Auditing where Opus tokens are actually being burned
|
|
30
|
+
- Logging per-session cost data for finance or chargeback
|
|
31
|
+
|
|
32
|
+
## Subcommands
|
|
33
|
+
|
|
34
|
+
- `/tokenwise:install` — guided installer with diff preview, automatic backups, and `--dry-run` mode
|
|
35
|
+
- `/tokenwise:report` — per-session token + cost summary vs all-Opus baseline
|
|
36
|
+
- `/tokenwise:summary [--week|--month|--all]` — historical aggregate with trend
|
|
37
|
+
- `/tokenwise:ab "<task>"` — A/B test the same task at multiple tiers, generates a markdown comparison
|
|
38
|
+
- `/tokenwise:undo` — restore CLAUDE.md / settings.json from backup
|
|
39
|
+
|
|
40
|
+
## Routing taxonomy
|
|
41
|
+
|
|
42
|
+
| Tier | Model | Task class |
|
|
43
|
+
|---|---|---|
|
|
44
|
+
| Mechanical | Haiku 4.5 | file reads, grep, format, rename, simple edits, doc lookups |
|
|
45
|
+
| Scoped reasoning | Sonnet 4.6 | single-file refactor, scoped research, test writing |
|
|
46
|
+
| Synthesis | Opus 4.7 | architecture decisions, multi-file refactor, security review |
|
|
47
|
+
|
|
48
|
+
Safety caps:
|
|
49
|
+
- Haiku never spawns further subagents
|
|
50
|
+
- Max spawn depth = 2
|
|
51
|
+
- Subagents that need a smarter model return to parent — they never escalate on their own
|
|
52
|
+
- Tasks under 100 chars with no file context run inline (subagent overhead > savings)
|
|
53
|
+
- Subagent context >30k tokens bumps a tier
|
|
54
|
+
|
|
55
|
+
## Privacy
|
|
56
|
+
|
|
57
|
+
Zero telemetry. All logs in `.tokenwise/log.ndjson` local to the project. Task descriptions truncated to 80 chars and stripped of file contents before logging. No analytics endpoint exists in the source.
|
|
58
|
+
|
|
59
|
+
## Install
|
|
60
|
+
|
|
61
|
+
In any Claude Code session:
|
|
62
|
+
|
|
63
|
+
```
|
|
64
|
+
/plugin marketplace add CodeShuX/tokenwise
|
|
65
|
+
/plugin install tokenwise@tokenwise
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
Then run `/tokenwise:install` and follow the guided prompts.
|
|
69
|
+
|
|
70
|
+
## Limitations
|
|
71
|
+
|
|
72
|
+
- Token counts approximate to ±2% vs Anthropic billing
|
|
73
|
+
- A/B test mode costs extra tokens (one task × N tiers) — intentional one-time validation
|
|
74
|
+
- Anthropic-only by design (use LiteLLM or OpenRouter for cross-vendor)
|
|
75
|
+
- Subagent `model:` param has known silent-fail bugs on some Claude Code builds — skill probes for this at install and refuses to configure if routing is broken
|
|
76
|
+
|
|
77
|
+
## Source
|
|
78
|
+
|
|
79
|
+
- Repo: https://github.com/CodeShuX/tokenwise
|
|
80
|
+
- License: MIT
|
|
81
|
+
- Author: CodeShuX
|
|
@@ -0,0 +1,124 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: wechat-official-account-strategist
|
|
3
|
+
description: "Grow WeChat Official Accounts (微信公众号) with high-conversion content strategy, title formulas, article architecture, and Mini-Program integration."
|
|
4
|
+
category: marketing
|
|
5
|
+
risk: safe
|
|
6
|
+
source: community
|
|
7
|
+
source_repo: demo112/yunqu-ai-skills
|
|
8
|
+
source_type: community
|
|
9
|
+
date_added: "2026-05-13"
|
|
10
|
+
author: yundu-ai
|
|
11
|
+
tags: [wechat, chinese-market, content-strategy, marketing, 公众号, 微信]
|
|
12
|
+
tools: [claude, cursor, gemini]
|
|
13
|
+
---
|
|
14
|
+
|
|
15
|
+
# WeChat Official Account Strategist
|
|
16
|
+
|
|
17
|
+
## Overview
|
|
18
|
+
|
|
19
|
+
Expert strategist for WeChat Official Accounts (微信公众号), China's most powerful content marketing channel with 1.3 billion WeChat users. Creates high-conversion article strategies with proven title formulas, reading-flow optimization, and Mini-Program integration paths.
|
|
20
|
+
|
|
21
|
+
This skill understands the unique WeChat ecosystem: closed garden distribution, Moments sharing mechanics, subscription vs. service account differences, and the critical role of the first fold (首屏) in reader retention.
|
|
22
|
+
|
|
23
|
+
## When to Use This Skill
|
|
24
|
+
|
|
25
|
+
- Use when creating articles for WeChat Official Accounts
|
|
26
|
+
- Use when planning WeChat content strategy or editorial calendar
|
|
27
|
+
- Use when optimizing article open rates and sharing rates
|
|
28
|
+
- Use when designing WeChat-driven sales funnels
|
|
29
|
+
- Use when converting readers to Mini-Program users or private traffic (私域流量)
|
|
30
|
+
|
|
31
|
+
## How It Works
|
|
32
|
+
|
|
33
|
+
### Step 1: Account Type Analysis
|
|
34
|
+
|
|
35
|
+
Identify the account type and its constraints:
|
|
36
|
+
- **Subscription Account (订阅号)**: 1 push per day, folded in subscription folder
|
|
37
|
+
- **Service Account (服务号)**: 4 pushes per month, appears in main chat list
|
|
38
|
+
- **Enterprise Account**: Internal communication and CRM
|
|
39
|
+
|
|
40
|
+
### Step 2: Title Engineering
|
|
41
|
+
|
|
42
|
+
Apply proven title formulas for WeChat:
|
|
43
|
+
|
|
44
|
+
1. **Curiosity Gap**: "为什么XXX却YYY?" (Why X but Y?)
|
|
45
|
+
2. **Counter-intuitive**: "一直以为XXX,原来YYY" (Always thought X, turns out Y)
|
|
46
|
+
3. **Social Proof**: "XXX万人都在用的..." (X million people use this)
|
|
47
|
+
4. **Urgency**: "再不看就晚了!" (Read before it's too late)
|
|
48
|
+
5. **Value Promise**: "看完这篇,你就懂了..." (After reading this, you'll understand)
|
|
49
|
+
6. **Identity**: "XXX的人,都有一共性" (People who X share this trait)
|
|
50
|
+
|
|
51
|
+
### Step 3: Article Architecture
|
|
52
|
+
|
|
53
|
+
Structure for WeChat's reading behavior:
|
|
54
|
+
1. **First Fold (首屏)** - Hook + value promise (visible without scrolling)
|
|
55
|
+
2. **Ramp (铺垫)** - Build context, establish credibility
|
|
56
|
+
3. **Core Content (核心)** - Deliver the promised value
|
|
57
|
+
4. **Emotional Peak (情感高潮)** - Create sharing motivation
|
|
58
|
+
5. **CTA (行动呼唤)** - Clear next step (follow, share, click Mini-Program)
|
|
59
|
+
|
|
60
|
+
### Step 4: Distribution Optimization
|
|
61
|
+
|
|
62
|
+
Optimize for WeChat's sharing mechanics:
|
|
63
|
+
- **Moments (朋友圈)**: Craft share-worthy pull quotes
|
|
64
|
+
- **Direct Share (转发)**: Provide suggested forwarding text
|
|
65
|
+
- **In-article search**: Place keywords for WeChat's article search index
|
|
66
|
+
|
|
67
|
+
## Examples
|
|
68
|
+
|
|
69
|
+
### Example 1: Tech Company Thought Leadership
|
|
70
|
+
|
|
71
|
+
```
|
|
72
|
+
Title: 程序员35岁危机?我和10个技术总监聊了聊,发现一个规律
|
|
73
|
+
Structure:
|
|
74
|
+
首屏: 35岁真的会失业吗?数据说话...
|
|
75
|
+
铺垫: 调研背景,10位总监的行业分布
|
|
76
|
+
核心: 3个关键发现,打破刻板印象
|
|
77
|
+
高潮: "真正淘汰你的不是年龄,是..."
|
|
78
|
+
CTA: 关注公众号,回复"职场"获取完整报告
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
### Example 2: E-commerce Product Launch
|
|
82
|
+
|
|
83
|
+
```
|
|
84
|
+
Title: 用了这款面霜一个月,同事问我是不是做了医美
|
|
85
|
+
Structure:
|
|
86
|
+
首屏: 真实使用对比图描述
|
|
87
|
+
铺垫: 皮肤困扰和选品过程
|
|
88
|
+
核心: 成分分析+使用感受+效果时间线
|
|
89
|
+
高潮: "最让我惊喜的是第三周..."
|
|
90
|
+
CTA: 点击小程序链接,限时优惠
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
## Best Practices
|
|
94
|
+
|
|
95
|
+
- Write the first fold as if it is the only thing readers will see (many stop there)
|
|
96
|
+
- Use short paragraphs (2-3 sentences) for mobile readability
|
|
97
|
+
- Include 1 image every 300-500 words to break up text
|
|
98
|
+
- End with a specific, low-friction CTA
|
|
99
|
+
- Maintain consistent voice across articles to build brand recognition
|
|
100
|
+
- Post at peak hours: 7-9am, 12-1pm, 8-10pm (China time)
|
|
101
|
+
|
|
102
|
+
## Limitations
|
|
103
|
+
|
|
104
|
+
- This skill generates text strategy; actual graphic design and layout require additional tools
|
|
105
|
+
- WeChat algorithm updates may change optimal strategies
|
|
106
|
+
- Industry-specific regulations (finance, health, education) may require compliance review
|
|
107
|
+
|
|
108
|
+
## Security and Safety Notes
|
|
109
|
+
|
|
110
|
+
- This skill generates content strategy and copy. It does not access WeChat APIs or accounts.
|
|
111
|
+
- All content should comply with Chinese advertising law, WeChat platform rules, and industry-specific regulations.
|
|
112
|
+
|
|
113
|
+
## Common Pitfalls
|
|
114
|
+
|
|
115
|
+
- **Problem:** High open rate but low completion rate
|
|
116
|
+
**Solution:** Strengthen the first fold hook and reduce article length. WeChat readers have 3-5 minute attention windows.
|
|
117
|
+
|
|
118
|
+
- **Problem:** Low sharing rate
|
|
119
|
+
**Solution:** Add an emotional peak before the CTA. People share content that makes them look smart or caring, not content that sells.
|
|
120
|
+
|
|
121
|
+
## Related Skills
|
|
122
|
+
|
|
123
|
+
- `xiaohongshu-content-strategist` - For short-form visual content on Xiaohongshu
|
|
124
|
+
- `chinese-market-content-engineer` - For multi-platform Chinese content strategy
|
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: x-twitter-scraper
|
|
3
|
-
description: "X/Twitter automation skill for tweet search, follower export,
|
|
3
|
+
description: "X/Twitter automation skill for tweet search, follower export, posting, DMs, webhooks, MCP, SDKs, Hermes Tweet, and TweetClaw."
|
|
4
4
|
category: data
|
|
5
5
|
risk: safe
|
|
6
6
|
source: community
|
|
7
|
-
tags: "[twitter, x-api, tweet-search, twitter-api, twitter-scraper, follower-export, automation, mcp, sdk, webhooks, openclaw, tweetclaw]"
|
|
7
|
+
tags: "[twitter, x-api, tweet-search, twitter-api, twitter-scraper, follower-export, automation, mcp, sdk, webhooks, hermes-agent, hermes-tweet, openclaw, tweetclaw]"
|
|
8
8
|
date_added: "2026-02-28"
|
|
9
9
|
---
|
|
10
10
|
|
|
@@ -12,7 +12,7 @@ date_added: "2026-02-28"
|
|
|
12
12
|
|
|
13
13
|
## Overview
|
|
14
14
|
|
|
15
|
-
Gives AI agents X (Twitter) data and automation workflows through the Xquik platform. Covers tweet search, advanced Twitter search, profile tweets, user lookup, follower export, media download, posting, replies, DMs, giveaway draws, account monitoring, webhooks, 23 bulk extraction tools, MCP, official SDKs, and the TweetClaw OpenClaw plugin.
|
|
15
|
+
Gives AI agents X (Twitter) data and automation workflows through the Xquik platform. Covers tweet search, advanced Twitter search, profile tweets, user lookup, follower export, media download, posting, replies, DMs, giveaway draws, account monitoring, webhooks, 23 bulk extraction tools, MCP, official SDKs, the Hermes Tweet Hermes Agent plugin, and the TweetClaw OpenClaw plugin.
|
|
16
16
|
|
|
17
17
|
## When to Use This Skill
|
|
18
18
|
|
|
@@ -27,6 +27,7 @@ Gives AI agents X (Twitter) data and automation workflows through the Xquik plat
|
|
|
27
27
|
- User wants to run a giveaway draw from tweet replies
|
|
28
28
|
- User needs real-time monitoring of an X account (new tweets, follower changes)
|
|
29
29
|
- User wants webhook delivery of monitored events
|
|
30
|
+
- User wants the Hermes Tweet Hermes Agent plugin with `tweet_explore`, `tweet_read`, and approval-gated `tweet_action`
|
|
30
31
|
- User wants the TweetClaw OpenClaw plugin instead of direct REST or MCP setup
|
|
31
32
|
- User asks about trending topics on X
|
|
32
33
|
|
|
@@ -48,6 +49,16 @@ git clone https://github.com/Xquik-dev/x-twitter-scraper.git .claude/skills/x-tw
|
|
|
48
49
|
git clone https://github.com/Xquik-dev/x-twitter-scraper.git .agents/skills/x-twitter-scraper
|
|
49
50
|
```
|
|
50
51
|
|
|
52
|
+
### Use the Hermes Agent Plugin
|
|
53
|
+
|
|
54
|
+
For Hermes Agent runtime tools, install Hermes Tweet. It wraps the same Xquik API with `tweet_explore` for endpoint discovery, `tweet_read` for read-only calls, and approval-gated `tweet_action` for writes and private actions.
|
|
55
|
+
|
|
56
|
+
```bash
|
|
57
|
+
hermes plugins install Xquik-dev/hermes-tweet --enable
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
Use Hermes Tweet when a Hermes Agent should search Twitter/X, read tweet replies, look up users, export followers, monitor tweets, post tweets, post replies, send DMs, or automate X actions with explicit approval gates.
|
|
61
|
+
|
|
51
62
|
### Use the OpenClaw Plugin
|
|
52
63
|
|
|
53
64
|
For OpenClaw runtime tools, install TweetClaw. It wraps the same Xquik API with `explore` for endpoint discovery and `tweetclaw` for approved calls.
|
|
@@ -84,6 +95,7 @@ export XQUIK_API_KEY="xq_YOUR_KEY_HERE"
|
|
|
84
95
|
| Write Actions | Send tweets, post replies, like, repost, follow, unfollow, and send DMs after explicit approval |
|
|
85
96
|
| SDKs | Official TypeScript, Python, Ruby, Go, Kotlin, Java, PHP, C#, CLI, and Terraform clients |
|
|
86
97
|
| MCP Server | StreamableHTTP endpoint for AI-native integrations |
|
|
98
|
+
| Hermes Tweet Hermes Agent Plugin | Installable `hermes-tweet` runtime with `tweet_explore`, `tweet_read`, and approval-gated `tweet_action` tools |
|
|
87
99
|
| TweetClaw OpenClaw Plugin | Installable `@xquik/tweetclaw` runtime with `explore` and `tweetclaw` tools |
|
|
88
100
|
|
|
89
101
|
## Examples
|
|
@@ -113,6 +125,11 @@ export XQUIK_API_KEY="xq_YOUR_KEY_HERE"
|
|
|
113
125
|
"Monitor @openai for new tweets and notify me via webhook"
|
|
114
126
|
```
|
|
115
127
|
|
|
128
|
+
**Use Hermes Agent:**
|
|
129
|
+
```
|
|
130
|
+
"Use Hermes Tweet to search Twitter/X for this launch, read the tweet replies, and prepare a draft reply for approval"
|
|
131
|
+
```
|
|
132
|
+
|
|
116
133
|
**Bulk extraction:**
|
|
117
134
|
```
|
|
118
135
|
"Extract all followers of @anthropic"
|
|
@@ -150,6 +167,8 @@ export XQUIK_API_KEY="xq_YOUR_KEY_HERE"
|
|
|
150
167
|
|
|
151
168
|
https://github.com/Xquik-dev/x-twitter-scraper
|
|
152
169
|
|
|
170
|
+
Hermes Tweet Hermes Agent plugin: https://github.com/Xquik-dev/hermes-tweet
|
|
171
|
+
|
|
153
172
|
TweetClaw OpenClaw plugin: https://github.com/Xquik-dev/tweetclaw
|
|
154
173
|
|
|
155
174
|
**Maintained By:** [Xquik](https://xquik.com)
|
|
@@ -0,0 +1,117 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: xiaohongshu-content-strategist
|
|
3
|
+
description: "Create viral Xiaohongshu (小红书) content with platform-native strategy, save-rate optimization, trending formats, and search SEO for China's #1 lifestyle platform."
|
|
4
|
+
category: marketing
|
|
5
|
+
risk: safe
|
|
6
|
+
source: community
|
|
7
|
+
source_repo: demo112/yunqu-ai-skills
|
|
8
|
+
source_type: community
|
|
9
|
+
date_added: "2026-05-13"
|
|
10
|
+
author: yundu-ai
|
|
11
|
+
tags: [xiaohongshu, chinese-market, content-strategy, social-media, marketing, 红书, 小红书]
|
|
12
|
+
tools: [claude, cursor, gemini]
|
|
13
|
+
---
|
|
14
|
+
|
|
15
|
+
# Xiaohongshu Content Strategist
|
|
16
|
+
|
|
17
|
+
## Overview
|
|
18
|
+
|
|
19
|
+
Expert content strategist for Xiaohongshu (小红书), China's most influential lifestyle and shopping platform with 300M+ monthly active users. Creates platform-native content optimized for the unique Xiaohongshu algorithm, which prioritizes saves over likes. Bilingual Chinese/English output with cultural sensitivity.
|
|
20
|
+
|
|
21
|
+
This skill understands Xiaohongshu's search-first traffic model, cover image plus title CTR mechanics, and the conversion path from save to sale.
|
|
22
|
+
|
|
23
|
+
## When to Use This Skill
|
|
24
|
+
|
|
25
|
+
- Use when creating content for Xiaohongshu
|
|
26
|
+
- Use when optimizing existing content for better Xiaohongshu performance
|
|
27
|
+
- Use when planning a Xiaohongshu content calendar or strategy
|
|
28
|
+
- Use when adapting international brand content for the Chinese market via Xiaohongshu
|
|
29
|
+
- Use when analyzing Xiaohongshu competitors
|
|
30
|
+
|
|
31
|
+
## How It Works
|
|
32
|
+
|
|
33
|
+
### Step 1: Analyze the Topic
|
|
34
|
+
|
|
35
|
+
Understand the target audience, product, or message. Identify primary keywords for Xiaohongshu's search algorithm. Research trending formats in the relevant category.
|
|
36
|
+
|
|
37
|
+
### Step 2: Choose the Content Format
|
|
38
|
+
|
|
39
|
+
Select from proven formats based on the topic:
|
|
40
|
+
|
|
41
|
+
| Format | Best For | Example |
|
|
42
|
+
|--------|----------|---------|
|
|
43
|
+
| Before/After | Transformations |妆前妆后、装修前后 |
|
|
44
|
+
| Step-by-Step | Tutorials | 5步学会xxx |
|
|
45
|
+
| Comparison | Decisions | A vs B 实测 |
|
|
46
|
+
| Hidden Gems | Discovery | 被低估的xxx |
|
|
47
|
+
| List/Rankings | Quick value | 2025必买的10件 |
|
|
48
|
+
|
|
49
|
+
### Step 3: Generate the Content Package
|
|
50
|
+
|
|
51
|
+
For each post, provide:
|
|
52
|
+
1. **Cover Image Brief** - Visual concept, text overlay under 10 chars, color mood
|
|
53
|
+
2. **Title** (2-3 options) - Primary keyword in first 8 chars, emotional trigger, 18-22 chars optimal
|
|
54
|
+
3. **Body Content** - Hook sentence, short paragraphs, strategic emoji, highlighted key info, CTA
|
|
55
|
+
4. **Hashtags** - 3-5 mix of high-volume and niche tags
|
|
56
|
+
5. **Comment Engagement Plan** - Seed comments and anticipated Q&A
|
|
57
|
+
|
|
58
|
+
### Step 4: Optimize for the Algorithm
|
|
59
|
+
|
|
60
|
+
Apply these ranking factors in priority order:
|
|
61
|
+
1. Save rate - number one ranking signal, content must be reference-worthy
|
|
62
|
+
2. Click-through rate - driven by cover image plus title
|
|
63
|
+
3. Comment depth - conversation quality over count
|
|
64
|
+
4. Completion rate - users who read to the end
|
|
65
|
+
|
|
66
|
+
## Examples
|
|
67
|
+
|
|
68
|
+
### Example 1: Beauty Product Review
|
|
69
|
+
|
|
70
|
+
Title: 用了28天,皮肤真的变好了|实测这款平价精华
|
|
71
|
+
Cover: Before/After face photo with product in corner, soft pink overlay
|
|
72
|
+
Body: 这款精华我用了整整28天,今天来交作业...
|
|
73
|
+
Hashtags: #平价护肤 #精华推荐 #28天打卡
|
|
74
|
+
Seed Comment: "姐妹们,我油皮可以用吗?"
|
|
75
|
+
|
|
76
|
+
### Example 2: Travel Destination
|
|
77
|
+
|
|
78
|
+
Title: 上海被低估的咖啡馆!拍照绝了
|
|
79
|
+
Cover: Cafe interior shot with warm tones, location pin overlay
|
|
80
|
+
Body: 周末不想人挤人?这家藏在法租界的小店...
|
|
81
|
+
Hashtags: #上海咖啡 #周末去哪 #小众探店
|
|
82
|
+
Seed Comment: "地址在哪里呀?"
|
|
83
|
+
|
|
84
|
+
## Best Practices
|
|
85
|
+
|
|
86
|
+
- Sound like a real person sharing a discovery, not a brand broadcasting
|
|
87
|
+
- Front-load keywords in titles (first 8 characters)
|
|
88
|
+
- Use numbers and specific results in titles
|
|
89
|
+
- Keep paragraphs to 2-3 sentences max
|
|
90
|
+
- Include a clear save-worthy takeaway
|
|
91
|
+
- Do not use corporate marketing language
|
|
92
|
+
- Do not ignore mobile formatting (most users are on phones)
|
|
93
|
+
- Do not post without relevant hashtags
|
|
94
|
+
|
|
95
|
+
## Limitations
|
|
96
|
+
|
|
97
|
+
- This skill generates text content strategy; actual image/video creation requires additional tools
|
|
98
|
+
- Trending topics and algorithm details may shift; always validate with current platform data
|
|
99
|
+
- Cultural nuances in specific sub-communities may require human review
|
|
100
|
+
|
|
101
|
+
## Security and Safety Notes
|
|
102
|
+
|
|
103
|
+
- This skill generates content strategy and copy. It does not access Xiaohongshu APIs or user accounts.
|
|
104
|
+
- All content should comply with Chinese advertising law and platform community guidelines.
|
|
105
|
+
|
|
106
|
+
## Common Pitfalls
|
|
107
|
+
|
|
108
|
+
- **Problem:** Low engagement despite good content
|
|
109
|
+
**Solution:** Check title CTR - the cover image plus title combo drives 80 percent of click-through. A/B test 2-3 title options.
|
|
110
|
+
|
|
111
|
+
- **Problem:** Content gets flagged or removed
|
|
112
|
+
**Solution:** Avoid absolute claims and ensure product reviews disclose sponsorships per platform rules.
|
|
113
|
+
|
|
114
|
+
## Related Skills
|
|
115
|
+
|
|
116
|
+
- `wechat-official-account-strategist` - For long-form content strategy on WeChat
|
|
117
|
+
- `chinese-market-content-engineer` - For multi-platform Chinese content strategy
|
package/package.json
CHANGED
package/skills_index.json
CHANGED
|
@@ -18719,6 +18719,28 @@
|
|
|
18719
18719
|
"reasons": []
|
|
18720
18720
|
}
|
|
18721
18721
|
},
|
|
18722
|
+
{
|
|
18723
|
+
"id": "mcp-tool-developer",
|
|
18724
|
+
"path": "skills/mcp-tool-developer",
|
|
18725
|
+
"category": "developer-tools",
|
|
18726
|
+
"name": "mcp-tool-developer",
|
|
18727
|
+
"description": "Build Model Context Protocol (MCP) servers and tools from scratch. Full-stack MCP development with TypeScript/Python, testing, deployment, and registry publishing.",
|
|
18728
|
+
"risk": "safe",
|
|
18729
|
+
"source": "community",
|
|
18730
|
+
"date_added": "2026-05-13",
|
|
18731
|
+
"plugin": {
|
|
18732
|
+
"targets": {
|
|
18733
|
+
"codex": "supported",
|
|
18734
|
+
"claude": "supported"
|
|
18735
|
+
},
|
|
18736
|
+
"setup": {
|
|
18737
|
+
"type": "none",
|
|
18738
|
+
"summary": "",
|
|
18739
|
+
"docs": null
|
|
18740
|
+
},
|
|
18741
|
+
"reasons": []
|
|
18742
|
+
}
|
|
18743
|
+
},
|
|
18722
18744
|
{
|
|
18723
18745
|
"id": "memory-forensics",
|
|
18724
18746
|
"path": "skills/memory-forensics",
|
|
@@ -20087,6 +20109,28 @@
|
|
|
20087
20109
|
"reasons": []
|
|
20088
20110
|
}
|
|
20089
20111
|
},
|
|
20112
|
+
{
|
|
20113
|
+
"id": "news-sentiment-engine",
|
|
20114
|
+
"path": "skills/news-sentiment-engine",
|
|
20115
|
+
"category": "research",
|
|
20116
|
+
"name": "news-sentiment-engine",
|
|
20117
|
+
"description": "Multi-source RSS news aggregation with Claude-powered sentiment analysis and structured briefing output",
|
|
20118
|
+
"risk": "safe",
|
|
20119
|
+
"source": "community",
|
|
20120
|
+
"date_added": "2026-05-13",
|
|
20121
|
+
"plugin": {
|
|
20122
|
+
"targets": {
|
|
20123
|
+
"codex": "supported",
|
|
20124
|
+
"claude": "supported"
|
|
20125
|
+
},
|
|
20126
|
+
"setup": {
|
|
20127
|
+
"type": "none",
|
|
20128
|
+
"summary": "",
|
|
20129
|
+
"docs": null
|
|
20130
|
+
},
|
|
20131
|
+
"reasons": []
|
|
20132
|
+
}
|
|
20133
|
+
},
|
|
20090
20134
|
{
|
|
20091
20135
|
"id": "nextjs-app-router-patterns",
|
|
20092
20136
|
"path": "skills/nextjs-app-router-patterns",
|
|
@@ -21256,6 +21300,28 @@
|
|
|
21256
21300
|
"reasons": []
|
|
21257
21301
|
}
|
|
21258
21302
|
},
|
|
21303
|
+
{
|
|
21304
|
+
"id": "options-flow-analyzer",
|
|
21305
|
+
"path": "skills/options-flow-analyzer",
|
|
21306
|
+
"category": "finance",
|
|
21307
|
+
"name": "options-flow-analyzer",
|
|
21308
|
+
"description": "Real vs lottery call separation for options P/C ratio analysis \u2014 prevents signal inversion from deep OTM noise",
|
|
21309
|
+
"risk": "safe",
|
|
21310
|
+
"source": "community",
|
|
21311
|
+
"date_added": "2026-05-13",
|
|
21312
|
+
"plugin": {
|
|
21313
|
+
"targets": {
|
|
21314
|
+
"codex": "supported",
|
|
21315
|
+
"claude": "supported"
|
|
21316
|
+
},
|
|
21317
|
+
"setup": {
|
|
21318
|
+
"type": "none",
|
|
21319
|
+
"summary": "",
|
|
21320
|
+
"docs": null
|
|
21321
|
+
},
|
|
21322
|
+
"reasons": []
|
|
21323
|
+
}
|
|
21324
|
+
},
|
|
21259
21325
|
{
|
|
21260
21326
|
"id": "oral-health-analyzer",
|
|
21261
21327
|
"path": "skills/oral-health-analyzer",
|
|
@@ -29104,6 +29170,28 @@
|
|
|
29104
29170
|
"reasons": []
|
|
29105
29171
|
}
|
|
29106
29172
|
},
|
|
29173
|
+
{
|
|
29174
|
+
"id": "tokenwise",
|
|
29175
|
+
"path": "skills/tokenwise",
|
|
29176
|
+
"category": "developer-tools",
|
|
29177
|
+
"name": "tokenwise",
|
|
29178
|
+
"description": "Measurement-driven model router for Claude Code. Routes Haiku/Sonnet/Opus per task class, logs every routed task with real $ numbers, and A/B tests cheaper tiers before you trust the savings.",
|
|
29179
|
+
"risk": "safe",
|
|
29180
|
+
"source": "community",
|
|
29181
|
+
"date_added": "2026-05-12",
|
|
29182
|
+
"plugin": {
|
|
29183
|
+
"targets": {
|
|
29184
|
+
"codex": "supported",
|
|
29185
|
+
"claude": "supported"
|
|
29186
|
+
},
|
|
29187
|
+
"setup": {
|
|
29188
|
+
"type": "none",
|
|
29189
|
+
"summary": "",
|
|
29190
|
+
"docs": null
|
|
29191
|
+
},
|
|
29192
|
+
"reasons": []
|
|
29193
|
+
}
|
|
29194
|
+
},
|
|
29107
29195
|
{
|
|
29108
29196
|
"id": "tool-design",
|
|
29109
29197
|
"path": "skills/tool-design",
|
|
@@ -30978,6 +31066,28 @@
|
|
|
30978
31066
|
"reasons": []
|
|
30979
31067
|
}
|
|
30980
31068
|
},
|
|
31069
|
+
{
|
|
31070
|
+
"id": "wechat-official-account-strategist",
|
|
31071
|
+
"path": "skills/wechat-official-account-strategist",
|
|
31072
|
+
"category": "marketing",
|
|
31073
|
+
"name": "wechat-official-account-strategist",
|
|
31074
|
+
"description": "Grow WeChat Official Accounts (\u5fae\u4fe1\u516c\u4f17\u53f7) with high-conversion content strategy, title formulas, article architecture, and Mini-Program integration.",
|
|
31075
|
+
"risk": "safe",
|
|
31076
|
+
"source": "community",
|
|
31077
|
+
"date_added": "2026-05-13",
|
|
31078
|
+
"plugin": {
|
|
31079
|
+
"targets": {
|
|
31080
|
+
"codex": "supported",
|
|
31081
|
+
"claude": "supported"
|
|
31082
|
+
},
|
|
31083
|
+
"setup": {
|
|
31084
|
+
"type": "none",
|
|
31085
|
+
"summary": "",
|
|
31086
|
+
"docs": null
|
|
31087
|
+
},
|
|
31088
|
+
"reasons": []
|
|
31089
|
+
}
|
|
31090
|
+
},
|
|
30981
31091
|
{
|
|
30982
31092
|
"id": "weightloss-analyzer",
|
|
30983
31093
|
"path": "skills/weightloss-analyzer",
|
|
@@ -31599,7 +31709,7 @@
|
|
|
31599
31709
|
"path": "skills/x-twitter-scraper",
|
|
31600
31710
|
"category": "data",
|
|
31601
31711
|
"name": "x-twitter-scraper",
|
|
31602
|
-
"description": "X/Twitter automation skill for tweet search, follower export,
|
|
31712
|
+
"description": "X/Twitter automation skill for tweet search, follower export, posting, DMs, webhooks, MCP, SDKs, Hermes Tweet, and TweetClaw.",
|
|
31603
31713
|
"risk": "safe",
|
|
31604
31714
|
"source": "community",
|
|
31605
31715
|
"date_added": "2026-02-28",
|
|
@@ -31638,6 +31748,28 @@
|
|
|
31638
31748
|
"reasons": []
|
|
31639
31749
|
}
|
|
31640
31750
|
},
|
|
31751
|
+
{
|
|
31752
|
+
"id": "xiaohongshu-content-strategist",
|
|
31753
|
+
"path": "skills/xiaohongshu-content-strategist",
|
|
31754
|
+
"category": "marketing",
|
|
31755
|
+
"name": "xiaohongshu-content-strategist",
|
|
31756
|
+
"description": "Create viral Xiaohongshu (\u5c0f\u7ea2\u4e66) content with platform-native strategy, save-rate optimization, trending formats, and search SEO for China's #1 lifestyle platform.",
|
|
31757
|
+
"risk": "safe",
|
|
31758
|
+
"source": "community",
|
|
31759
|
+
"date_added": "2026-05-13",
|
|
31760
|
+
"plugin": {
|
|
31761
|
+
"targets": {
|
|
31762
|
+
"codex": "supported",
|
|
31763
|
+
"claude": "supported"
|
|
31764
|
+
},
|
|
31765
|
+
"setup": {
|
|
31766
|
+
"type": "none",
|
|
31767
|
+
"summary": "",
|
|
31768
|
+
"docs": null
|
|
31769
|
+
},
|
|
31770
|
+
"reasons": []
|
|
31771
|
+
}
|
|
31772
|
+
},
|
|
31641
31773
|
{
|
|
31642
31774
|
"id": "xlsx-official",
|
|
31643
31775
|
"path": "skills/xlsx-official",
|