publisher profilecommunity

generaljerel

generaljerel publishes 3 tracked skills in DriftBot.

Catalog decision: Mixed but usable publisher: there is meaningful evidence here, but reputation still needs to be earned skill by skill.

indexed skills

average score

manual reviews

high-risk labels

catalog evidence snapshotno baseline-v3 receipts yetno functionality-v2 receipts yetno manual reviews yetno high-risk labels

Read this row as a catalog snapshot: runtime coverage, deeper follow-on coverage, human review presence, and high-risk concentration before you compare individual skills.

📊 Runtime quality summary

Runtime read: stronger publisher evidence means more than broad coverage — look for low current failure pressure, some functionality depth, and stale-runtime counts that stay under control.

eligible runtime skills: 3latest touch: n/ano current regressions

Baseline coverage

00% of eligible skills have baseline-v3 receipts

Baseline pass rate

0%0 passed · 0 currently failing

Functionality coverage

00% of baseline-cleared skills have functionality-v2

Fixture-backed rate

0%0 functionality-v2 rows have richer fixture/example proof

Stale baseline rows

0baseline receipts older than 7 days

Functionality failures

0current failed functionality-v2 rows in the latest publisher state

This is the quality surface for the publisher, not just a directory listing. It shows how much of the catalog has real receipts, how often those receipts are passing, whether richer fixture-backed proof exists, and whether the publisher currently carries regressions, reproduced failures, or stale runtime evidence.

Latest runtime touch: n/a. Publisher-level summaries do not replace skill-level review, but they do make reputation more earned: a publisher with broader coverage, stronger pass rates, and fixture-backed proof looks different from one living on thin smoke tests.

If you want the system-wide view, open the runtime dashboard. If you want the scoring logic, read the methodology.

Fresh runtime slice Stale runtime slice

No runtime receipts for this publisher yet.

Skills from this publisher

Showing 3 of 3 skills

Label mix on this page

Trusted: 3Use Caution: 0Insufficient Evidence: 0High Risk: 0

This distribution is a quick provenance cue, not a verdict. A publisher can have a mix of safer and riskier skills, so the useful move is to compare patterns here and then open the individual scorecards.

Publisher profiles are best for spotting catalog patterns: repeated shell access, common external services, whether manual review exists, and whether higher-risk labels are isolated or widespread.

On this page: 3 source-scanned, 0 catalog-only, and 0 manually reviewed entries in the current slice.

If you want the scoring logic, read the methodology. If you want the broader landscape, go back to the full index.

copilotkit-react

generaljerel · vsource-scanned

overall

CopilotKit React best practices for agentic applications. Use when writing, reviewing, or refactoring React code that uses CopilotKit hooks (useAgent, useFrontendTool, useRenderTool, useCopilotAction, useCopilotReadable), providers (CopilotKit), or chat UI components (CopilotChat, CopilotSidebar, CopilotPopup). Triggers on tasks involving agent integration, tool rendering, shared state, or generative UI in React.

Trustedconfidence: source evidencesource-scanned

+ 1 more

Take: Source-aware scan found higher-privilege capability areas (token, email), but that alone is not evidence of malicious behavior.

Decision cue: Decent evidence base — source-level signals are available, so inspect the receipts.

copilotkit-runtime-patterns

generaljerel · vsource-scanned

overall

Server-side runtime patterns for CopilotKit. Use when setting up CopilotKit runtime endpoints (Express, Hono, Next.js), configuring remote agent endpoints, adding middleware, or securing the runtime. Triggers on backend tasks involving @copilotkit/runtime, CopilotRuntime, agent registration, or API endpoint configuration.

Trustedconfidence: source evidencesource-scanned

+ 1 more

Take: Source-aware scan found higher-privilege capability areas (token), but that alone is not evidence of malicious behavior.

Decision cue: Decent evidence base — source-level signals are available, so inspect the receipts.

copilotkit-agent-patterns

generaljerel · vsource-scanned

overall

Patterns for building AI agents that integrate with CopilotKit. Use when designing agent architecture, implementing AG-UI event streaming, managing shared state between agent and UI, adding human-in-the-loop checkpoints, or emitting generative UI from agents. Triggers on agent implementation tasks involving CopilotKit runtime, BuiltInAgent, or AG-UI protocol.

Trustedconfidence: source evidencesource-scanned

+ 1 more

Take: Source-aware scan found higher-privilege capability areas (token, email), but that alone is not evidence of malicious behavior.

Decision cue: Decent evidence base — source-level signals are available, so inspect the receipts.

Page 1 / 1

Trust reading guide

Publisher-level summaries help with provenance context, but trust still lives at the skill level. Use this page to compare patterns across the publisher’s catalog, then inspect the raw findings on individual skill pages.

Back to the full index