Paper Lens
YSQ-boop/paper-lens
Read and critically analyze one academic paper from an arXiv URL/ID or a local PDF, producing a source-grounded Markdown report that can grow from a quick read into a reviewer-level deep review.
Create personalized, source-grounded travel dossiers from a destination, dates, duration, travelers, and constraints.
Install Travel Guide
$ npx skills add magnus919/agent-skills --skill travel-guide -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/agent-skills travel-guide --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/travel-guide .claude/skills/travel-guide && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "travel-guide" agent skill from https://github.com/magnus919/agent-skills/tree/main/travel-guide into .claude/skills/travel-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "travel-guide", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/magnus919/agent-skills/tree/main/travel-guideType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add magnus919/agent-skills --skill travel-guide -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/agent-skills travel-guide --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/travel-guide .agents/skills/travel-guide && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "travel-guide" agent skill from https://github.com/magnus919/agent-skills/tree/main/travel-guide into .agents/skills/travel-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "travel-guide", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill travel-guide -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/agent-skills travel-guide --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/travel-guide .cursor/skills/travel-guide && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "travel-guide" agent skill from https://github.com/magnus919/agent-skills/tree/main/travel-guide into .cursor/skills/travel-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "travel-guide", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/magnus919/agent-skills.git --path travel-guide--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add magnus919/agent-skills --skill travel-guide -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/agent-skills travel-guide --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/travel-guide .gemini/skills/travel-guide && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "travel-guide" agent skill from https://github.com/magnus919/agent-skills/tree/main/travel-guide into .gemini/skills/travel-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "travel-guide", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install magnus919/agent-skills travel-guideInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add magnus919/agent-skills --skill travel-guide -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/travel-guide .github/skills/travel-guide && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "travel-guide" agent skill from https://github.com/magnus919/agent-skills/tree/main/travel-guide into .github/skills/travel-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "travel-guide", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill travel-guide -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install magnus919/agent-skills travel-guide --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/travel-guide .opencode/skills/travel-guide && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "travel-guide" agent skill from https://github.com/magnus919/agent-skills/tree/main/travel-guide into .opencode/skills/travel-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "travel-guide", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
travel-guide- GitHub stars
- 115
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,114 words
- Files
- 17 (incl. scripts, references, assets)
- Skills in repo
- 131
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create personalized, source-grounded travel dossiers from a destination, dates, duration, travelers, and constraints.
- Works in 6 steps: Establish the trip contract → Handle personal context explicitly → Research current facts → …
- Someone wants an individualized itinerary
- SKILL.md covers When to use, When not to use, Progressive routing and Workflow, plus 2 more sections
- Runs Python scripts from its folder; calls python3
What it does
Travel Guide is an agent skill from magnus919/agent-skills. Create personalized, source-grounded travel dossiers from a destination, dates, duration, travelers, and constraints. Ask only the questions that change the plan, use explicitly permitted personal context without exposing it, research current logistics, and produce a cited, visually coherent PDF or responsive companion web page. Use when someone wants an individualized itinerary, trip brief, travel field guide, or shareable travel website. Do not use for real-time booking, ticket purchasing, visa or legal advice…
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 22 other files, including scripts, reference files and assets (for example `README.md`, `evals/evals.json` and `references/editorial-structure.md`). Compatibility notes: Requires an Agent Skills-compatible host, access to current web sources for live travel facts, and a print-capable browser or document renderer for PDF…
It sits in Knowledge Management, covering Source-grounded notebooks and PDF. The repository describes itself as: Curated collection of AI agent skills for Hermes and other agent frameworks. The licence is MIT.
When your agent uses it
- Someone wants an individualized itinerary
- Travel field guide
- Shareable travel website
- Real-time booking
Example prompts
- “/travel-guide”
Requirements
- Python 3
- Compatibility (from SKILL.md): Requires an Agent Skills-compatible host, access to current web sources for live travel facts, and a print-capable browser or document renderer for PDF output. Bundled Python scripts require Python 3.8+ and only the standard library.
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 22b4723. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires an Agent Skills-compatible host, access to current web sources for live travel facts, and a print-capable browser or document renderer for PDF output. Bundled Python scripts require Python 3.8+ and only the standard library.
From compatibility in the SKILL.md frontmatter.
Context cost
Travel Guide loads about 2.4k tokens when it runs, and up to ~7.6k if it reads all its reference files. Until then it costs about 151 tokens; SKILL.md has 1,114 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from magnus919/agent-skills at commit 22b4723, republished under its MIT licence (© magnus919). 1,114 words, ~2,359 tokens.
Download SKILL.mdSave it as
.claude/skills/travel-guide/SKILL.md (or your agent's skills folder). This skill also uses 16 other files; get the full folder from GitHub.- name
- travel-guide
- description
- Create personalized, source-grounded travel dossiers from a destination, dates, duration, travelers, and constraints. Ask only the questions that change the plan, use explicitly permitted personal context without exposing it, research current logistics, and produce a cited, visually coherent PDF or responsive companion web page. Use when someone wants an individualized itinerary, trip brief, travel field guide, or shareable travel website. Do not use for real-time booking, ticket purchasing, visa or legal advice, or generic destination summaries without a specific traveler and trip.
- compatibility
- Requires an Agent Skills-compatible host, access to current web sources for live travel facts, and a print-capable browser or document renderer for PDF output. Bundled Python scripts require Python 3.8+ and only the standard library.
- license
- MIT
- metadata.category
- travel
- metadata.tags
- travel, itinerary, trip-planning, dossier, pdf, web, personalization
Travel Guide
Create a commissioned travel dossier, not a generic list of attractions. The finished guide should answer: why this place, for these travelers, at this moment? It should leave room for discovery while making the trip feel considered.
When to use
Use this skill when the traveler wants one or more of the following:
- an individualized itinerary or trip brief;
- a beautifully designed travel PDF or printable field guide;
- recommendations shaped by permitted preferences, constraints, or companions;
- a shareable, responsive web page for travel companions;
- a private and sanitized version of the same trip plan.
When not to use
- For booking, purchasing tickets, changing reservations, or handling payment.
- For visa, immigration, medical, safety, or legal decisions that require an authoritative professional or government source.
- For a generic destination summary when there is no concrete traveler or trip.
- For extracting text from an existing document. Route that to
anydoc; it reads documents but does not author or validate them.
Progressive routing
Read only the references needed for the request:
| Need | Read |
|---|---|
| Personal context, consent, pointed questions, or group trade-offs | references/intake-and-personalization.md |
| Current places, hours, prices, reservations, transit, or source quality | references/research-and-evidence.md |
| Trip thesis, anchor selection, day structure, or editorial voice | references/editorial-structure.md |
| Private/shareable editions or redaction | references/privacy-and-sharing.md |
| HTML, PDF, print CSS, rendering, or visual QA | references/pdf-rendering.md |
Use templates/trip-brief.json as the structured source of truth. Use templates/dossier-outline.md when drafting content before entering JSON.
Workflow
Match the process to the request. A narrow question - one neighborhood, one restaurant, one transfer, one practical fact - can be answered directly with sources in a short reply. Run the full dossier pipeline only when the traveler wants a guide, PDF, companion page, or a multi-day plan. The dossier format is a deliverable choice, not an automatic output for every travel question.
1. Establish the trip contract
Collect, or confirm:
- destination or route;
- arrival and departure dates, or at least the intended season;
- duration and approximate pace;
- who is traveling and any real differences in needs;
- budget range and currency, if relevant;
- mobility, dietary, sensory, language, or booking constraints;
- desired output: private PDF, shareable PDF, companion web page, or all three;
- intended audience: the traveler, the travel party, or wider sharing. The working model is private by default; ask who the output is for when it is not clear.
If a missing answer would change the recommendations, ask a pointed question. Do not run a long questionnaire. Read the intake reference for the question budget and personalization boundary.
2. Handle personal context explicitly
If the host can retrieve user preferences or history, use only context that is
relevant to this trip and permitted for this purpose. Internally classify each
personal signal as known, relevant memory, hypothesis, ask first, or
do not use. Never copy a raw private note into the guide. When personalization
would be surprising, explain the relevant basis briefly or ask permission.
3. Research current facts
Research only what the guide needs. Prefer official venue, operator, transit, government, tourism-board, and booking sources. Record URLs and retrieval dates in the source ledger. Separate:
- verified current facts;
- editorial interpretation about fit;
- estimates and assumptions;
- facts that remain unknown.
Do not present a search snippet, stale memory, or unsourced price as current truth. Read the research reference before making logistics or cost claims.
4. Build the editorial model
Write a one- or two-sentence trip thesis. Select a small set of anchors rather than ranking everything. Every anchor must state why it fits these travelers, when it works best, what it costs or requires, and what could make it fail.
Shape each day around:
- one anchor;
- one meal, drink, or local texture;
- one walk, neighborhood, or ordinary-life encounter;
- one pause or recovery space;
- one weather, energy, or closure alternative.
Include a short “skip this” section when famous options are poor fits. Read the editorial reference before drafting the dossier.
Show full SKILL.md (471 more words)Show less
5. Render the artifacts
Work in a dedicated working folder for this trip: create one explicitly (for
example $(mktemp -d) on macOS/Linux, or a named folder under the system
temp directory) and keep the trip model, rendered HTML, sanitized editions,
and PDFs there. Never write outputs into the skill directory or the user's
home directory root. The examples below use $WORK for that folder.
Keep content separate from layout. Validate the content model first:
python3 scripts/validate-trip-brief.py "$WORK/trip-brief.json" --strict --jsonRender a print-oriented HTML dossier:
python3 scripts/render-travel-guide.py "$WORK/trip-brief.json" \
--mode dossier --output "$WORK/travel-dossier.html" --jsonFor a responsive companion page, use the same model:
python3 scripts/render-travel-guide.py "$WORK/trip-brief.json" \
--mode companion --output "$WORK/index.html" --jsonThe renderer embeds the bundled CSS and local image assets when possible. Use a
print-capable browser or the repository's documents skill to turn the dossier
HTML into a PDF. The PDF is not complete until it has been structurally checked
and visually inspected. Read the PDF reference for the exact gate.
6. Produce a shareable edition when requested
Keep the private model as the source of truth. Create a sanitized copy rather than painting over a finished PDF:
python3 scripts/sanitize-trip-brief.py "$WORK/trip-brief.json" \
--profile shareable --output "$WORK/trip-brief-shareable.json" --jsonRender and validate the sanitized model separately. Do not assume that a shareable version may expose exact dates, lodging, companions, addresses, booking identifiers, contact details, or private notes.
Required dossier sections
Adapt the length to the trip, but preserve the information hierarchy:
- cover: destination, trip line, duration/route, and image credit;
- the brief: the reason this trip fits these travelers;
- anchors: high-confidence experiences with fit and logistics;
- day architecture: anchors, texture, pauses, and alternatives;
- make it special: specific gestures that are not generic search results;
- practical field notes: transit, reservations, etiquette, costs, and caveats;
- skip this: attractive but poor-fit options, where useful;
- sources and freshness: links, retrieval dates, and unresolved uncertainty.
The visual default is a dark photographic cover with a route journey line, warm gold eyebrow, white headline, restrained red accent, generous white content pages, ghost section numbers, a color-coded day strip right after the brief, pace and budget meters, compact cards, a unified warm photo grade on anchor images, readable tables, and a bottom-of-page footer per section: a content- derived field note (failure mode, plan B, recheck item, or skip reason) when one exists, a next-section line, and a ghost route mark. Preserve contrast and selectable text. Do not let decoration hide uncertainty or practical caveats. The footer is informational, never a schedule: it repeats model content in one line, it does not invent new plans.
Exit criteria
Stop when all requested artifacts exist and:
- the trip model passes the bundled validator;
- current claims have source URLs and retrieval dates or are labeled uncertain;
- the PDF has passed structural and visual QA, if requested;
- a companion page has been checked at narrow and wide widths, if requested;
- private and shareable outputs are clearly distinguished;
- the delivery names the source model, renderer, validation result, and known limitations.
© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 16 other files (scripts, references, assets) in travel-guide of magnus919/agent-skills.
- SKILL.md
- README.md
- assets/route-mark.svg
- evals/evals.json
- references/editorial-structure.md
- references/intake-and-personalization.md
- references/pdf-rendering.md
- references/privacy-and-sharing.md
- references/research-and-evidence.md
- scripts/render-travel-guide.py
- scripts/sanitize-trip-brief.py
- scripts/validate-trip-brief.py
- styles/travel-dossier.css
- templates/dossier-outline.md
- templates/trip-brief.json
- … and 2 more
Open the folder on GitHubat commit 22b4723
Compare with similar skills
Travel Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Travel Guide this skillmagnus919/agent-skills | 115 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Paper LensYSQ-boop/paper-lens | 101 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Researchiusztinpaul/ai-research-os-workshop | 179 | — | ~17k | Automated safety check: Pass | MIT | |
| Notebooklmrobonuggets/notebooklm-skill | 140 | — | ~2.5k | Automated safety check: Pass | None | |
| Notebooklm Slide StylesYamilAyma/notebooklm-prompt-styles | 106 | — | ~744 | Automated safety check: Pass | None | |
| Second Brain Import FilePieroSierra/SecondBrain | 153 | — | ~2.7k | Automated safety check: Pass | None |
Similar skills
Research
iusztinpaul/ai-research-os-workshop
Build, extend, AND query a persistent LLM-maintained wiki for any research topic.
Notebooklm
robonuggets/notebooklm-skill
Query, manage, and automate Google NotebookLM from your AI agent.
Notebooklm Slide Styles
YamilAyma/notebooklm-prompt-styles
Translates visual identity and design documents into standardized YAML for NotebookLM slide generation.
Second Brain Import File
PieroSierra/SecondBrain
Import a file of any supported type (PDF, image, .txt/.md) into the vault's raw/ directory, ready for ingestion.
Timestamped Video Summary
cnfjlhj/ai-collab-playbook
Generate a detailed, professional video content summary from timestamped subtitles/transcripts (e.g., lines starting with 00:00 / 1:23:45).
More from magnus919/agent-skills
All 131 skills in this repoArtifact Pyramids
magnus919/agent-skills
Organize durable agent research outputs as summaries, analysis, and evidence dossiers.
Ascii City Engine
magnus919/agent-skills
Build portable, first-person colored ASCII city engines and small GIS-derived city packs.
Color Management
magnus919/agent-skills
Manage color workflows with ICC profiles, working spaces, gamut mapping, and color science.
Data Scientist
magnus919/agent-skills
A skill your agent uses for PhD-level expertise in data science, statistics, and machine learning: rigorous statistical analysis, experimental design, causal inference, advanced modeling, research…
Docker Compose
magnus919/agent-skills
Use Docker Compose to define, run, debug, and harden multi-container applications.
Fpga Development
magnus919/agent-skills
Design, review, simulate, and verify FPGA logic using explicit RTL contracts, clock and reset models, CDC analysis, timing constraints, and reproducible implementation evidence.
Related
Categories
Questions about Travel Guide
What does Travel Guide do?
Create personalized, source-grounded travel dossiers from a destination, dates, duration, travelers, and constraints. Travel Guide is an agent skill from magnus919/agent-skills. Create personalized, source-grounded travel dossiers from a destination, dates, duration, travelers, and constraints.
When should I use Travel Guide?
Travel Guide fits situations like: someone wants an individualized itinerary; travel field guide; shareable travel website; real-time booking.
How do I install Travel Guide in Claude Code?
Run `npx skills add magnus919/agent-skills --skill travel-guide -a claude-code`. Or copy the skill folder (travel-guide in magnus919/agent-skills) into .claude/skills/travel-guide in your project. Claude Code loads it when a task matches its description.
How do I install Travel Guide in Codex?
Run `npx skills add magnus919/agent-skills --skill travel-guide -a codex`. Or copy the skill folder (travel-guide in magnus919/agent-skills) into .agents/skills/travel-guide in your project. Codex loads it when a task matches its description.
Can I use Travel Guide in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add magnus919/agent-skills --skill travel-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/travel-guide, .gemini/skills/travel-guide, .github/skills/travel-guide and .opencode/skills/travel-guide in your project.
What does Travel Guide need to run?
Going by SKILL.md and its folder, Travel Guide needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3. Compatibility (from SKILL.md): Requires an Agent Skills-compatible host, access to current web sources for live travel facts, and a print-capable browser or document renderer for PDF output. Bundled Python scripts require Python 3.8+ and only the standard library..
Does Travel Guide access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Travel Guide safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Travel Guide use?
Travel Guide is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Travel Guide use?
About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.2k tokens, read only when the agent opens those files.
What are the alternatives to Travel Guide?
Skills that share tags, products or a category with Travel Guide: Paper Lens (YSQ-boop/paper-lens, 101 stars), Research (iusztinpaul/ai-research-os-workshop, 179 stars), Notebooklm (robonuggets/notebooklm-skill, 140 stars) and Notebooklm Slide Styles (YamilAyma/notebooklm-prompt-styles, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Travel Guide?
magnus919 (a GitHub user) maintains it in magnus919/agent-skills, which has 115 GitHub stars. The repository holds 131 skills in this directory. The repository was last updated on October 10, 2026.
Source: magnus919/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.