Run any Skill in Manus with one click

$pwd:

zeabur-rag-inspect

Name: Zeabur Rag Inspect
Author: zeabur

// View a single chunk's full content plus related reports, search signals, and edit history. Use when you need to understand a chunk's context before editing, when investigating why a search result appeared, or when reviewing a reported issue. Triggers on "inspect chunk SUP-1234", "show chunk DOC-xxx", "chunk history", "why did this result appear", "look at this chunk". Requires admin scope.

Run Skill in Manus

$ git log --oneline --stat

stars:3

forks:0

updated:April 13, 2026 at 08:47

SKILL.md

readonly

name	zeabur-rag-inspect
description	View a single chunk's full content plus related reports, search signals, and edit history. Use when you need to understand a chunk's context before editing, when investigating why a search result appeared, or when reviewing a reported issue. Triggers on "inspect chunk SUP-1234", "show chunk DOC-xxx", "chunk history", "why did this result appear", "look at this chunk". Requires admin scope.

RAG — Inspect

Get the full picture of a single knowledge base chunk: its content, related reports, search signals that surfaced it, and audit history.

Base URL: $ZEABUR_RAG_URL Auth: Authorization: Bearer $RAG_API_KEY — admin scope required

API

curl -s "$ZEABUR_RAG_URL/api/admin/chunks/<chunk_id>" \
  -H "Authorization: Bearer $RAG_API_KEY"

Input: Chunk ID (e.g. SUP-1234, DOC-deploy-variables-0, LEARNED-1712345678-abc123).

Response

{
  "chunk": {
    "id": "SUP-1234",
    "title": "...",
    "question": "...",
    "answer": "...",
    "text_content": "...",
    "tags": ["..."],
    "source": "forum",
    "verified": true,
    "status": "verified",
    "visibility": "public",
    "parent_id": null,
    "created_at": "...",
    "url": "..."
  },
  "reports": [
    { "id": "...", "type": "outdated", "query": "...", "detail": "...", "status": "open", "created_at": "..." }
  ],
  "signals": [
    { "id": "...", "query": "...", "mode": "hybrid", "top_similarity": 0.012, "feedback_score": null, "created_at": "..." }
  ],
  "audit_log": [
    { "id": "...", "chunk_id": "SUP-1234", "action": "edit", "old_value": {}, "new_value": {}, "created_at": "..." }
  ]
}

Key fields

text_content — the text used for embedding and BM25 index. You MUST read this before editing a chunk, because zeabur-rag-edit requires you to provide updated text_content whenever you change title/question/answer.
reports — any open or closed reports pointing to this chunk. If there's an open report, it may need action.
signals — recent queries that surfaced this chunk in search results. Shows how the chunk is being found and whether users found it helpful (via feedback_score).
audit_log — edit history. Check this to see who changed what and when.

Common workflows

Before editing: inspect → read text_content → construct updated text_content in the same format → call zeabur-rag-edit.
Investigating a report: inspect the reported chunk → check if the report is valid → decide to edit, reject, or close the report.
Understanding search behavior: inspect a chunk that keeps appearing in irrelevant queries → check signals to see which queries surface it → consider editing text_content to improve relevance.

Error

Returns 404 with {"error": "Chunk not found"} if the ID doesn't exist.

related-skills.json

same repository

zeabur-rag-learn.md

from "zeabur/rag-service"

Contribute new verified knowledge to the RAG knowledge base. Use after you've solved a concrete problem, debugged a non-obvious issue, or discovered undocumented behavior that would help future agents — but only after calling zeabur-rag-search first to confirm the knowledge isn't already covered. Only contribute verified facts, not guesses or workarounds. The new chunk is marked unverified until an admin reviews it.

2026-04-163

zeabur-rag-curate.md

from "zeabur/rag-service"

Interactive knowledge base curation loop — reviews pending items (reports, unverified chunks, failed queries, negative feedback) and walks through fixes one by one. Use when asked to "maintain the knowledge base", "review pending items", "run a curation round", "process reports", "clean up the KB", or any request to improve KB quality. This is the main entry point for the expand → organize → reflect cycle, and requires admin scope.

2026-04-133

zeabur-rag-feedback.md

from "zeabur/rag-service"

Send feedback on RAG search results — thumbs-up (+1) or thumbs-down (-1) to indicate whether the answer was helpful. Use after calling zeabur-rag-search when you can evaluate the quality of the results. Positive feedback reinforces good results; negative feedback flags poor matches for review. Requires write:feedback scope.

2026-04-133

zeabur-rag-search.md

from "zeabur/rag-service"

Search the RAG knowledge base via hybrid search (semantic + BM25). Use whenever answering technical questions that may be covered in your knowledge base — even if the user doesn't explicitly ask you to search. Also use when you need to verify claims or find up-to-date information.

2026-04-133

zeabur-rag-triage.md

from "zeabur/rag-service"

List pending knowledge base maintenance items — open reports, unverified learned chunks, low-score queries, and negative feedback. Use when checking KB health, reviewing the maintenance queue, or starting a curation session. Triggers on "review queue", "what needs attention in the KB", "pending reports", "unverified chunks", "failed queries", "KB health check". Requires admin scope.

2026-04-133

zeabur-rag-edit.md

from "zeabur/rag-service"

Edit the content of an existing chunk in the RAG knowledge base. Use when a chunk has a typo, outdated info, wrong tags, wrong visibility, or needs its title/question/answer rewritten — and you want the fix to take effect immediately. Requires admin scope. Prefer zeabur-rag-report for surfacing issues without write access.

2026-04-113

package.json

"author": "zeabur"

"repository": "zeabur/rag-service"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	zeabur-rag-inspect
description	View a single chunk's full content plus related reports, search signals, and edit history. Use when you need to understand a chunk's context before editing, when investigating why a search result appeared, or when reviewing a reported issue. Triggers on "inspect chunk SUP-1234", "show chunk DOC-xxx", "chunk history", "why did this result appear", "look at this chunk". Requires admin scope.

RAG — Inspect

Get the full picture of a single knowledge base chunk: its content, related reports, search signals that surfaced it, and audit history.

Base URL: $ZEABUR_RAG_URL Auth: Authorization: Bearer $RAG_API_KEY — admin scope required

API

curl -s "$ZEABUR_RAG_URL/api/admin/chunks/<chunk_id>" \
  -H "Authorization: Bearer $RAG_API_KEY"

Input: Chunk ID (e.g. SUP-1234, DOC-deploy-variables-0, LEARNED-1712345678-abc123).

Response

{
  "chunk": {
    "id": "SUP-1234",
    "title": "...",
    "question": "...",
    "answer": "...",
    "text_content": "...",
    "tags": ["..."],
    "source": "forum",
    "verified": true,
    "status": "verified",
    "visibility": "public",
    "parent_id": null,
    "created_at": "...",
    "url": "..."
  },
  "reports": [
    { "id": "...", "type": "outdated", "query": "...", "detail": "...", "status": "open", "created_at": "..." }
  ],
  "signals": [
    { "id": "...", "query": "...", "mode": "hybrid", "top_similarity": 0.012, "feedback_score": null, "created_at": "..." }
  ],
  "audit_log": [
    { "id": "...", "chunk_id": "SUP-1234", "action": "edit", "old_value": {}, "new_value": {}, "created_at": "..." }
  ]
}

Key fields

text_content — the text used for embedding and BM25 index. You MUST read this before editing a chunk, because zeabur-rag-edit requires you to provide updated text_content whenever you change title/question/answer.
reports — any open or closed reports pointing to this chunk. If there's an open report, it may need action.
signals — recent queries that surfaced this chunk in search results. Shows how the chunk is being found and whether users found it helpful (via feedback_score).
audit_log — edit history. Check this to see who changed what and when.

Common workflows

Before editing: inspect → read text_content → construct updated text_content in the same format → call zeabur-rag-edit.
Investigating a report: inspect the reported chunk → check if the report is valid → decide to edit, reject, or close the report.
Understanding search behavior: inspect a chunk that keeps appearing in irrelevant queries → check signals to see which queries surface it → consider editing text_content to improve relevance.

Error

Returns 404 with {"error": "Chunk not found"} if the ID doesn't exist.

zeabur-rag-inspect

RAG — Inspect

API

Response

Key fields

Common workflows

Error

More from this repository

More from this repository

RAG — Inspect

API

Response

Key fields

Common workflows

Error