Summarize files
🐒 Local, private LLM studio for Ollama — projects, Claude-style skills, and live file knowledge. Nothing leaves your machine.
npx -y skills add codalanguez/Monkii --skill summarize-filesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Summarize attached project files into a concise brief. Use when the user asks for an overview, summary, or "what is this project/document about".
SKILL.md
0.9 KB, 162 tokens by cl100k_base, as published. Nobody here has run it
Summarize Files
When this skill is invoked, produce a structured summary of the attached project knowledge:
- One-line gist — what this project/document is, in a single sentence.
- Key points — 3 to 7 bullets covering the most important content.
- Structure — if multiple files are attached, list each file path with a one-line description.
- Open questions — anything ambiguous, missing, or worth clarifying.
Rules:
- Ground every claim in the attached files; cite file paths inline like
(src/app.js). - If no files are attached, say so and ask the user to attach some via the project's Knowledge panel.
- Keep the whole summary under 300 words unless the user asks for more depth.
Gives 0 of the 12 instructions most note taking skills give in 162 tokens
Counted across 686 of the 876 authors here whose files we hold, read 2026-08-06
- include a visual element on every slidein 44 of 686, across 13 files
- use wikilinks for internal vault linksin 35 of 686, across 11 files
- commit to a single visual motif across every slidein 34 of 686, across 9 files
- read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
- keep 0.5 inch minimum marginsin 30 of 686, across 7 files
- use subagents to visually inspect rendered slidesin 30 of 686, across 6 files
- re-verify affected slides after every fixin 27 of 686, across 5 files
- run content QA checks before declaring successin 26 of 686, across 3 files
- Use Markdown links for external URLs onlyin 26 of 686, across 10 files
- pick a bold topic specific color palettein 24 of 686, across 2 files
- read editing guide before editing existing presentationsin 23 of 686, across 1 file
- use one dominant color across all slidesin 23 of 686, across 1 file
Said here and by no other author read
- produce a structured summary of the attached files
- write a one-sentence gist of the project
- list three to seven key points
- list each file path with a one-line description
- note ambiguous, missing, or unclear content as open questions
- keep the summary under 300 words unless asked for more
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.