claude-cortex and claude-scholar

One is a low-level API client for Claude (Cortex), while the other is a higher-level CLI configuration designed for academic and software development workflows that likely integrates with or utilizes such API clients (Scholar), making them ecosystem siblings or potentially complementary depending on the user's technical needs.

claude-cortex
58
Established
claude-scholar
56
Established
Maintenance 13/25
Adoption 12/25
Maturity 18/25
Community 15/25
Maintenance 25/25
Adoption 10/25
Maturity 3/25
Community 18/25
Stars: 12
Forks: 4
Downloads: 908
Commits (30d): 0
Language: Python
License: MIT
Stars: 1,341
Forks: 108
Downloads:
Commits (30d): 53
Language: Python
License:
No risk flags
No License No Package No Dependents

About claude-cortex

NickCrew/claude-cortex

Claude Cortex

Enforces cross-model code review workflows where implementing agents never review their own code—reviews route between Claude, Codex, and Gemini with structured fallback chains. Implements progressive quality gates (implementation → independent review → remediation loops) with circuit breakers and P0/P1 escalation rules, plus automated test auditing and lint enforcement. Integrates with Claude MCP servers and includes a TUI with background skill recommendation engine using keyword matching and optional semantic analysis.

About claude-scholar

Galaxy-Dawn/claude-scholar

Personal AI CLI configuration for academic research & software development. Supports Claude Code, OpenCode, and Codex CLI — covering the full research lifecycle from ideation to publication.

Provides filesystem-first project knowledge management via Obsidian with auto-synced experiment reports and results, plus Zotero MCP integration for remote bibliography access (DOI/arXiv import, collection management). Architecture uses skill-based command routing across 40+ Claude Code/Codex/OpenCode-compatible skills and agents, with Node.js hooks for cross-platform session management, security filtering, and 30-day log auto-cleanup—designed around human-centered semi-automation where the researcher retains decision authority over problem selection, hypothesis validation, and manuscript direction.

Scores updated daily from GitHub, PyPI, and npm data. How scores work