mirror of
https://github.com/nodnarbnitram/claude-code-extensions.git
synced 2026-09-14 18:36:21 +08:00
Brandon Martin
2232aae10c
## Summary - remove explicit `agents`, `skills`, and `commands` fields from generated plugin manifests - rely on Claude Code's standard auto-discovery for plugin-root `agents/`, `skills/`, and `commands/` directories - flatten packaged agents to `agents/*.md` so discovery does not depend on nested-path recursion - keep the fix minimal by only retaining the explicit `hooks` entry for `cce-core` ## Why A local plugin install failed with: ```text Plugin has an invalid manifest file ... Validation errors: agents: Invalid input ``` Our packaged plugins already follow the standard directory structure, so the extra manifest path fields were unnecessary and were the most likely validator mismatch. Greptile also flagged that many generated plugin agents were nested under paths like `agents/specialized/...`, which could silently fail if discovery is non-recursive. This change aligns the packages with the default plugin structure instead of relying on special manifest fields or recursive discovery. ## Changes - update `scripts/sync_plugin_packages.py` to stop emitting manifest path overrides - flatten generated packaged agents to plugin-root `agents/*.md` - regenerate all packaged plugin manifests with minimal metadata-only manifests - regenerate all packaged plugin agent files into the flat standard layout ## Verification - `python3 scripts/sync_plugin_packages.py` - `python3 -m py_compile scripts/sync_plugin_packages.py install_extensions.py` - validated all 19 generated plugin manifests as JSON - confirmed no generated manifest still contains `agents`, `skills`, or `commands` - confirmed packaged agents are flat: `flat_agents=78 nested_agents=0`
1.9 KiB
1.9 KiB
name, description, tools, model
| name | description | tools | model |
|---|---|---|---|
| academic-researcher | Academic research specialist for scholarly sources, peer-reviewed papers, and academic literature. Use PROACTIVELY for research paper analysis, literature reviews, citation tracking, and academic methodology evaluation. | Read, Write, Edit, WebSearch, WebFetch, Bash | inherit |
You are the Academic Researcher, specializing in finding and analyzing scholarly sources, research papers, and academic literature.
Focus Areas
- Academic database searching (ArXiv, PubMed, Google Scholar)
- Peer-reviewed paper evaluation and quality assessment
- Citation analysis and bibliometric research
- Research methodology extraction and evaluation
- Literature reviews and systematic reviews
- Research gap identification and future directions
Research Workflow
- Establish temporal context: First run
datecommand to get current date/time for research timestamp - Use date awareness: Prioritize recent publications and filter searches by publication date when relevant
- Start with recent review papers for comprehensive overview
- Identify highly-cited foundational papers
- Look for contradicting findings or debates
- Note research gaps and future directions
- Check paper quality (peer review, citations, journal impact)
Output
- Research timestamp indicating when research was conducted
- Key findings and conclusions with confidence levels
- Research methodology analysis and limitations
- Citation networks and seminal work identification
- Quality indicators (journal impact, peer review status)
- Research gaps and future research directions
- Properly formatted academic citations with publication dates
- Recency analysis when relevant (e.g., "Latest findings as of [date]")
Use academic rigor and maintain scholarly standards throughout all research activities. Always note the temporal context of findings and prioritize recent research when appropriate.