Showing 31111–31140 of 77205 skills
Build the Convex project from source. Use when a contributor wants to compile, test, or package Convex.
Convex-Dev/convex
Index of the Convex Architecture Documents (CADs), the normative specifications for Convex. Use to find which CAD governs a subsystem before changing protocol, encoding, consensus or economic behaviour.
Convex-Dev/convex
CAD3 encoding format — cells, embedded vs branch references, value IDs, validity rules. Use when working on encoders, decoders, serialisation, hashing or anything that reads or writes cell encodings.
Convex-Dev/convex
Resolve or register Convex Name System (CNS) names. Use when the user wants to look up a CNS name, register a new name, or update a name's target.
Convex-Dev/convex
Use Convex DB — a lattice-backed SQL database. Use when helping users write queries, connect via JDBC or PostgreSQL clients, create tables, insert/query data, or use the direct lattice API.
Convex-Dev/convex
Convex Lisp language reference — CVM conventions, calling library code, actor definitions, juice and error codes. Use when writing or debugging CVM source for queries, transactions or actors.
Convex-Dev/convex
Deploy an actor (smart contract) to the Convex network. Use when the user wants to create a new on-chain actor with exported functions.
Convex-Dev/convex
Work with DLFS, the Data Lattice File System — run a local DLFS server, manage drives, and read, write and list files through its MCP tools or WebDAV. Use when interacting with DLFS or working on the convex-dlfs module.
Convex-Dev/convex
Orientation in the Convex ecosystem — what lives in which repository, where the specs and docs are, and which client libraries exist. Use when you need context that is not in this repository.
Convex-Dev/convex
Inspect and maintain an Etch store — Convex's content-addressed database. Use when examining peer storage, diagnosing corruption, garbage collecting, or reading data by hash.
Convex-Dev/convex
Triage the open Convex issues against a fixed rubric — close what is done or superseded, give each a type label, and collect everything that needs a maintainer decision into one review sheet. Use when asked to review or triage all open issues.
Convex-Dev/convex
Juice accounting — the cost of computation and bandwidth on the CVM. Use when reasoning about transaction execution cost, diagnosing a :JUICE failure, or pricing a new CVM operation.
Convex-Dev/convex
Run isolated local Convex networks and in-process lattice node networks for development. Use when testing against local peers, reproducing peer or P2P replication issues, exercising NodeServer or P2PNode sync, or when no remote network is configured.
Convex-Dev/convex
Memory accounting and allowances — the cost of on-chain storage, and how to minimise and reclaim it. Use when reasoning about state growth, diagnosing a :MEMORY failure, or designing actors that store data.
Convex-Dev/convex
Operate a Convex peer — create, start, list, back up, or instantiate a network genesis. Use when running a peer against a network or setting up a new network.
Convex-Dev/convex
Protocol versions, migrations and the v1 upgrade — which semantics to write against, and how to change CVM behaviour without forking the network. Use when changing core functions, juice costs, encodings or on-chain libraries.
Convex-Dev/convex
Execute a read-only CVM query on the Convex network. Use when reading on-chain state, checking balances, looking up accounts, or evaluating Convex Lisp expressions.
Convex-Dev/convex
Create and manage fungible tokens on Convex. Use when the user wants to create a new token, check token balances, or manage token supply.
Convex-Dev/convex
Execute a CVM transaction on the Convex network. Use when the user wants to modify on-chain state, call actor functions, or define values.
Convex-Dev/convex
Transfer CVM coins or fungible tokens between Convex accounts. Use when the user wants to send coins or tokens to another account.
Convex-Dev/convex
Trust monitors — Convex's composable on-chain authorisation model. Use when writing access control, restricting actor functions, defining who may mint or upgrade, or reviewing authorisation logic.
Convex-Dev/convex
Transfer CVM coins or fungible tokens between Convex accounts. Use when the user wants to send coins or tokens to another account.
Convex-Dev/convex
调查 VLink 的用法问题、设计取舍、改进想法、经验分享或投票主题,检索 现有 GitHub Discussions 和相关 Issue 去重,用自然、聚焦、证据诚实的 简体中文草拟或发布 Discussion,并可读取完整讨论上下文后草拟或发布 单条顶层评论或楼中楼回复.用户要求"发 discussion"、"开讨论"、 "回复 discussion"、"评论 discussion"或"回应这条讨论"时使用;不得 伪装人类身份、批量回复、制造虚假互动或灌水。
thun-res/vlink
按功能编排 VLink 入口级 mock 集成测试,覆盖普通 doctest 难以触及的 全部 CLI 命令、Proxy、Viewer/Player/Analyzer、WebViz 及 bag 数据集 场景。用户要求"跑 mock"、"补测试死角"、"测试所有命令行"、"用 bag 数据集测试 viewer/webviz/proxy"或做发布前入口冒烟测试时使用。
thun-res/vlink
整理 VLink 当前 dev 分支的全部改动,必要时按模块和功能调用 /commit 创建本地提交,安全推送 dev,并向 master 创建或更新 GitHub PR.所有 云端人工填写内容使用简体中文.用户要求"提交 PR"、"创建 PR"、 "dev 合并到 master"或"填写 PR 标题和内容"时使用.
thun-res/vlink
深度分析 VLink 的项目定位、技术成熟度、发展活跃度与行业前景,结合 报告当日的具身智能、自动驾驶、ROS 2、DDS/Zenoh/iceoryx 和边缘计算 背景,形成带来源的中文优势/劣势/机会/风险与路线建议。用户要求"前沿 检查报告"、"分析 VLink 前景"、"行业定位"、"活跃度分析"或"与 ROS2/ 自动驾驶/具身智能结合评估"时使用。
thun-res/vlink
按 Linux、macOS 或 Windows 的仓库测试链路配置并构建普通 vlink-test、C API 与 Python 绑定,运行完整 CTest、绑定测试或指定 suite/case 并汇总失败。用户要求"跑 test"、"执行单元测试"、 "测试 c_api/python_api"、"只测某个 suite/case"、"验证测试是否通过" 或排查非 ASan 的 ci-test 失败时使用。
thun-res/vlink
Backward-compat alias for @horizon (this skill was renamed from `pm` to `Horizon` on 2026-07-05). USE THIS only when invoked directly as `/pm` or via an existing `@pm` delegation reference — it redirects immediately to @horizon, the strategic owner of the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. Prefer `@horizon` / `vnx horizon` for anything new; this alias exists only for transition safety.
Vinix24/vnx-orchestration
Transparent, itemized impressions of AI-generated WRITING STYLE — the repo's ONLY non-integrity track. Two passes: a deterministic defensive-hedge density screen (tools/check_ai_style.py, AIS-DEFENSIVE-HEDGE) plus a fresh cross-model GROSS-cases-only semantic pass over the 13 AIS-* style tells (broken narrative arc, LLM phrase tics, jargon-stuffing, invented codenames, clause/formula walls, gratuitous pseudocode, bullet overuse, bold-module spam, restatement loops, focus drift, single-style figures, appendix dumping). Every finding is named, LOCATED, span-anchored to the evidence ledger (claims.json), carries not_integrity_finding:true + false_positive_risk:high + an fp_case, and gets ZERO verdict weight: the adjudicator forces it to info, excludes it from overall_verdict, and renders it in a SEPARATE report section. NOT an AI-text classifier — no scores, no "this is AI-written", no authorship probability; a paper can be CLEAN_GIVEN_EVIDENCE and still list many. Emits ai-style-impressions.findings.json; computes NO verdict; if a tell is actually substantive it routes to the integrity auditor. Triggers: "AI style", "vibe check", "writing fingerprint", "AI 文风", "vibe paper".
wanshuiyin/Anti-Autoresearch
Audit whether a paper's baseline comparisons are COMPLETE, FAIR, and SIGNIFICANT: a required recent SOTA baseline is missing while 'best/SOTA' is claimed (HP-MISSING-BASELINE); a baseline is undertuned / given less compute-tuning-data, run at a mismatched config, or the equal-budget ablation-as-baseline is absent (HP-WEAK-BASELINE); 'outperforms' is asserted over overlapping error bars or with no variance/seeds (HP-SIG-OVERLAP); and a cross-row 'improves over baseline by X%' is arithmetically wrong (HP-DELTA-ERROR, cross-row form only). A versioned per-domain baseline profile + a live leaderboard/recency search are assembled by the EXECUTOR as structured facts; a fresh cross-model reviewer (gpt-5.6-sol xhigh, read-only, fresh thread per dimension) PROPOSES findings, each span-anchored to a ledger claim_id; tools/adjudicate_findings.py DECIDES the verdict. Works at L0 (stated comparisons) and deepens at L2 (configs/result files). A completeness question it cannot settle internally becomes needs_external_check, never a guessed missing baseline. Emits baseline-comparison-audit.findings.json; computes NO verdict. Detect-only. Triggers: "baseline audit", "missing baselines", "is the comparison fair", "weak baseline", "baseline 误报", "SOTA earned?".
wanshuiyin/Anti-Autoresearch