insights-repository-kit
Governance + tooling pattern for storing research artifacts, tagging, and discovery.
Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security
Installation for Agentic Skill
View all platforms →skilz install gtmagents/gtm-agents/insights-repository-kitskilz install gtmagents/gtm-agents/insights-repository-kit --agent opencodeskilz install gtmagents/gtm-agents/insights-repository-kit --agent codexskilz install gtmagents/gtm-agents/insights-repository-kit --agent geminiFirst time? Install Skilz: pip install skilz
Works with 22+ AI coding assistants
Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...
Extract and copy to ~/.claude/skills/ then restart Claude Desktop
git clone https://github.com/gtmagents/gtm-agentscp -r gtm-agents/plugins/market-research/skills/insights-repository-kit ~/.claude/skills/Need detailed installation help? Check our platform-specific guides:
Related Agentic Skills
tailwind-shadcn-setup
by vanman2024
Setup Tailwind CSS and shadcn/ui component library for Next.js projects. Use when configuring Tailwind CSS, installing shadcn/ui, setting up design...
spanish-language-tutor
by sandraschi
Comprehensive Spanish language expert covering grammar, conversation, regional dialects, and language learning strategies
frontend-dev-guidelines
by diet103
Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organiz...
torch-geometric
by davila7
Graph Neural Networks (PyG). Node/graph classification, link prediction, GCN, GAT, GraphSAGE, heterogeneous graphs, molecular property prediction, ...
Agentic Skill Details
- Repository
- gtm-agents
- Stars
- 31
- Forks
- 7
- Type
- Non-Technical
- Meta-Domain
- development
- Primary Domain
- javascript
- Market Score
- 28
Agent Skill Grade
F Score: 58/100 Click to see breakdown
Score Breakdown
Areas to Improve
- Description needs trigger phrases
- Missing Reference Files for Templates
- No Step-by-Step Workflow
Recommendations
- Focus on improving Ease Of Use (currently 13/25)
- Focus on improving Utility (currently 8/20)
- Address 2 high-severity issues first
Graded: 2026-01-24
Developer Feedback
I've been digging through repository analysis tools, and the insights-repository-kit's approach to metadata extraction caught my eye—though I'm curious why the Progressive Disclosure architecture feels a bit top-heavy for what it's trying to accomplish (58/100 suggests there might be some structural trade-offs worth examining).
Links:
The TL;DR
You're at 58/100, which is F territory. This is based on Anthropic's Progressive Disclosure Architecture best practices for agentic skills. Your strongest area is Spec Compliance (11/15)—the YAML frontmatter is clean and properly formatted. The weakest link is Utility (8/20)—the framework outlines concepts without giving developers actual implementation guidance or examples they can use.
What's Working Well
- Clean frontmatter structure – Your YAML is valid with required fields properly configured
- Consistent terminology – "repository," "metadata," "research artifacts" are used consistently throughout
- Real problem identification – You're addressing an actual pain point (organizing research without getting lost)
- grep-friendly structure – Simple, scannable file format that's easy to parse
The Big One: Missing Reference Files & Templates
Here's what's holding you back: you mention templates (repository IA diagram, metadata dictionary, intake forms) but don't actually provide them. This breaks the Progressive Disclosure principle—instead of layering from simple to complex, you're leaving readers hanging.
The fix: Create a references/ directory with actual implementation files:
references/templates/repository-ia-template.md– Actual folder structure diagramreferences/templates/metadata-schema.json–...
Browse Category
More development Agentic SkillsReport Security Issue
Found a security vulnerability in this agent skill?
Report Security Issue
Thank you for helping keep SkillzWave secure. We'll review your report and take appropriate action.
Note: For critical security issues that require immediate attention, please also email security@skillzwave.ai directly.