GitStar uses this page as a validation layer: visible, active, adopted, and confidence signals are pulled into one first-fold read before you open the source repository.
First read
Gitlawb/openclaude-skills is better read as a directional signal than a clean recommendation. Keep the snapshot conservative and validate source activity, package reality, and close alternatives before committing to it.
16 public stars in the current GitStar snapshot.
Needs a narrower context read
Last commit May 27, 2026.
Stale activity
Treat stars as discovery context until a linked package appears.
No linked package mapping
One or more key signals are partial, so GitStar keeps the interpretation conservative.
Partial snapshot
Snapshot facts
Compare lens
Graphify-Labs/graphify and firecrawl/firecrawl are the closest comparison targets GitStar found. A side-by-side comparison usually tells you more than a single raw rank.
Signal trail
Read the recent motion first. This block is for deciding whether the repository still looks alive, compounding, or flattening before you trust stars alone.
Package reality
No linked npm or PyPI package is mapped for this repository yet, so the page leans more heavily on GitHub-visible popularity and should be read more conservatively.
GitStar expects a package signal here, but no npm or PyPI package is linked to this repository yet.
Validation note
GitStar can summarize public signals for Gitlawb/openclaude-skills, but the GitHub repository is still the primary place to confirm release cadence, issue activity, and maintainer intent.
GitStar surfaces public popularity and package signals. These rankings are not endorsements, security reviews, or investment advice.
Why this rank
This repo is here because it still carries strong GitHub attention.
Reconstructed from current stars and cached daily/weekly/monthly deltas.
GitStar can see repository momentum, but it does not have a reliable linked package signal yet.
Treat stars and recent movement as discovery context only until npm or PyPI usage is available.
Overlaps on topics such as ai-agents and developer-tools, which makes it a stronger alternative than a random popularity neighbor.
Overlaps on topics such as ai-agents and markdown, which makes it a stronger alternative than a random popularity neighbor.
Overlaps on topics such as ai-agents and developer-tools, which makes it a stronger alternative than a random popularity neighbor.
Overlaps on topics such as ai-agents and developer-tools, which makes it a stronger alternative than a random popularity neighbor.
GitStar picked graphify + firecrawl as the closest next comparison from the related repository set.
[](https://gitstar.space/repo/Gitlawb/openclaude-skills)<a href="https://gitstar.space/repo/Gitlawb/openclaude-skills"><img src="https://gitstar.space/api/badge/Gitlawb/openclaude-skills" alt="GitStar"></a>Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
The context API to search, scrape, and interact with the web at scale. 🔥
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
DeepSeek Harness: Everything is a Plugin.
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.
This page provides a quick overview of Gitlawb/openclaude-skills based on GitStar's cached data. The signal chart reconstructs approximate checkpoints from current stars plus cached daily, weekly, and monthly star deltas, so it is best read as directional context rather than as a precise historical audit log.
Want to show your project's ranking? Copy the badge embed code above and add it to your README.