Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/jasonkneen/openclicky/llms.txt

Use this file to discover all available pages before exploring further.

Skills are the primary extension mechanism in OpenClicky. Each skill is a SKILL.md file — a plain markdown document with a YAML frontmatter header — that tells Clicky exactly how to approach a particular type of task, which tools to reach for, and what safety rules to follow. When you ask Clicky to manage your GitHub issues, automate a macOS app, or draft a research report, it loads the matching skill and follows its instructions rather than improvising from scratch.

​
What a Skill Is

A skill is a SKILL.md file combining structured metadata with detailed prose instructions. The frontmatter declares machine-readable facts about the skill — its name, version, trigger description, and tags — while the body is freeform markdown that Clicky reads and follows like a colleague reading a runbook. 
---
name: github-issues
description: "Create, triage, label, assign GitHub issues via gh or REST."
version: 1.1.0
author: OpenClicky
license: MIT
metadata:
  openclicky:
    tags: [GitHub, Issues, Project-Management, Bug-Tracking, Triage]
    related_skills: [github-auth, github-pr-workflow]
---

# GitHub Issues Management

Create, search, triage, and manage GitHub issues…
The description field is the most important part of the frontmatter — it’s the phrase Clicky matches against when deciding which skill to activate.

​
Frontmatter Fields

FieldRequiredPurpose
name✅Machine identifier for the skill; used in related_skills references
description✅Natural-language trigger description; Clicky matches this semantically
versionRecommendedSemantic version string for tracking changes
argument-hintOptionalPlaceholder shown to users in UI, e.g. "[workspace task or auth setup]"
authorOptionalFree-text author credit
licenseOptionalSPDX license identifier, e.g. MIT
metadata.openclicky.tagsOptionalArray of keyword tags for discovery and filtering
metadata.openclicky.related_skillsOptionalArray of skill name values that complement this skill
The description field is what Clicky uses to decide whether a skill applies to a user request. Write it as a precise trigger clause — not a generic summary — starting with “Use when…” or stating the action directly. Compare "Create, triage, label, assign GitHub issues via gh or REST." with the too-vague "GitHub stuff".

​
How Skills Are Loaded

OpenClicky ships two distinct locations for skills.

Bundled Skills

Shipped inside the app bundle at AppResources/OpenClicky/OpenClickyBundledSkills/. These are read-only, version-controlled skills maintained by the OpenClicky team and community. They cover coding agents, Google Workspace, GitHub, design, screen automation, and more.

Learned Skills

Created by Clicky at runtime and stored in OpenClickyLearnedSkills/ under the Codex home directory. These are auto-generated from your repeated workflows — see Learned Skills below.
Each bundled skill lives in its own subdirectory: 
OpenClickyBundledSkills/
├── claude-code/
│   └── SKILL.md
├── github-issues/
│   └── SKILL.md
├── notion/
│   └── SKILL.md
└── …

​
How Clicky Selects Skills

Clicky selects skills through two complementary mechanisms.

​
Semantic Matching

When you send a message, Clicky compares it against every skill’s description field. If your request semantically matches — even without using the skill’s exact name — the skill is activated. For example, asking “help me triage my open bugs” will match the github-issues skill whose description reads “Create, triage, label, assign GitHub issues via gh or REST.”

​
Skill Suggestion Rules

The skill-suggestion-rules.json file defines proactive, context-aware suggestions that appear as chips in the OpenClicky UI. Rules are organized by:
  • Default suggestions — always shown regardless of context (e.g. GitHub PR workflow, OpenClicky log-learning workflow)
  • App rules — shown only when a specific macOS app is in the foreground (e.g. Blender guidance when Blender is frontmost, Notion workflow help when Notion is active)
{
  "defaultSuggestions": [
    {
      "id": "github-pr-workflow",
      "title": "GitHub PR workflow",
      "detail": "Default connector-style workflow for repository, issue, PR, and branch checks.",
      "source": "mcp",
      "chipTitle": "GitHub check",
      "systemImage": "point.3.connected.trianglepath.dotted"
    }
  ],
  "appRules": [
    {
      "id": "active-blender-app-skill",
      "appMatches": ["blender", "org.blender.blender"],
      "suggestions": [
        {
          "id": "active-blender-guided-tour",
          "title": "Blender guided tour",
          "chipTitle": "Tour Blender"
        }
      ]
    }
  ]
}

​
The Two Skill Types

Bundled skills are read-only and updated with each release of OpenClicky. They cover the most common integrations and workflows out of the box — from delegating coding tasks to Claude Code or OpenAI Codex, to managing Google Workspace through the local gog CLI, to controlling macOS apps in the background via Computer Use.Bundled skills live at:
OpenClicky.app/Contents/Resources/AppResources/OpenClicky/OpenClickyBundledSkills/
You cannot edit bundled skills directly. To customise a bundled skill’s behaviour, the recommended pattern is to create an optimised copy in your learned skills directory — see the Creating Skills guide.
Learned skills are generated automatically by the learn-from-openclicky-logs and optimize-openclicky-skills bundled skills. When Clicky reviews your conversation logs and identifies a repeated workflow pattern, it can crystallise that pattern into a new SKILL.md saved to your learned skills directory.Learned skills live at:
~/Library/Application Support/OpenClicky/OpenClickyLearnedSkills/
Each learned skill follows the same SKILL.md format as bundled skills. You can view, edit, or delete them like any text file.

​
Enabling and Disabling Skills

Skills can be toggled individually in Settings → Agents. Disabling a skill prevents Clicky from selecting it for matching tasks — useful if a bundled skill conflicts with a custom workflow or integration you’ve set up differently.
1

Open Settings

Click the OpenClicky icon in the macOS menu bar and select Settings.
2

Navigate to Agents

Click the Agents tab in the Settings panel.
3

Toggle skills

Find the skill you want to enable or disable and use its toggle. Changes take effect immediately — no restart required.

​
Learned Skills

When you use OpenClicky repeatedly for the same type of task, Clicky can turn that pattern into a learned skill automatically. The learn-from-openclicky-logs skill reviews your conversation logs, identifies recurring workflows, and drafts new SKILL.md files. The optimize-openclicky-skills skill can then improve existing skills — both bundled and learned — based on evidence from how they’ve actually performed.
To trigger log learning manually, tell Clicky: “Review my logs and learn from them.” Clicky will read recent conversation history, identify repeatable patterns, and save any new skills to your OpenClickyLearnedSkills/ directory.
Learned skills live under the Codex home directory: 
~/Library/Application Support/OpenClicky/OpenClickyLearnedSkills/
├── my-deploy-workflow/
│   └── SKILL.md
└── weekly-gmail-triage/
    └── SKILL.md
You can inspect, edit, or delete any learned skill file directly. Clicky will pick up changes on the next request that matches the skill’s description.

Build docs developers (and LLMs) love

Get started for freeTalk to us