Vibewatch Sentiment

SKILL待分类
待分类 未标注权限 许可证不明确

Stacks ecosystem community sentiment from the Vibewatch Stacks Vibe Index — free public index plus x402 pay-per-query depth (per-project history, evidence receipts, deltas) settled in sBTC on Stacks.

一句话选型结论

按资料字段整理

Vibewatch Sentiment是待分类类的 Agent Skill,安装方式:GitHub 仓库,权限级别未标注,许可证不明确,没有现成安装命令,需按说明手动放置 SKILL.md。技能本质是给模型读的说明书,效果取决于模型与客户端;装完先用一个小任务验证,再放进正式流程。

分类待分类 安装方式GitHub 仓库 权限级别未标注权限 许可证许可证不明确
累计安装 未标注 本周 未标注
GitHub 星标 未标注 仓库 skills
下载量 未标注 技能市场下载数
权限级别 未标注权限 安装前请确认风险范围
许可证 许可证不明确 未说明

安装

GitHub 仓库
在支持 Skills 的客户端里执行,装完问一句「你有哪些技能」验证
  1. 1
    确认客户端支持

    确认你的客户端支持 Skills(Claude、Codex、Cursor 等),并升级到较新的版本。

  2. 2
    拿到技能文件

    按安装说明或仓库 README,把 SKILL.md 放到客户端的 skills 目录(一般一个技能一个文件夹)。

  3. 3
    刷新技能列表

    重新打开客户端,或刷新技能列表,让新放进来的技能被加载。

  4. 4
    验证是否生效

    问一句「你有哪些技能」,确认列表里出现它,再拿一个小任务试跑。

技能档案

待分类
字段来自技能仓库与公开索引,中文说明由本站标注
作者 / 维护方aibtcdev仓库 skills · 版本 未标注
宿主客户端未标注技能可被这些客户端加载
安装方式GitHub 仓库安装包 aibtcdev/skills
权限级别未标注权限安装前请确认风险范围
许可证未说明许可证不明确,商用前请自行确认条款
仓库可用性available技能仓库当前是否可访问
最近核验未标注上游最后核验时间 · 数据更新 2026-09-16
正文体量9.2 KBSKILL.md 原文大小,越大说明说明书写得越细

典型使用场景

3 类
按分类整理的常见用法,具体以 SKILL.md 为准
探索新能力

先试一类新技能能做什么。

当通用助手

让模型按说明书处理常见任务。

补齐模型缺的技能

给模型补上它原本没有的做法。

选择建议

装之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 基础信息齐全,可以先按说明装一个试试。

先想清楚的地方

  • 没有标注权限级别,实际能做什么要装好后确认。
  • 许可证不明确,商用或二次分发前先到仓库确认条款。
  • 没有现成安装命令,要按安装说明或仓库 README 手动放置。
  • 没有做站内核验,内容以作者仓库为准。
  • 技能只是说明书,实际效果取决于模型与客户端,装完先用小任务试一遍。

更适合

  • 需要在待分类场景里给模型补一套做法的人。
  • 愿意先读一遍 SKILL.md、确认它会让模型做什么的人。

不太适合

  • 对许可证要求很严、必须明确可商用的人。
  • 只想装完就自动变强、不打算看说明书的人。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
技能权限级别安装方式累计安装宿主客户端安装命令
Vibewatch Sentiment当前 未标注权限 GitHub 仓库 未标注 未标注 无
着色页 联网访问 GitHub 仓库 1.4 万 Codex、Claude、Cursor 有
获取焦点模式 未标注权限 GitHub 仓库 1.1 万 Codex、Claude、Cursor 有
Nano PDF 文档 只读 GitHub 仓库 6,823 Codex、Claude、Cursor 有
Civil Servant 未标注权限 GitHub 仓库 — 未标注 无
07 Project Handoff 未标注权限 GitHub 仓库 — 未标注 无

SKILL.md 全文

9.2 KB
模型实际读到的说明书原文,来自技能仓库

vibewatch-sentiment

Community sentiment for the Stacks ecosystem, from the Vibewatch Stacks Vibe
Index — a public sentiment index over an opted-in
panel of Stacks projects (Stacks, Zest Protocol, Bitflow, Stacking DAO, AIBTC,
Hermetica, and more), computed from each project's own community channels
(Discord, Telegram, X, forums, GitHub Discussions, governance votes) and
published with k-anonymity floors and marked suppression.

Two tiers:

  • Free (index, terms, reports) — everything the public page shows:
    ecosystem composite (0–10), per-project current scores, 90-day history with
    Fear & Greed overlay, weekly message/author counts, rolling themes,
    governance votes, and the weekly-report archive. No wallet, no key.
  • Paid (project, evidence, delta) — depth per query over x402,
    settled on Stacks: 100 sats sBTC or 300000 µSTX (0.3 STX) per query. The
    402 challenge lists both, sBTC first; this skill pays sBTC unless you pass
    --asset STX (see Payment). Answers "what changed, why, and
    where's the receipt": per-project daily series, the public posts backing
    each weekly theme, and changes-since deltas for polling loops.

Subcommands

index (free)

bun run vibewatch-sentiment/vibewatch-sentiment.ts index

The full live index payload (schema_version, as_of, index, panel,
source_mix_7d, distribution_7d, history, projects[], panel_joins,
panel_joins_truncated, governance, summary, suppressed[], plus the
skill's own network and endpoint). Each projects[] entry carries the
project's slug and name.

terms (free)

bun run vibewatch-sentiment/vibewatch-sentiment.ts terms

The x402 discovery document (/.well-known/x402.json): current price,
accepted assets, payTo, and every paid resource. When the paid tier is
disabled the document truthfully serves empty accepts — check this before
the first paid call.

reports (free)

bun run vibewatch-sentiment/vibewatch-sentiment.ts reports

The Stacks Vibe Weekly archive: one line per completed report with its
week_start (the --week value for evidence), title, week composite, and
week-over-week change.

project (paid)

bun run vibewatch-sentiment/vibewatch-sentiment.ts project --project "Zest Protocol" --days 30
bun run vibewatch-sentiment/vibewatch-sentiment.ts project --project "Zest Protocol" --days 30 --asset STX

One panel project's daily composite series (≤90 days) plus its current score
and week-over-week change. --project accepts the project's name or slug;
the skill resolves it against the free index before paying (live slugs carry
a suffix, e.g. zest-protocol-3672, so you never have to know it). An
unknown or ambiguous project fails before any payment and lists the panel.
latest is null when the project's newest score is older than the index's
7-day recency floor — an old number is never presented as current.
A panel project whose free-index score is null (no scored days yet) cannot
be charged: since 2026-09-16 the index answers such a slug with a free
422 {"detail":{"error":"project_not_scored","slug":"…","days":90}} before
issuing any 402 (Vibewatch-io/vibewatch-app#1745; before that it served a
paid 200 with series: []). The skill still refuses the call locally after
the free slug lookup, which is faster; --allow-unscored only skips that
local check and surfaces the index's own refusal — nothing is paid either way.

evidence (paid)

bun run vibewatch-sentiment/vibewatch-sentiment.ts evidence --week 2026-08-24
bun run vibewatch-sentiment/vibewatch-sentiment.ts evidence --week 2026-08-24 --asset STX

Receipts behind one weekly report's themes: links to the public posts backing
each theme, with attributed excerpts for X posts. --week is a week_start
from reports; the skill checks it against the archive before paying, so a
week with no completed report fails free. Themes whose evidence is all in-server return receipts: []
marked no_public_evidence — private community content is never exposed.

delta (paid)

bun run vibewatch-sentiment/vibewatch-sentiment.ts delta --since 2026-09-01T00:00:00Z
bun run vibewatch-sentiment/vibewatch-sentiment.ts delta --since 2026-09-01T00:00:00Z --asset STX

What changed since a timestamp (hour-bucketed): per-project score moves with
constant-panel baselines, ecosystem composite then/now, current themes, and
reports published since. Defaults to the last 24 hours; --since older than
90 days is clamped.

Paid response shape

Every paid subcommand returns the index's paid envelope (schema_version,
tier: "paid", as_of, resource, payment, data, suppressed[]) plus
the skill's own endpoint, network, and payment_receipt:

  • payment — the settlement the index verified for this response: txid,
    payer, amount, asset, network, and payment_identifier (the id the
    operators match against their ledger). payment.txid is the receipt to
    cite.
  • payment_receipt — the same settlement as the x402 payment-response
    header, decoded (success, payer, transaction, network).
    payment_receipt.transaction equals payment.txid.
  • data — the resource payload:
  • project: slug, name, latest { score, wow_change, as_of_date },
    series[] { date, composite } (scored days only, oldest first).
  • evidence: week_start, themes[] with receipts[]; a theme with only
    in-server evidence has receipts: [] and suppressed: true,
    reason: "no_public_evidence".
  • delta: since_effective (hour-bucketed), index { composite_then, composite_now, change }, projects[], reports_published[],
    themes_current[].
  • suppressed[] — slices withheld for privacy (slice, reason), e.g.
    index_delta / below_min_orgs. Report them as withheld, not zero.

Payment

Standard x402 flow via the shared payment engine: the first request answers
402 with payment terms, the wallet signs, the retry carries the payment, and
the response includes a payment_receipt with the on-chain txid. One run,
one payment.

Choosing the asset. The index's 402 challenge advertises two Stacks
options, in this order: 100 sats of sBTC (SM3VDXK3WZZSA84XXFKAFAF15NNZX32CTSG82JFQ4.sbtc-token)
and 300000 µSTX (0.3 STX) — check terms for the current list. The shared
engine's default rule is first Stacks option; this skill does not rely on
that order and always asks for sBTC unless told otherwise. --asset STX (on project, evidence, delta)
makes the engine select the STX option instead — a wallet holding STX but no
sBTC can pay the index without ever touching sBTC. --asset sBTC is the
default and can be passed explicitly. If the challenge does not offer the
asset you asked for, the run fails before anything is signed and names the
assets that were offered. The payment.asset and payment.amount fields in
the paid response confirm which option settled. Any other client should do
the same explicitly: select the accepts[] entry by asset, not by
position (Vibewatch-io/vibewatch-mcp#16).

Running the same command again is a new query and a new
payment — there is no free re-read window across runs. (The server does hold
a 10-minute idempotency window keyed on the signed payment itself, which the
engine uses internally if the retry that carries a payment has to be resent;
that never costs a second payment.)

Networks

--network mainnet (default) pays real sBTC on the live index; set NETWORK=mainnet too, since the wallet follows NETWORK (default testnet) and the payment engine refuses a network mismatch before signing. Payments are sponsored unless X402_PAYMENT_MODE=direct is set (see the x402 skill), in which case the wallet also pays the STX fee. The live index accepts sponsored transfers again as of 2026-09-16 (Vibewatch-io/vibewatch-mcp#15), so a wallet holding only sBTC can pay in the default mode; direct remains the fallback if a 402 challenge is followed by 422 sponsored_unsupported. --network testnet
targets the staging index, which advertises the canonical testnet sBTC
(SN3VMHXEN64ZZF71JQ5VESXDWTR301XTTXGF4J8F1.sbtc-token); the shared engine
currently pins a different testnet sBTC id (aibtcdev/skills#419), so paid
testnet calls fail at the asset check until that lands. Free subcommands work
on both.

Reference

  • Index: https://stacks.vibewatch.io
  • Methodology: https://stacks.vibewatch.io/methodology
  • Discovery: https://stacks.vibewatch.io/.well-known/x402.json
  • Weekly reports: https://stacks.vibewatch.io/reports
  • x402scan listing: https://scan.stacksx402.com/resources/6c71357a-b7f8-466e-a7e8-0e5babd8039d
  • Report a problem: https://github.com/Vibewatch-io/vibewatch-mcp/issues

常见问题

5 问
答案由本站依据条目字段整理
Vibewatch Sentiment怎么安装?

没有现成安装命令:按安装说明或仓库 README,把 SKILL.md 放进客户端的 skills 目录(一般一个技能一个文件夹)。

Vibewatch Sentiment支持哪些客户端?

资料没有标注宿主客户端,但只要客户端支持 Skills(Claude、Codex、Cursor 等),一般都能加载。

Vibewatch Sentiment权限高吗,安全吗?

权限级别为未标注权限。安装前先看它会读取或写入哪些内容。

Vibewatch Sentiment收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于技能本身和所用的模型或客户端,正式使用前按作者说明确认。

Vibewatch Sentiment用什么许可证?

许可证标注为 未说明(许可证不明确)。商用或二次分发前请到仓库确认条款原文。

热门专题

按场景挑技能
全部专题 →

技能内容以作者仓库为准;分类、权限级别与许可证状态的中文说明为中文整理,最近核验 未标注。