From skillful-alhazen
Interacts with TypeDB databases to list entities, ingest and analyze domain data, recognize schema gaps, and file issues for schema evolution using Python scripts.
npx claudepluginhub sciknow-io/skillful-alhazen --plugin tech-reconThis skill uses the workspace's default tool permissions.
Use this skill to [describe primary use case]. Claude acts as [describe Claude's role in this domain].
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Share bugs, ideas, or general feedback.
Use this skill to [describe primary use case]. Claude acts as [describe Claude's role in this domain].
When to use: [Triggers: "ingest [item]", "analyze [item]", "show [entity]", ...]
make db-startuv sync --all-extras (from project root)make build-db after adding your schema.tqlTYPEDB_HOST: TypeDB server (default: localhost)TYPEDB_PORT: TypeDB port (default: 1729)TYPEDB_DATABASE: Database name (default: alhazen_notebook)uv run python .claude/skills/<your-domain>/<your-domain>.py list-entities
During sensemaking, if you encounter a concept, relationship, or entity type that has no place in the current TypeDB schema, that is a schema gap — a signal for schema evolution, not a failure.
When you notice a schema gap:
uv run python local_resources/skilllog/skill_logger.py file-schema-gap \
--skill <this-skill-name> \
--concept "<the concept you tried to represent>" \
--missing "<which TypeDB entity/relation/attribute is absent>" \
--suggested "<proposed TypeQL addition, or 'unknown' if unsure>"
Examples of schema gaps:
methodology attribute on scilit-paperUse --dry-run first to review the issue before filing it.
uv run emits a VIRTUAL_ENV warning to stderr. Always use 2>/dev/null when piping output to a JSON parser — never 2>&1, which merges the warning into stdout and breaks JSON parsing.
Before executing any commands, read USAGE.md in this directory for the complete command reference, workflows, and data model.