From grepai
Use when you need to create, modify, or inspect GrepAI workspaces and their project associations
npx claudepluginhub jugrajsingh/skillgarden --plugin grepaiThis skill is limited to using the following tools:
Handle all workspace operations based on the `operation` parameter passed from the invoking command.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Handle all workspace operations based on the operation parameter passed from the invoking command.
Workspaces enable cross-project semantic search with a shared vector store (PostgreSQL or Qdrant). Config lives in ~/.grepai/workspace.yaml.
Create a new workspace with backend and embedding selection. Parse workspace name from args (suggest parent directory name if missing). Ask for backend (Qdrant recommended, PostgreSQL), embedding provider (Ollama recommended, OpenAI), and model. Verify backend running via Docker/curl. Create workspace using piped printf input to grepai workspace create (interactive CLI). Add projects by absolute path. Print summary with commands.
See references/create-workflow.md for backend selection prompts, printf sequences for all 4 backend+provider combinations, project addition flow, and summary template.
Add a project to an existing workspace.
Extract workspace name and project path. If workspace name missing, list available and ask:
grepai workspace list
Which workspace?
If project path missing, default to current directory.
Use absolute path:
grepai workspace add {WORKSPACE} {ABSOLUTE_PATH}
Note: grepai derives the project name from filepath.Base(path) (the directory basename).
Added {BASENAME} to workspace {WORKSPACE} (path: {ABSOLUTE_PATH})
Remove a project from a workspace.
Extract workspace name and project name from arguments.
Important: grepai workspace remove takes the project name (directory basename), not the path. If the user provides a path, extract the basename.
Show current projects first so the user can identify the correct name:
grepai workspace show {WORKSPACE}
grepai workspace remove {WORKSPACE} {PROJECT_NAME}
Removed {PROJECT_NAME} from workspace {WORKSPACE}
Delete an entire workspace.
Extract workspace name.
Ask via AskUserQuestion:
Confirm deletion of workspace {NAME}? This removes config but not indexed data.
○ Yes, delete workspace
○ No, cancel
If cancel, stop.
grepai workspace delete {NAME}
Workspace {NAME} deleted
Run grepai workspace list. Display each workspace with backend type and project count. See references/output-templates.md for list format.
Extract workspace name. Run grepai workspace show {NAME} (optionally read ~/.grepai/workspace.yaml for detail). Display backend, embedder, projects, and management commands. See references/output-templates.md for show format.
Extract optional workspace name (grepai workspace status {NAME} or all). Check watcher (grepai watch --workspace {NAME} --status). Display backend status, per-project index health (OK/FAIL/STALE), and watcher state. See references/output-templates.md for status format.