markdown-ingestor
Automates the transfer and documentation of source files into a central wiki.
Install
mkdir -p .claude/skills/markdown-ingestor && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10801" && unzip -o skill.zip -d .claude/skills/markdown-ingestor && rm skill.zipInstalls to .claude/skills/markdown-ingestor
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
you are to ingest the raw source files from the raw directory within the GE Tools directory and write to the wiki folder, either appending to current pages or adding new ones as you see fitKey capabilities
- →Ingest documentation source files
- →Update master changelog
- →File new bugs
How it works
It moves files from a raw directory to the wiki folder, updating indexes and logs.
Inputs & outputs
When to use markdown-ingestor
- →Ingest documentation source files
- →Update master changelog
- →File new bugs in the wiki
About this skill
Location
All of these actions take place in the GE Tools directory, which is located at "C:\Users\19024\Documents\ObsidianVaults\Programming\GE Tools". Consider that the root directory for this skill
Workflow
- Read a file in the raw directory to get context, ignore files in the "ingested" directory
- Navigate to master_index.md within the "GE Tools/wiki" directory
- Use this as a starting point for navigation; find your way to the correct sub directory within the wiki directory, then navigate to the index.md file within it. Use that index.md file to find an appropriate file to append to, based on what you read in the raw folder, or if none are suitable, create a new file. link any new files you create inside the index.md file of that directory. After a file in the raw folder has been ingested, move it to the "ingested" folder that lives in the raw folder.
What your contributions should look like
- High level, conceptual overview of changes / design decisions / implementation stratey. This should go in the correct sub folder (front_end, back_end, ect.)
- Add an entry to the change log "GE Tools/wiki/change_log/Master Change Log.md" with a quick one to three line summary. Only add another dedicated page within that folder to talk about the change if it was significant.
- Possible bugs or issues that may have been introduced (This is important: make sure all bugs go within the "bugs" folder. Like the change_log folder, add an entry to the "Master Bug List.md" file, and only introduce a dedicated page if it is a major bug. The lising in the master list should link to the dedicated page as well as any other page that is relavent within the wiki folder.)
- If a bug or code base changes and conflicts with an older file in the wiki, update it (delete the fixed bug, update archetecture, ect)
- Suggestions for future changes
Always do the following
- ALWAYS prioritize a modular wiki. Many small notes is better than few larger ones. You should strive for many ATOMIC, SPECIFIC notes, that way they can be linked when needed to enforce context
- ALWAYS leave a human readable date time stamp attached to content you add, so if you edit multiple sections of a file you should add multiple date time stamps that correspond with your edits.
- Always link any new files you create inside the index.md file of that directory.
- Do not be overly verbose. It is important that this wiki is quickly ingestable for context when making changes. The exception is if a change is a major change, then make sure to go into lots of detail.
When not to use it
- →Direct code editing
Prerequisites
Limitations
- →Requires manual index maintenance
How it compares
It maintains a modular, atomic wiki structure rather than large monolithic files.
Compared to similar skills
markdown-ingestor side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| markdown-ingestor (this skill) | 0 | 3mo | No flags | Intermediate |
| ai-dock-history-exporter-executor | 0 | 3mo | No flags | Intermediate |
| codex-cli-bridge | 9 | 9mo | Review | Intermediate |
| skill-forge | 11 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
ai-dock-history-exporter-executor
Nepopams
Use for scoped AI Dock History Hub, exporter, source metadata, and safe history data workflow changes.
codex-cli-bridge
alirezarezvani
Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools
skill-forge
WilliamSaysX
Automated skill creation workshop with intelligent source detection, smart path management, and end-to-end workflow automation. This skill should be used when users want to create a new skill or convert external resources (GitHub repositories, online documentation, or local directories) into a skill. Automatically fetches, organizes, and packages skills with proactive cleanup management.
notion-knowledge-capture
makenotion
Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.
feishu-doc
openclaw
Feishu document read/write operations. Activate when user mentions Feishu docs, cloud docs, or docx links.
openspec-continue-change
studyzy
通过创建下一个产出物继续处理 OpenSpec 变更。当用户想要推进其变更、创建下一个产出物或继续其工作流程时使用。