Use when working in the verified PsychSift checkout, especially for local run, UI/browser QA, Supabase/OpenAI/RAG changes, clinical governance, dependency/upload shortcuts, or choosing verification.
66%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./plugins/clinical-kb/skills/clinical-kb-workflow/SKILL.mdUse this skill for the PsychSift Next.js clinical reference RAG app. Establish the actual
checkout root with git rev-parse --show-toplevel and verify repository identity and ownership.
Root AGENTS.md remains authoritative. If these notes drift, inspect the repo before acting.
Follow the current Cloud policy,
user-controlled reasoning guidance and
agent allocation policy; this plugin neither
selects a host profile nor changes the user's main-chat model or effort.
package-lock.json.src/app; shared RAG, OpenAI, Supabase, safety, and validation logic live under src/lib.PsychSift Production with project ref sjrfecxgysukkwxsowpy.qjgitjyhxrwxsrydablr as stale.run request, run npm run ensure and return the printed URL.npm run ensure before browser checks.localhost:3000, localhost:3001, or localhost:3002./api/local-project-id as used by npm run ensure.npm run ensure verifies local server ownership; it does not by itself prove the selected app
configuration is provider-free or authorise live requests. Apply current host and task boundaries.node_modules/next/dist/docs/.npm run verify:cheap once only when cross-module or unknown risk warrants a broad offline gate.npm run ensure first, prove the affected journey, and use npm run verify:ui only when shared UI risk or handoff policy warrants the broad Chromium gate.npm run verify:pr-local. Run npm run verify:release only when the user explicitly requests release confidence and approves its provider-backed checks.npm run check:production-readiness:ci when readiness/configuration structure is in scope. Before production release or activation, retain the strict approvals and release-mode npm run check:production-readiness; routine development does not establish release readiness.npm run check:supabase-project as an approval gate; do not run it without explicit user approval.main, master, develop, or release/*, create a codex/... feature branch before editing when safe..github/pull_request_template.md.BigSimmo/PsychSift
0d5a97a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.