Agent skill

Foliole Hosted Quality Repair

by campfirium in campfirium/foliole

Diagnose, locally repair, verify, and commit one failed independent Foliole dev T7 Hosted Quality run from a handoff locator; route any T7 Release failure back to the existing pinned release task…

Apache-2.0Auto-check passedKnowledge Management

Install Foliole Hosted Quality Repair

skills CLI
$ npx skills add campfirium/foliole --skill foliole-hosted-quality-repair -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install campfirium/foliole foliole-hosted-quality-repair --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/campfirium/foliole.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/foliole-hosted-quality-repair .claude/skills/foliole-hosted-quality-repair && rm -rf skills-src

Use ~/.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/

Facts

Skill name
foliole-hosted-quality-repair
GitHub stars
138
Token cost
~1.4k tokens
SKILL.md length
699 words
Files
2
Skills in repo
1
Repo updated
First seen
Licence
Apache-2.0

At a glance

Diagnose, locally repair, verify, and commit one failed independent Foliole dev T7 Hosted Quality run from a handoff locator; route any T7 Release failure back to the existing pinned release task…

  • Works in 6 steps: Read the complete run with gh run view… → If read-only GitHub access requires… → Confirm the returned branch is dev and… → …
  • A Codex Desktop task names a failed Foliole dev T7 Hosted Quality run
  • SKILL.md covers Route Before Diagnosing, Establish The Source Of Truth, Repair and Prevention Audit, plus 1 more section
  • Calls gh, git and npm

What it does

Foliole Hosted Quality Repair is an agent skill from campfirium/foliole. Diagnose, locally repair, verify, and commit one failed independent Foliole dev T7 Hosted Quality run from a handoff locator; route any T7 Release failure back to the existing pinned release task instead of creating a repair task. Use when a Codex Desktop task names a failed Foliole dev T7 Hosted Quality run, T7 Release run, or asks the visible controller to take over hosted-quality repair.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Knowledge Management. The repository describes itself as: An approachable incremental reading app. The licence is Apache-2.0.

When your agent uses it

  • A Codex Desktop task names a failed Foliole dev T7 Hosted Quality run
  • Asks the visible controller to take over hosted-quality repair

Example prompts

  • “/foliole-hosted-quality-repair”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Read the complete run with gh run view --repo --json jobs,conclusion,event,headBranch,headSha,displayTitle,url,workflowName and fetch…
  2. If read-only GitHub access requires approval, request only the exact read operation. Without it, set…
  3. Confirm the returned branch is dev and the workflow is the independent T7 Hosted Quality entry. Treat any mismatch as a routing failure.
  4. Use the returned commit identity only to correlate the observed run with repository history. Do not make it a human dispatch or…
  5. Inspect git status, the named commit, and relevant history. Preserve unrelated dirty changes; never switch, reset, or overwrite the…
  6. Inspect every failed job before editing. Set failedStage=T5 only for failure in the nested admission chain; otherwise set failedStage=T6…

What it can do on your machine

Read from SKILL.md and the folder at commit 29fbdbe. 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

    Shell commands in SKILL.md call:

    • gh
    • git
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, git and npm, which can reach the network depending on how they are called.

    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.

Context cost

Foliole Hosted Quality Repair loads about 1.4k tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 699 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~106
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from campfirium/foliole at commit 29fbdbe, republished under its Apache-2.0 licence (© campfirium). 699 words, ~1,408 tokens.

Download SKILL.mdSave it as .claude/skills/foliole-hosted-quality-repair/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
foliole-hosted-quality-repair
description
Diagnose, locally repair, verify, and commit one failed independent Foliole dev T7 Hosted Quality run from a handoff locator; route any T7 Release failure back to the existing pinned release task instead of creating a repair task. Use when a Codex Desktop task names a failed Foliole dev T7 Hosted Quality run, T7 Release run, or asks the visible controller to take over hosted-quality repair.

Foliole Hosted Quality Repair

Act as the single visible repair controller only for an independent dev T7 Hosted Quality run. A handoff is a locator, not failure or stage evidence.

Route Before Diagnosing

  • Read the stable workflow path, run ID, branch, URL, and workspace from the task.
  • If the run is .github/workflows/t7-release.yml, has branch release, or belongs to a T7 nested/platform stage, do not accept repair ownership, edit code, commit, dispatch, or create another task. Route the run URL and first failed stage to the existing pinned release task.
  • Only an independent .github/workflows/t7-hosted-quality.yml run on dev is in repair scope.
  • T5 and T6 are reusable stages inside both top-level T7 workflows, not independent repair streams. Report their failures as runTier=T7, failedStage=T5 or runTier=T7, failedStage=T6.
  • Legacy candidate, platform, or assembly workflow names do not establish a separate T7 repair owner.

If the pinned release task cannot be identified, report repairState=waiting-for-release-owner and stop. Never create a replacement release task from this skill.

Establish The Source Of Truth

  1. Read the complete run with gh run view <run-id> --repo <repository> --json jobs,conclusion,event,headBranch,headSha,displayTitle,url,workflowName and fetch failed-step logs with gh run view <run-id> --repo <repository> --log-failed.
  2. If read-only GitHub access requires approval, request only the exact read operation. Without it, set repairState=waiting-for-read-approval; do not diagnose from locator fields.
  3. Confirm the returned branch is dev and the workflow is the independent T7 Hosted Quality entry. Treat any mismatch as a routing failure.
  4. Use the returned commit identity only to correlate the observed run with repository history. Do not make it a human dispatch or branch-control input.
  5. Inspect git status, the named commit, and relevant history. Preserve unrelated dirty changes; never switch, reset, or overwrite the workspace to match the run.
  6. Inspect every failed job before editing. Set failedStage=T5 only for failure in the nested admission chain; otherwise set failedStage=T6. Do not guess when evidence is incomplete.
Show full SKILL.md (384 more words)Show less

Repair

  1. Group failures by shared root cause and overlapping write scope.
  2. Implement the smallest complete root-cause repair on dev. Do not weaken gates, widen allowlists, delete stable assertions, or replace native/user-path coverage with a narrower mock merely to get green.
  3. Run only checks registered as local-quick, starting with the narrowest reproducer. Local green never replaces hosted evidence.
  4. Review the integrated diff and preserve all unrelated changes.
  5. A monitor handoff that names the independent run and states it is a locator authorizes the bounded sequence of scoped local commits needed to resolve the failures owned by this controller, including failures exposed by its registered orchestrator revalidation. Use commit-note for every commit. Split commits by independently verifiable repair boundaries when useful; do not impose an artificial commit-count limit or bundle unrelated changes. Otherwise obtain explicit commit authorization.
  6. This handoff authorizes those local repair commits, not a push. Before each revalidation, prove that the latest repair commit is reachable from remote dev. If it is not, set repairState=waiting-for-dev-delivery and stop unless the user separately authorizes the push.
  7. Once the repair is reachable from remote dev, request hosted revalidation only with npm run quality:remote -- --scope <desktop|shared|android|ios|full> while on dev, then use quiet-wait for the terminal result. Never pass a SHA; the workflow event derives the internal target commit.
  8. Never enter release, mutate a Draft, reuse T7 evidence, or transfer the repair to the pinned release task.

Stop for product judgment, external service failure, missing permission, write-scope expansion, or ownership conflict. An intermediate red local check is not itself a stop condition.

Prevention Audit

After the repair commits, identify the narrow reproducer and whether the changed-file, fast, pre-push, or host routing should have selected it. Classify the root cause as exactly one of:

  • local-validation-missed
  • local-gate-coverage-gap
  • hosted-only-by-design
  • pre-existing-or-external

Report the classification and evidence. Do not automatically create sibling tasks; monitor ownership stays singular.

Report

Report runTier, failedStage, repairState, and preventionState separately. Valid repair states are waiting-for-read-approval, waiting-for-release-owner, investigating, repairing, committing, waiting-for-dev-delivery, waiting-for-orchestrator, and complete.

Set repairState=complete only after every observed in-scope dev T7 Hosted Quality failure is locally resolved, risk-matched local-quick validation is green, all scoped repairs are committed, and the registered dev orchestrator has reached its required terminal state. Never describe task creation, Desktop navigation, or prompt delivery as hosted-quality progress.

© campfirium, Apache-2.0. 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 1 other file in .agents/skills/foliole-hosted-quality-repair of campfirium/foliole.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 29fbdbe

Compare with similar skills

Foliole Hosted Quality Repair 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.

Foliole Hosted Quality Repair compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Foliole Hosted Quality Repair this skillcampfirium/foliole138—~1.4kAutomated safety check: PassApache-2.0
NotebookLM Research Workflowclaude-world/notebooklm-skill467—~1.8kAutomated safety check: PassMIT
Field LabKyleAMathews/field-lab576—~15kAutomated safety check: PassNone
Obsidian StudyVault Builderbevibing/tutor-skills1.3k—~1.9kAutomated safety check: NotesMIT
YouTube Talk Notetakerdair-ai/dair-academy-plugins614—~2.3kAutomated safety check: PassMIT
SurveySNL-UCSB/literature-survey-skill106—~5kAutomated safety check: PassMIT

Similar skills

  • NotebookLM Research Workflow

    claude-world/notebooklm-skill

    Creates NotebookLM notebooks from URLs, text and files, asks cited questions, runs web research and generates audio, slides, quizzes and other artifacts.

    467 GitHub stars~1.8k tokensUpdated 2 mo ago
    Knowledge ManagementAuto-check passed
  • Field Lab

    KyleAMathews/field-lab

    An always-available field lab for thinking with AI, guided by Kit.

    576 GitHub stars~15k tokensUpdated 16 days ago
    Knowledge ManagementAuto-check passed
  • Obsidian StudyVault Builder

    bevibing/tutor-skills

    Converts PDFs, text, web pages or a codebase into an Obsidian vault of study notes, practice questions, or a developer onboarding guide.

    1.3k GitHub stars~1.9k tokensUpdated 7 mo ago
    Knowledge ManagementAuto-check: notes
  • YouTube Talk Notetaker

    dair-ai/dair-academy-plugins

    Converts a YouTube talk into a markdown study note with slide images, a timestamped transcript and editable notes, browsable through a small local server.

    614 GitHub stars~2.3k tokensUpdated 2 mo ago
    Knowledge ManagementAuto-check passed
  • Survey

    SNL-UCSB/literature-survey-skill

    Literature survey assistant with four modes: /survey intent (capture student goals, expertise, and success criteria), /survey triage (landscape mapping via NotebookLM), /survey deepen (structured…

    106 GitHub stars~5k tokensUpdated 6 mo ago
    Knowledge ManagementAuto-check passed
  • Nlm Skill

    iusztinpaul/ai-research-os-workshop

    Expert guide for the NotebookLM CLI (nlm) and MCP server - interfaces for Google NotebookLM.

    179 GitHub starsUsed in 1 repo~6.9k tokens
    Knowledge ManagementAuto-check passed

Questions about Foliole Hosted Quality Repair

What does Foliole Hosted Quality Repair do?

Diagnose, locally repair, verify, and commit one failed independent Foliole dev T7 Hosted Quality run from a handoff locator; route any T7 Release failure back to the existing pinned release task…. Foliole Hosted Quality Repair is an agent skill from campfirium/foliole. Diagnose, locally repair, verify, and commit one failed independent Foliole dev T7 Hosted Quality run from a handoff locator; route any T7 Release failure back to the existing pinned release task instead of creating a repair task.

When should I use Foliole Hosted Quality Repair?

Foliole Hosted Quality Repair fits situations like: A Codex Desktop task names a failed Foliole dev T7 Hosted Quality run; asks the visible controller to take over hosted-quality repair.

How do I install Foliole Hosted Quality Repair in Claude Code?

Run `npx skills add campfirium/foliole --skill foliole-hosted-quality-repair -a claude-code`. Or copy the skill folder (.agents/skills/foliole-hosted-quality-repair in campfirium/foliole) into .claude/skills/foliole-hosted-quality-repair in your project. Claude Code loads it when a task matches its description.

How do I install Foliole Hosted Quality Repair in Codex?

Run `npx skills add campfirium/foliole --skill foliole-hosted-quality-repair -a codex`. Or copy the skill folder (.agents/skills/foliole-hosted-quality-repair in campfirium/foliole) into .agents/skills/foliole-hosted-quality-repair in your project. Codex loads it when a task matches its description.

Can I use Foliole Hosted Quality Repair 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 campfirium/foliole --skill foliole-hosted-quality-repair -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/foliole-hosted-quality-repair, .gemini/skills/foliole-hosted-quality-repair, .github/skills/foliole-hosted-quality-repair and .opencode/skills/foliole-hosted-quality-repair in your project.

What does Foliole Hosted Quality Repair need to run?

Going by SKILL.md and its folder, Foliole Hosted Quality Repair needs the command-line tools its instructions call (gh, git and npm).

Does Foliole Hosted Quality Repair access the network?

SKILL.md contains no URLs. Its commands use gh, git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Foliole Hosted Quality Repair 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. Review the folder before installing.

What licence does Foliole Hosted Quality Repair use?

Foliole Hosted Quality Repair is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Foliole Hosted Quality Repair use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Foliole Hosted Quality Repair?

Skills that share tags, products or a category with Foliole Hosted Quality Repair: NotebookLM Research Workflow (claude-world/notebooklm-skill, 467 stars), Field Lab (KyleAMathews/field-lab, 576 stars), Obsidian StudyVault Builder (bevibing/tutor-skills, 1.3k stars) and YouTube Talk Notetaker (dair-ai/dair-academy-plugins, 614 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Foliole Hosted Quality Repair?

campfirium (a GitHub user) maintains it in campfirium/foliole, which has 138 GitHub stars. The repository was last updated on October 11, 2026.

Source: campfirium/foliole on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.