Answer debugging and navigation questions about a Clef codebase by querying Score (the code-as-data layer). Use for "where is X defined", "who uses Y", "impact of changing Z", "trace this stack", "what syncs fire on Concept/action", or any question that benefits from code-as-data introspection. Score-first; falls back to Read/Grep only when Score genuinely can't answer.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "debug-with-score" with this command: npx skills add Itshalffull/skillsmp-itshalffull-itshalffull-debug-with-score
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Compose a multi-step write to a Clef app as a single atomic Transaction using transactQL (the EdgeQL-style DSL) or transact(ops:) (the explicit Op[] form). Use whenever a fix touches >1 concept / >1 file / requires a precondition / would otherwise be a stack of separate Edit/Write calls. Atomic, idempotent on retry, dryRun-previewable, rolls back on failure.
Unified facade over the five Score suites ( parse , symbol , semantic , analysis , discovery ) providing a single LLM friendly surface for querying any Clef project s structure , symbols , semantics , data flows , and search indexes . Every Clef app gets ScoreApi registered automatically LLMs can immediately ask questions about the codebase without configuration . Actions are designed for natural language invocation : parameter names read as English , results are structured for tool use consumption , and error variants include actionable suggestions
Diagnoses plant nutrient deficiency or excess based on computer vision and plant physiology, outputs targeted fertilization suggestions for precision nutrien...
Explains the Web3 privacy landscape - what is public on-chain, what privacy tools exist, and how to think about personal privacy tradeoffs - without recommen...