Run any Skill in Manus with one click

status

Stars2

Forks0

UpdatedJuly 8, 2026 at 08:32

Use when checking RagKit index health — doc and chunk counts, backend resolution, staleness and drift between knowledge-base/ and index. Trigger /ragkit:status. Rebuilding after drift uses ragkit:embed.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

qxbyte

qxbyte/pluginhub

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	status
description	Use when checking RagKit index health — doc and chunk counts, backend resolution, staleness and drift between knowledge-base/ and index. Trigger /ragkit:status. Rebuilding after drift uses ragkit:embed.

RagKit Status

脚本在本插件的 scripts/ 目录（本 skill 目录的上两级）；用本 skill 的 base directory 把下面的相对路径拼成绝对路径执行。

sh ../../scripts/run.sh ../../scripts/ragkit.py \
   status --kb <项目根>/knowledge-base --json

解读：drift.missing_from_index 非空或 index_stale: true → 建议重跑 embed；backend_resolved: none → 原样转述固定提示块。

More from this repository

same repository

execute

qxbyte/pluginhub

Use when running a spec's execution tail — presents the 执行方式 selector, dispatches the chosen engine (task-swarm / superpowers / specode-native TDD), then runs acceptance and the distill prompt. Trigger /specode:execute <slug> manually at any time once tasks.md exists, or invoked by name (specode:execute) via the Skill tool by the spec / continue skills.

2026-07-092

intake

qxbyte/pluginhub

Use when running specode's requirements phase — project analysis + code location + clarification, then writing requirements.md. Produces <specsRoot>/<slug>/requirements.md (with the project_root frontmatter contract) plus the location pointers handed to the design phase. Invoked by name (specode:intake) via the Skill tool by the specode orchestration SKILL; not a user-triggered command.

2026-07-092

spec

qxbyte/pluginhub

Use when creating a new spec-driven workflow — the /specode:spec entry that walks requirements → design → tasks → 执行方式 → execute → acceptance, autonomously calling superpowers skills for the heavy lifting with a first-class specode-native fallback, and filing 4 fixed artifacts (requirements.md / design.md / tasks.md / implementation-log.md) under the user document directory. Trigger /specode:spec <request>, or 进入 spec 模式 with a new requirement.

2026-07-092

continue

qxbyte/pluginhub

Use when resuming an existing spec by slug — the /specode:continue entry that reads the fixed docs, reports a progress brief (inferred phase + checkbox progress), then stops and waits for the user; it never auto-resumes. Trigger /specode:continue <slug>.

2026-07-092

distill

qxbyte/pluginhub

Use when distilling a finished specode spec into atomic, locate-oriented markdown knowledge points — writes cases/ + navigation/ + MEMORY.md into the project's own <project_root>/knowledge-base/ (md-only, no auto-injection), optionally copied to an Obsidian vault. Trigger ONLY /specode:distill <slug>, never auto-run by the main specode flow.

2026-07-092

list

qxbyte/pluginhub

Use when listing all specs under the specs root — the /specode:list entry that shows every spec slug with its inferred phase, for looking up slugs or an overview; it does not resume. Trigger /specode:list.

2026-07-092

Run any Skill with one click