gork-analysis
Gork data API. Uses Grok model to analyze tweet comments, extract valuable intelligence from replies, and fetch latest community sentiment on projects or topics.
What this skill does
# Gork Analysis — Tweet Comment Intelligence
**Base URL**: `https://crab-skill.opsat.io`
## API Endpoint
`POST /api/gork/analyze` (requires Crab signature headers)
| Field | Required | Description |
|-----------|----------|---------------------------------------------------------------------|
| `prompt` | Yes | Analysis prompt with context (tweet URL, project name, question) |
| `messages`| No | OpenAI-style message list; takes precedence over `prompt` if given |
Response: plain-text analysis generated by the Grok model.
## Use Cases & Prompt Patterns
### 1. Analyze comments on a specific tweet
Extract valuable information from replies — insider knowledge, community
warnings, technical critiques, sentiment signals.
```json
{
"prompt": "Analyze the comments and replies on this tweet: https://x.com/{username}/status/{id}\n\nFocus on:\n- High-value comments (technical insights, insider info, warnings)\n- Overall sentiment (bullish/bearish/neutral ratio)\n- Notable accounts that replied and their stance\n- Any claims or information worth verifying"
}
```
### 2. Get latest community sentiment on a project
Fetch what people are saying about a project right now.
```json
{
"prompt": "What are the latest comments and discussions about {project_name} (${ticker}) on Twitter/X?\n\nFocus on:\n- Recent criticisms or concerns\n- Notable endorsements or callouts\n- Any news, events, or incidents being discussed\n- Red flags mentioned by the community"
}
```
### 3. Deep dive on a topic or controversy
When Step 4 (deep dig) surfaces a lead worth investigating via social data.
```json
{
"prompt": "Search for discussions about {specific topic} related to {project_name}.\n\nFor example: '{project_name} + scam', '{team_member} + rug', '{project_name} + hack'\n\nSummarize what the community is saying and whether concerns are substantiated."
}
```
## Key Rules
- **Max 2 calls per research** — pick the top tweet (highest engagement) and the
latest tweet (most recent). Do not make additional calls for project-level sentiment.
- **Always include tweet URL or project context in the prompt** — Gork needs specific
context to return useful data, not generic questions
- **Use targeted prompts** — ask for specific information (comments, sentiment, controversy)
rather than broad "analyze this project"
- **Chain with Twitter data** — use tweet URLs discovered from `/api/twitter/tweets`
as input for Gork comment analysis
- **Deep dig exception** — Step 4 may make additional Gork calls only when a
high-value lead requires verification, but still keep total calls minimal
## Timeout & Fallback
Gork calls the Grok model for analysis, so response times are significantly
longer than standard APIs. **Allow up to 120 seconds** before considering a
request timed out.
| Scenario | Behavior |
|-------------------------|-----------------------|
| Gork API key not set | Skip Gork data |
| Response slow (< 120s) | **Keep waiting** — this is normal for LLM analysis |
| Gork request timeout (≥ 120s) | Retry once, then skip and record a warning |
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.