SkillCurated by metahubEval warningsagents

kirby-debugging-and-tracing

Name: kirby-debugging-and-tracing
Author: bnomei

Diagnoses Kirby rendering/runtime issues using MCP runtime rendering, dump traces, and template/snippet/controller indexes. Use when outputs are wrong, errors occur, or tracing execution paths is required.

pinned to #3474420updated 2 months ago

7/11Verified publisherCurated by MetaHubActively maintainedLicensedDocumentedStructuredClean repo

Ask your AI client: “install skills/kirby-debugging-and-tracing”.

Requires the metahub MCP server installed in your client. Set up MCP.

mh install skills/kirby-debugging-and-tracing

metahub onboarded this repo on the author's behalf.

If you own github.com/bnomei/kirby-mcp on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.

Claim this repo

Stars

Last commit

2 months ago

3474420

Latest release

published

2 months ago

#agent-tools
#agentic-workflow
#claude-code
#cli
#codex-cli
#commands
#developer-tools
#google-gemini
#kirby
#kirby-cms
#knowledge-base
#mcp-server
#model-context-protocol
#php8
#prompts
#resources
#tools

Evaluation report

WarningsView full report

Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.3474420· 2 months ago

Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.

Kind-specific

3 passed1 warning

Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: SKILL.md present
found at skills/kirby-debugging-and-tracing/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
248 words · 2,078 chars · 8 sections · 1 code block
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)

Release history

releasecurrent3474420warn2 months ago

View on GitHub

Quick start

Follow the workflow below to reproduce and trace render issues.

KB entry points

kirby://kb/scenarios/68-snippet-controllers
kirby://kb/scenarios/03-shared-controllers
kirby://kb/scenarios/13-custom-routes
kirby://kb/scenarios/02-json-content-representation-ajax-load-more
kirby://kb/scenarios/14-escaping-and-safe-markdown

Required inputs

Page id/uuid or URL path.
Expected vs actual output and content type.
Auth/session requirements and steps to reproduce.

Repro checklist

Capture page id/uuid or URL, content type, and expected vs actual output.
Note auth/session state and request parameters.
Record cache state and the render traceId.

Stop condition

Stop once output matches expected behavior and temporary dumps are removed.

Dump placement example

mcp_dump([
  'page' => $page->id(),
  'template' => $page->intendedTemplate()->name(),
]);

Remove dumps after the issue is resolved.

Common pitfalls

Leaving mcp_dump() in production code.
Debugging cached output or the wrong content type.

Workflow

Ask for page id/uuid or URL path, expected vs actual output, content type, and any session/login requirements.
Call kirby:kirby_init, then ensure runtime availability with kirby:kirby_runtime_status and kirby:kirby_runtime_install if needed.
Reproduce with kirby:kirby_render_page(noCache=true, contentType=...) and capture traceId plus errors.
Locate relevant code paths:
- kirby:kirby_templates_index
- kirby:kirby_snippets_index
- kirby:kirby_controllers_index
- kirby:kirby_models_index
- kirby:kirby_routes_index when routing is involved
If the issue is unclear, add targeted mcp_dump() calls and read the trace with kirby:kirby_dump_log_tail(traceId=...).
Apply the smallest fix, re-render to confirm, and remove temporary dumps.
Search the KB with kirby:kirby_search (examples: "custom routes", "snippet controllers", "shared controllers", "content representations").