gate-news-communityscan

General Rules

⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding. Do NOT select or call any tool until all rules are read. These rules have the highest priority. → Read gate-runtime-rules.md → Also read info-news-runtime-rules.md for gate-info / gate-news-specific rules (tool degradation, report standards, security, routing degradation, per-skill version checks when

scripts/

is present, and legacy wrapper routing).

Only call MCP tools explicitly listed in this skill. Tools not documented here must NOT be called, even if they exist in the MCP server.
Legacy / routing mode: when Step 0 emits
```
__FALLBACK__
```
, use only the MCP tools listed in this file. When Step 0 emits
```
__ROUTE_CLI__
```
, do not call those MCP tools; delegate to the mapped primary skill per Step 0.

Community Sentiment Scan Skill (X/Twitter focused). Parallel calls fetch X/Twitter discussion analysis and quantitative social sentiment; LLM aggregates into a community insights report.

Trigger Scenarios: Community opinions, Twitter/X discussions, KOL views, social sentiment, etc.

Per-skill updates: This directory includes

scripts/update-skill.sh

and may include

scripts/update-skill.ps1

. ClawHub packages uploaded to the marketplace often omit

update-skill.ps1

(upload-page restriction); GitHub / Bitbucket source trees keep both. Policy: info-news-runtime-rules.md §1. The Trigger update steps below apply in addition to gate-runtime-rules.md; when scripts are present, use this flow for version checks before execution.

Update check — user visibility: Technical failures during version check (missing script, sandbox, network, non-zero exit, no parseable

Result=

line) must not be explained to the user; continue with Execution per info-news-runtime-rules.md. Only successful

check

apply

outcomes may be summarized (including update_available
/ strict exit 3, which is still a success path that requires user confirmation before

apply

). Do not auto-download

update-skill.*

from the network. Static reference if

.ps1

is missing: canonical scripts live in gate/gate-skills under

skills/<name>/scripts/

(same

<name>

as frontmatter).

Step 0 — Wrapper routing probe

This legacy skill is a compatibility alias for the primary CLI skill

gate-news-intel

Before Trigger update, MCP tool selection, or any legacy Execution Workflow, run a deterministic shell probe:

bash

PRIMARY_SKILL="gate-news-intel"
HAS_PRIMARY=0
for root in \
  "$HOME/.cursor/skills" \
  "$HOME/.codex/skills" \
  "$HOME/.openclaw/skills" \
  "$HOME/.agents/skills" \
  "$HOME/.gemini/antigravity/skills"
do
  if [ -f "$root/$PRIMARY_SKILL/SKILL.md" ]; then
    HAS_PRIMARY=1
    break
  fi
done

if command -v gate-cli >/dev/null 2>&1 && [ "$HAS_PRIMARY" = "1" ]; then
  echo "__ROUTE_CLI__"
else
  echo "__FALLBACK__"
fi

Interpretation:

```
__ROUTE_CLI__
```
→ stop here. Do not run Trigger update or the legacy MCP sections below. Follow
```
https://github.com/gate/gate-skills/blob/master/skills/gate-news-intel/SKILL.md
```
and its playbook contract. Carry over the minimum context:
```
symbol
```
and optional
```
time_range
```
.
```
__FALLBACK__
```
→ continue with Trigger update and the legacy MCP workflow in this file.

Trigger update (with Execution)

Default (PD / blocking): On each trigger, run check
first without GATE_SKILL_UPDATE_MODE=auto
. The script only compares local vs remote; if

Result=update_available

, it does not overwrite files. STOP — ask the user whether to update before any apply
, run
, or skill Execution. In sandboxes (e.g. Cursor), use full / all permissions when later running apply
. This matches blocking update confirmation in the independent-script TEST_REPORT: blocking is enforced by these SKILL instructions plus check-only behavior (not by silent auto-apply).

Strict check (Agent / IDE — recommended on
check
): Use GATE_SKILL_CHECK_STRICT=1
. When

Result=update_available

, check
exits 3 and prints GATE_SKILL_CHECK_EXIT=3
— it stops only that shell step. Hard rule: after you ask the user, end this assistant turn; do not call apply
, run
, or MCP in the same message. run
applies without a prior user step — do not use run
in chat for the blocking flow; use check
→ user confirms →
apply
.

Step 1 — Check

Install root:

check

apply

read $DEST/SKILL.md
. Typical $SKILL_ROOT
: $HOME/.cursor/skills/<name>/
, $HOME/.codex/skills/<name>/
, $HOME/.openclaw/skills/<name>/
, $HOME/.agents/skills/<name>/
, $HOME/.gemini/antigravity/skills/<name>/
. Single-arg: the script resolves DEST
in that order when SKILL.md
exists; otherwise DEST
is

scripts/../

. Workspace-only trees need two-arg check
/ apply
with explicit DEST
.

Agent selection rules (run at most one of the fenced examples below; choose by OS and files under

$SKILL_ROOT/scripts/

macOS / Linux / WSL / Git Bash: If
```
update-skill.sh
```
exists → use only the Bash example.
Windows (native PowerShell): If
```
update-skill.ps1
```
exists → use only the PowerShell example.
Windows without
.ps1
(typical ClawHub install): If only
```
update-skill.sh
```
exists → try WSL or Git Bash (
```
bash
```
) using the same command shape as the Bash example. If bash is unavailable or execution fails → skip Step 1 silently (no script stderr or “version check failed” message to the user); proceed to Execution.
Neither script exists: Skip Step 1 silently; proceed to Execution. Do not invent
```
GATE_SKILL_CONFIRM_TOKEN
```
or run
```
apply
```
/
```
revoke-pending
```
.

Bash (blocking — no auto; example Cursor):

bash

GATE_SKILL_CHECK_STRICT=1 bash "$HOME/.cursor/skills/gate-news-communityscan/scripts/update-skill.sh" check "gate-news-communityscan"

PowerShell:

powershell

$env:GATE_SKILL_CHECK_STRICT = '1'
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-news-communityscan\scripts\update-skill.ps1" check "gate-news-communityscan"

Result semantics:

skipped

= no action.

update_available

= remote newer; with blocking flow, do not apply until the user agrees.

check_failed

= could not compare — proceed with current version per info-news-runtime-rules.md; do not surface technical check failure details to the user.

Agent parse (stdout):

GATE_SKILL_UPDATE_AGENT_ACTION=…

. BLOCK_UNTIL_USER_CONFIRMS_UPDATE
→ Step 2 before Execution. CONTINUE_SKILL_EXECUTION
→ no block from the check script.

Step 2 — Confirm or Reject (blocking)

Runtime: Use the same shell family for Step 2 as for Step 1 (Bash vs PowerShell). If Step 1 was skipped, do not run

apply

revoke-pending

If
update_available
:

STOP — do NOT proceed to Execution yet.
Inform the user (e.g. newer version available; summarize if helpful).
Wait for the user’s reply — blocking step.
Hard rule (Cursor / Agent): When
```
check
```
reports update_available
, or BLOCK_UNTIL_USER_CONFIRMS_UPDATE
, or strict exit 3
, end this turn after asking. Only in the user’s next message run apply
(if they agree) or revoke-pending
(if they decline). Do not chain apply
in the same turn as check
for this flow.
- User agrees → run apply
  with GATE_SKILL_CONFIRM_TOKEN
  from strict check
  stdout when required, then Execution.
- User declines → revoke-pending
  , then Execution on the current install.

Two-step gate (strict
check
): apply
/ run
(without GATE_SKILL_UPDATE_MODE=auto
) fail until GATE_SKILL_CONFIRM_TOKEN
matches .gate-skill-apply-token
. User decline → revoke-pending
.

bash

GATE_SKILL_CONFIRM_TOKEN="<paste from check stdout>" bash "$HOME/.cursor/skills/gate-news-communityscan/scripts/update-skill.sh" apply "gate-news-communityscan"

bash

bash "$HOME/.cursor/skills/gate-news-communityscan/scripts/update-skill.sh" revoke-pending "gate-news-communityscan"

powershell

$env:GATE_SKILL_CONFIRM_TOKEN = '<paste from check stdout>'
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-news-communityscan\scripts\update-skill.ps1" apply "gate-news-communityscan"

powershell

powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-news-communityscan\scripts\update-skill.ps1" revoke-pending "gate-news-communityscan"

If Step 1 was not strict (no pending token): apply
without GATE_SKILL_CONFIRM_TOKEN
is allowed.

If
skipped
or
check_failed
: no update step; proceed to Execution.

Optional —

GATE_SKILL_UPDATE_MODE=auto

For CI / unattended automation only: setting GATE_SKILL_UPDATE_MODE=auto
on check
makes the script apply immediately when the remote is newer — no user confirmation and incompatible with blocking update confirmation tests. Do not use auto
on check
when reproducing the blocking PD flow.

Parameters

name: Frontmatter
```
name
```
above; must match
```
skills/<name>/
```
on gate-skills.
Invoke: Use $SKILL_ROOT/scripts/update-skill.sh
(or
```
.ps1
```
) where $SKILL_ROOT/SKILL.md
is this skill — e.g. ~/.cursor/skills/<name>
, ~/.codex/skills/<name>
, ~/.openclaw/skills/<name>
, ~/.agents/skills/<name>
, ~/.gemini/antigravity/skills/<name>
; do not treat ~/.cursor
(or any host root without skills/<name>/SKILL.md
) as the install. With one arg, the script resolves $SKILL_ROOT
in that order before falling back to the script’s directory; workspace installs need explicit
DEST
. Two-arg
check
/
apply
/
revoke-pending
: canonical order is absolute
DEST
(skill root) first, then name
; update-skill.sh
/
update-skill.ps1
auto-swap when only one normalized path contains
```
SKILL.md
```
(e.g. agent passes
```
name
```
then path).
ClawHub vs full tree: Installs without
```
update-skill.ps1
```
may copy it from gate/gate-skills under
```
skills/<name>/scripts/
```
(manual only; agents must not auto-download).

Do not dump raw script logs into the user-facing reply except when debugging. On check
exit 3 (strict), do not run Execution until Step 2 is resolved. On check_failed
or apply
failure, still run Execution when appropriate per runtime rules.

Known Limitations

UGC platforms: Reddit, Discord, and Telegram depend on
```
search_ugc
```
availability. Until that API is online, label reports as X/Twitter-only.
Historical sentiment trend may degrade to a single-point snapshot depending on upstream API coverage.

MCP Dependencies

Legacy path only — this section applies when Step 0 emitted

__FALLBACK__

Required MCP Servers

MCP Server	Status
Gate-News	✅ Required

MCP Tools Used

Query Operations (Read-only)

news_feed_search_x (X/Twitter discussion — e.g., Grok-backed analysis per upstream)
news_feed_get_social_sentiment

Authentication

API Key Required: No
Credentials Source: None; this skill uses read-only Gate Info / Gate News MCP access only.

Installation Check

Required: Gate-News
Install: Use the local Gate MCP installation flow for the current host IDE before continuing.
Continue only after the required Gate MCP server is available in the current environment.

Routing Rules

Legacy path only — when Step 0 emitted

__ROUTE_CLI__

, routing is delegated to

gate-news-intel

User Intent	Keywords	Action
Community opinion on a coin	"what does community think about ETH"	Execute with `coin`
X/Twitter discussion	"Twitter discussion" "KOL views"	Execute (X-focused)
General social sentiment	"overall market sentiment"	Execute (no specific coin)
Reddit/Discord specific	"Reddit discussion"	Inform: X now; UGC coming
News only	"any crypto news"	Route to `gate-news-briefing`
Coin analysis	"analyze SOL"	Route to `gate-info-coinanalysis`
Why price moved	"why did BTC pump"	Route to `gate-news-eventexplain`

Execution Workflow

Legacy path only — this section applies when Step 0 emitted

__FALLBACK__

Step 0: Multi-Dimension Intent Check

Community/social sentiment → this Skill.
Coin fundamentals + technicals + macro together →
```
gate-info-research
```
(if available).

Step 1: Intent Recognition & Parameter Extraction

```
coin
```
(optional)
```
topic
```
(optional): e.g., ETF, regulation, Layer 2
```
query
```
: constructed from coin + topic for X search; if neither, general market social scan

Step 2: Call MCP Tools in Parallel

Step	MCP Tool	Parameters	Retrieved Data	Parallel
1a	`news_feed_search_x`	`query={coin or topic}`	X discussion / narratives / KOL angles	Yes
1b	`news_feed_get_social_sentiment`	`coin={coin}` if specified	Sentiment score, ratios, mention volume	Yes

Step 3: LLM Aggregation

Synthesize qualitative X discussion with quantitative sentiment
Dominant narratives and KOL themes
Sentiment vs price alignment or divergence

Report Template

Legacy path only — this section applies when Step 0 emitted

__FALLBACK__

markdown

## Community Sentiment Scan: {coin or topic}

> Generated: {timestamp} | Platforms: X/Twitter only
> Note: Reddit/Discord/Telegram not yet supported.

### X/Twitter Discussion

{Summary from news_feed_search_x}

**Key Narratives**: ...
**Notable KOL Views**: ...

### Sentiment Metrics

| Metric | Value | Assessment |
|--------|-------|------------|
| Sentiment Score | {score} | {Bullish/Bearish/Neutral} |

### Sentiment vs Price

| Dimension | Current |
|-----------|---------|
| Social Sentiment | ... |
| Price Trend (24h) | ... |
| Alignment | {Aligned / Divergent} |

### Key Takeaways

{2–3 insights}

> Community sentiment is not a reliable price predictor. This does not constitute investment advice.

Decision Logic

Condition	Assessment
Sentiment score > 70	Strongly bullish — contrarian caution
Sentiment score < 30	Strongly bearish — possible capitulation or opportunity
Positive ratio > 80%	Strong positive consensus — watch for reversal
Discussion volume > 2x 7d average	Unusual activity — possible catalyst
KOL opinions divided	Broken consensus — uncertainty
Sentiment bullish but price falling	Divergence — sentiment may lag
Sentiment bearish but price rising	Divergence — market defying expectations

Error Handling

Error Type	Handling
`news_feed_search_x` fails	Sentiment metrics only; note X discussion unavailable
`news_feed_get_social_sentiment` fails	X discussion only; skip metrics
Both Tools fail	Return error; suggest retry
No X discussions for query	Broaden query; note limited data
User asks for Reddit/Discord	State UGC not available; X-only for now

Cross-Skill Routing

User Follow-up Intent	Route To
"Analyze this coin"	`gate-info-coinanalysis`
"Any news about this?"	`gate-news-briefing`
"Why is it pumping/dumping?"	`gate-news-eventexplain`
"Technical analysis?"	`gate-info-trendanalysis`
"On-chain data?"	`gate-info-tokenonchain`
"How's the overall market?"	`gate-info-marketoverview`

Safety Rules

No fabricated opinions: Only report what data supports; do not invent KOL quotes.
Source attribution: Attribute generically to KOL/community unless public figure is clearly named in data.
Neutral presentation: Show bullish and bearish views.
Sentiment ≠ prediction: State limitations clearly.
Platform transparency: Label X/Twitter-only coverage.
Misinformation: Prefer "unverified claims circulating" over stating rumors as fact.
Age & eligibility: Intended for users aged 18 or above with full civil capacity in their jurisdiction.
Data flow: The host agent processes user prompts; this skill directs read-only Gate-News MCP tools listed above. The LLM synthesizes from tool results. This skill does not invoke additional third-party data services.

gate-news-communityscan

NPX Install

Tags

SKILL.md Content

gate-news-communityscan

General Rules

Step 0 — Wrapper routing probe

Trigger update (with Execution)

Step 1 — Check

Step 2 — Confirm or Reject (blocking)

Optional —
`GATE_SKILL_UPDATE_MODE=auto`

Parameters

Known Limitations

MCP Dependencies

Required MCP Servers

MCP Tools Used

Authentication

Installation Check

Routing Rules

Execution Workflow

Step 0: Multi-Dimension Intent Check

Step 1: Intent Recognition & Parameter Extraction

Step 2: Call MCP Tools in Parallel

Step 3: LLM Aggregation

Report Template

Decision Logic

Error Handling

Cross-Skill Routing

Safety Rules