Hyprland Local logo

Hyprland Local

Community
Firstp1ck
hyprland-local

Use automatically for Hyprland troubleshooting, configuration, Wayland compositor issues, monitors, input, keybinds, rules, animations, decoration, portals, plugins, crashes, NVIDIA, or hyprctl/hyprpm questions. Prefer local official Hyprland Wiki evidence via hyprwiki tools before web sources.

Overview

PublisherFirstp1ck
Repositorypi-coding-agent-forge
Skill namehyprland-local
Stars
93
Forks
22
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Firstp1ck on GitHub. Read the source before you install it.

Installation

Install the Hyprland Local AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Firstp1ck/pi-coding-agent-forge/tree/main/pi-extension-hyprland-wiki-local/skills/hyprland-local
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forge.git /tmp/pi-coding-agent-forge
mkdir -p .claude/skills
cp -r /tmp/pi-coding-agent-forge/pi-extension-hyprland-wiki-local/skills/hyprland-local .claude/skills/hyprland-local
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Hyprland Local in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Hyprland Local on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Hyprland Local is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Hyprland Local Wiki

Use the local official Hyprland Wiki clone before web sources. Optimize for source-backed answers with bounded output and local path citations.

Corpus profile

  • Local checkout path: ~/.hyprwiki
  • Upstream repository: https://github.com/hyprwm/hyprland-wiki.git
  • Parser/format: Markdown with frontmatter-title handling and fenced-code-aware heading extraction
  • Indexed extensions: .md, .mdx
  • Setup command: /hyprwiki-local-setup
  • Smoke test: /hyprwiki-smoke-test or hyprwiki_smoke_test({ maxSearchResults: 5 })

Required workflow

  1. Run hyprwiki_search({ query, limit: 5, includeSnippets: false }) for the user's Hyprland topic.
  2. Use hyprwiki_sections({ page, maxSections: 40-80 }) when the right page is found but the relevant heading is unclear.
  3. Prefer exact hyprwiki_extract({ page, section, maxChars: 4000-8000, maxSections: 2-5 }) for final evidence.
  4. Use query extraction only for exploration, then switch to exact section headings when available.
  5. Use hyprwiki_read({ page, maxChars }) only for broad context or when no relevant heading is identifiable.
  6. Use hyprwiki_related({ page, limit: 5-10 }) when the issue spans connected Hyprland topics.
  7. Compare documentation guidance with local config/system evidence when relevant.
  8. Cite local paths and section names in final answers.
  9. Prefer read-only diagnostics and ask before destructive or user-facing changes.

Search hints

  • Monitors: monitor resolution scale, hyprctl monitors, workspace monitor.
  • Window rules: windowrule float opacity, window rules class title, workspace rules.
  • Input/keybinds: keyboard kb_layout keybinds, bind dispatcher, touchpad gestures.
  • Portals/screen sharing: xdg desktop portal screenshare, xdg-desktop-portal-hyprland.
  • NVIDIA: nvidia wayland env, nvidia multi gpu, GBM.
  • Plugins: hyprpm plugins, using plugins, plugin guidelines.

Source priority

  1. Local official Hyprland Wiki via hyprwiki_* tools.
  2. Local user config/system evidence (hyprctl, config files, logs) when relevant.
  3. Official online Hyprland Wiki/GitHub only when local docs are missing, stale, or insufficient.
  4. Other sources only when necessary and clearly labeled.

Tool usage

  • hyprwiki_search({ query, limit, includeSnippets }): find candidate pages. Keep limit at 5 unless exploring broadly; snippets default off.
  • hyprwiki_sections({ page, maxSections }): inspect headings before extracting from large pages.
  • hyprwiki_extract({ page, section, maxChars, maxSections }): retrieve focused exact sections; best for final answers.
  • hyprwiki_extract({ page, query, maxChars, maxSections }): retrieve query-relevant sections; best for exploration.
  • hyprwiki_read({ page, maxChars }): retrieve broad page text; use sparingly.
  • hyprwiki_related({ page, limit }): discover linked local pages.
  • hyprwiki_smoke_test({ maxSearchResults }): verify parser/search/extract/read behavior after package or corpus updates.

Read-only diagnostics examples

Use only when relevant:

bash
hyprctl version
hyprctl monitors
hyprctl clients
hyprctl activewindow
hyprctl getoption general:gaps_in
journalctl --user -b -u hyprland --no-pager

Ask before editing Hyprland config, restarting the compositor/session, disabling portals, changing GPU environment, or installing/removing plugins.

Token/output discipline

  • Prefer search -> sections -> exact section extract for final answers.
  • Keep search limits small (limit: 5-10) and snippets off unless needed.
  • Use maxSections around 2-5 and maxChars around 4000-8000 for focused extracts.
  • If omittedSectionCount or truncated: true affects confidence, say so explicitly.

Citation format

Use local source citations like:

txt
Sources:
- ~/.hyprwiki/content/Configuring/Basics/Monitors.md — General
- ~/.hyprwiki/content/Configuring/Basics/Window-Rules.md — Window Rules

Frequently asked questions

What does the Hyprland Local AI skill do?

Use automatically for Hyprland troubleshooting, configuration, Wayland compositor issues, monitors, input, keybinds, rules, animations, decoration, portals, plugins, crashes, NVIDIA, or hyprctl/hyprpm questions. Prefer local official Hyprland Wiki evidence via hyprwiki tools before web sources.

Why use Hyprland Local on TypingMind?

Because you install it once and use it with any model. Hyprland Local is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Hyprland Local in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Firstp1ck/pi-coding-agent-forge/tree/main/pi-extension-hyprland-wiki-local/skills/hyprland-local. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Hyprland Local?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Hyprland Local?

As many as you like. As long as a model supports skills, you can use Hyprland Local with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Hyprland Local AI skill free?

Yes. It is published on GitHub by Firstp1ck under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇