generate-catalog
Generate CATALOG.md from deployed tickets. Extracts files_created metadata and builds project asset catalog with usage instructions.
Install / Use
npx skills add astro44/Autonom8-Agents --skill generate-catalogInstalls into whichever agent you are using.
Gemini Rules
Gemini CLI config
Quality Score
Category
OperationsSupported Platforms
Tags
Our assessment of generate-catalog
generate-catalog scores 71/100 on our quality scale, 695th of 756 Operations skills we index.
Its Gemini Rules is 4.2 KB long, well organised into 21 sections with 10 code examples: a solid amount of guidance for an agent.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
- Our last check on 2026-10-18 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 78/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
generate-catalog compared with similar skills
All 4 of these similar skills score higher than generate-catalog; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| generate-catalog (this skill)by astro44 | 71 | 0 | 4mo ago | Gemini Rules |
| apify-reddit-scraperby sickn33 | 100 | 48.9k | 5d ago | SKILL.md |
| diffdockby K-Dense-AI | 100 | 46.4k | 45d ago | SKILL.md |
| pkpd-modelingby K-Dense-AI | 100 | 46.4k | 45d ago | SKILL.md |
| simpyby K-Dense-AI | 100 | 46.4k | 45d ago | SKILL.md |
Frequently asked questions
- How do I install generate-catalog?
- Run
npx skills add astro44/Autonom8-Agents. The install tabs above show the steps for each supported agent. - Which AI agents does generate-catalog work with?
- It is written for Gemini CLI, as a Gemini Rules file. Other agents that read the same format can often use it too.
- Is generate-catalog safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 78/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is generate-catalog still maintained?
- The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
Skill content
View source on GitHubname: generate-catalog description: Generate CATALOG.md from deployed tickets. Extracts files_created metadata and builds project asset catalog with usage instructions.
generate-catalog - Project Catalog Generator
Generates or updates CATALOG.md from deployed ticket metadata. Builds a comprehensive asset catalog showing all components, styles, and utilities with usage instructions.
Input Schema
{
"project_dir": "/path/to/project",
"tickets_dir": "/path/to/tickets/deployed",
"include_tests": false,
"include_deps": true
}
Instructions
1. Scan Deployed Tickets
cd $tickets_dir
for ticket in *.json; do
jq -r '.files_created[]' "$ticket"
done
2. Extract File Metadata
For each deployed ticket, extract:
{
"files_created": [
{
"path": "src/components/MetricCard.js",
"type": "component",
"intended_use": "Import { MetricCard } from './MetricCard.js'"
}
]
}
3. Categorize Assets
| Category | Patterns | Description |
|----------|----------|-------------|
| Components | src/components/**/*.js | Reusable UI components |
| Styles | src/styles/**/*.css | CSS stylesheets |
| Utils | src/utils/**/*.js, src/js/utils/** | Helper functions |
| Data | src/data/**/*.json | Static data files |
| Pages | src/pages/**/*.html | HTML pages |
| Tests | tests/**/*, *.spec.js | Test files (if included) |
4. Generate Markdown
# Project Asset Catalog
> Auto-generated by generate-catalog on {date}
## Summary
| Category | Count | Status |
|----------|-------|--------|
| Components | 5 | ✅ |
| Styles | 3 | ✅ |
## Components
| File | Intended Use | Created By |
|------|--------------|------------|
| `src/components/MetricCard.js` | Import { MetricCard } | TICKET-001 |
Output Format
{
"skill": "generate-catalog",
"status": "success|failure",
"catalog_path": "src/CATALOG.md",
"stats": {
"tickets_processed": 5,
"files_cataloged": 23,
"categories": {
"components": 8,
"styles": 5,
"utils": 4,
"data": 2,
"pages": 4
}
},
"errors": [],
"warnings": [],
"next_action": "proceed"
}
Catalog Structure
# Project Asset Catalog
> Auto-generated by generate-catalog on 2026-01-07
## Summary
| Category | Count | Status |
|----------|-------|--------|
| Components | 8 | ✅ |
| Styles | 5 | ✅ |
| Utils | 4 | ✅ |
| Data | 2 | ✅ |
| **Total** | **19** | |
## Components
| File | Intended Use | Created By |
|------|--------------|------------|
| `src/components/impact/MetricCard.js` | Import { MetricCard } from './MetricCard.js' | TICKET-OXY-003-A.3 |
## Styles
| File | Intended Use | Created By |
|------|--------------|------------|
| `src/styles/components/metric-card.css` | Link in HTML: <link rel="stylesheet" href="..."> | TICKET-OXY-003-A.3 |
## Changelog
- **2026-01-07**: Added MetricCard component via TICKET-OXY-003-A.3
Decision Logic
All tickets parsed successfully?
YES → status: "success"
NO → status: "failure", errors: [parse errors]
Catalog written successfully?
YES → next_action: "proceed"
NO → next_action: "fix"
Usage Examples
Generate from deployed tickets:
{
"project_dir": "/projects/oxygen_site",
"tickets_dir": "/projects/oxygen_site/tickets/sprint_current/deployed",
"include_tests": false,
"include_deps": true
}
Include test files:
{
"project_dir": "/projects/oxygen_site",
"tickets_dir": "/projects/oxygen_site/tickets/sprint_current/deployed",
"include_tests": true,
"include_deps": true
}
Custom tickets directory:
{
"project_dir": "/projects/oxygen_site",
"tickets_dir": "/projects/oxygen_site/tickets/archive/sprint-42",
"include_tests": false,
"include_deps": false
}
Merge Behavior
When updating existing CATALOG.md:
- Read existing catalog
- Add new files from recently deployed tickets
- Preserve existing entries (don't remove)
- Update changelog section
- Sort entries alphabetically within categories
Token Efficiency
- JSON parsing only, no LLM inference
- Incremental updates (append-only)
- ~2-5 second execution
- Writes directly to file system
Related Skills
apify-reddit-scraper
48.9kScrape Reddit posts, comments, subreddits and users with the harshmaur/reddit-scraper Apify Actor. No Reddit API key. Keyword search, date windows, full threads.
diffdock
46.4kPredicts protein-small-molecule binding poses with DiffDock and DiffDock-L from PDB or sequence plus SMILES/SDF/MOL2. Covers batch docking, pose triage, confidence interpretation, and validation. Use for molecular docking and virtual-screening pose generation, not binding-affinity prediction.
pkpd-modeling
46.4kPharmacokinetic and pharmacodynamic modelling and simulation - non-compartmental analysis, compartmental and population PK, PK/PD and exposure-response, TMDD, PBPK orientation, bioequivalence, allometric scaling and first-in-human dose, drug interaction prediction, and Bayesian therapeutic drug moni…
simpy
46.4kBuilds, inspects, tests, and analyzes bounded process-based discrete-event simulations with SimPy. Use for event scheduling, resource queues, interrupts, monitoring, independent replications, warm-up, and reproducible output analysis.
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
