New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Qv Dev Diary Setup

by tetherto in tetherto/qvac

Set up the opt-in local dev diary for any developer. An agent skill from tetherto/qvac.

Apache-2.0Auto-check passedKnowledge Management

Install Qv Dev Diary Setup

skills CLI
$ npx skills add tetherto/qvac --skill qv-dev-diary-setup -a claude-code

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

GitHub CLI
$ gh skill install tetherto/qvac qv-dev-diary-setup --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/tetherto/qvac.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/qv-dev-diary-setup .claude/skills/qv-dev-diary-setup && 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
qv-dev-diary-setup
GitHub stars
674
Token cost
~874 tokens
SKILL.md length
372 words
Files
2
Skills in repo
50
Repo updated
First seen
Licence
Apache-2.0

At a glance

Set up the opt-in local dev diary for any developer. An agent skill from tetherto/qvac.

  • Works in 7 steps: Open Asana developer console. → Create a Personal Access Token. → Description suggestion: Local… → …
  • The user asks to enable diary logging
  • SKILL.md covers Asana Token Setup, Commands, Workflow and Rules
  • Calls node and curl; needs ASANA_ACCESS_TOKEN

What it does

Qv Dev Diary Setup is an agent skill from tetherto/qvac. Set up the opt-in local dev diary for any developer. Use when the user asks to enable diary logging, initialize diary capture, run diary --init, or configure local daily work updates.

Its SKILL.md is about 870 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, covering Journaling and reflection. It works with Asana. The repository describes itself as: Open-source local AI SDK - run AI on-device with no cloud, no API keys. Supports GGUF, RAG, image, music, and video generation, speech-to-text, P2P inference, and more… The licence is Apache-2.0.

When your agent uses it

  • The user asks to enable diary logging
  • Initialize diary capture
  • Run diary --init
  • Configure local daily work updates

Example prompts

  • “/qv-dev-diary-setup”

Requirements

  • A credential in ASANA_ACCESS_TOKEN

Workflow steps

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

  1. Open Asana developer console.
  2. Create a Personal Access Token.
  3. Description suggestion: Local qvac-pr-skills.
  4. Permission model: Asana Personal Access Tokens do not require choosing scopes in this setup. The token acts as the current Asana user and…
  5. No OAuth app and no Asana MCP server are needed.
  6. Store it in your default shell startup file or export it in the current shell. Coding agents may not inherit the app environment, so the…
  7. Verify manually

What it can do on your machine

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

    • node
    • curl

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

  • Network

    Links to these hosts (documentation or services it may open):

    • developers.asana.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • ASANA_ACCESS_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Qv Dev Diary Setup loads about 874 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 372 words of instructions outside code blocks.

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

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 tetherto/qvac at commit d92f697, republished under its Apache-2.0 licence (© tetherto). 372 words, ~874 tokens.

Download SKILL.mdSave it as .claude/skills/qv-dev-diary-setup/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
qv-dev-diary-setup
description
Set up the opt-in local dev diary for any developer. Use when the user asks to enable diary logging, initialize diary capture, run diary --init, or configure local daily work updates.
disable-model-invocation
true

Dev Diary Setup

Sets up local diary capture. The diary is off by default and only turns on after initialization succeeds.

Use this skill only for setup/enable/disable. For reading, editing, or adding diary entries after setup, use qv-dev-diary.

Asana Token Setup

When using --asana or an Asana config file, first show these instructions to the user before checking whether ASANA_ACCESS_TOKEN exists:

  1. Open Asana developer console.
  2. Create a Personal Access Token.
  3. Description suggestion: Local qvac-pr-skills.
  4. Permission model: Asana Personal Access Tokens do not require choosing scopes in this setup. The token acts as the current Asana user and can access whatever that user can access. For this workflow, that user must be able to read the workspace/project/tasks; for sync actions, the user must also be allowed to comment, move, and complete tasks in that project.
  5. No OAuth app and no Asana MCP server are needed.
  6. Store it in your default shell startup file or export it in the current shell. Coding agents may not inherit the app environment, so the helper falls back to asking your default shell for this variable.
bash
export ASANA_ACCESS_TOKEN='<token>'
  1. Verify manually:
bash
curl https://app.asana.com/api/1.0/users/me \
  -H "Authorization: Bearer $ASANA_ACCESS_TOKEN"

Docs: Asana personal access token

Commands

Basic local diary only:

bash
node .agents/skills/_lib/developer-workflow/diary-cli.mjs --init --basic

Local diary plus Asana config import:

bash
node .agents/skills/_lib/developer-workflow/diary-cli.mjs --init /path/to/asanaconfig.json

Status:

bash
node .agents/skills/_lib/developer-workflow/diary-cli.mjs --status

Disable:

bash
node .agents/skills/_lib/developer-workflow/diary-cli.mjs --off
Show full SKILL.md (165 more words)Show less

Workflow

For Asana-backed setup:

  1. Present the Asana Token Setup section above.
  2. Do not run a raw shell check like test -n "$ASANA_ACCESS_TOKEN" or echo "$ASANA_ACCESS_TOKEN". That only checks the agent process environment and bypasses the helper's default-shell fallback.
  3. Run the init command directly and let diary-cli.mjs resolve the token from process.env or the user's default shell startup files:
bash
node .agents/skills/_lib/developer-workflow/diary-cli.mjs --init /path/to/asanaconfig.json
  1. If the helper reports a missing token, stop after showing its output. Do not replace it with a shorter "export token" message.
  2. If init succeeds, confirm diary status:
bash
node .agents/skills/_lib/developer-workflow/diary-cli.mjs --status

Rules

  • Do not enable diary capture unless init succeeds.
  • Do not ask for Slack channel during init.
  • Do not write tokens, Asana IDs, or diary entries into repo files.
  • If Asana is requested, walk the user through creating ASANA_ACCESS_TOKEN and verify /users/me.
  • If an Asana config path is provided, it must contain only shared workspace/project/section/custom-field metadata.
  • Never preflight token presence with raw shell env checks; always use diary-cli.mjs / asana.mjs so default-shell fallback is applied.

© tetherto, 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/qv-dev-diary-setup of tetherto/qvac.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit d92f697

Compare with similar skills

Qv Dev Diary Setup 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.

Qv Dev Diary Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qv Dev Diary Setup this skilltetherto/qvac674—~874Automated safety check: PassApache-2.0
LLM Wikilewislulu/llm-wiki-skill655—~3.7kAutomated safety check: PassNone
Munger Perspectivealchaincyf/munger-skill3771 repos~3.7kAutomated safety check: PassMIT
Daily Journalhuytieu/COG-second-brain1.3k—~1.3kAutomated safety check: PassMIT
Letterboxd Diaryjoe-bell/skills211—~4.2kAutomated safety check: PassMIT
Em Grid Scorermanager-dot-dev/manager-skills114—~5.8kAutomated safety check: PassMIT

Similar skills

  • LLM Wiki

    lewislulu/llm-wiki-skill

    Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…

    655 GitHub stars~3.7k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed

  • Munger Perspective

    alchaincyf/munger-skill

    查理·芒格的思维框架与表达方式。基于《穷查理宝典》、伯克希尔/Daily Journal股东会、 USC/哈佛演讲、访谈记录、外部批评等50+来源的深度调研， 提炼5个核心心智模型、8条决策启发式和完整的表达DNA。

    377 GitHub starsUsed in 1 repo~3.7k tokens
    Knowledge ManagementAuto-check passed

  • Daily Journal

    huytieu/COG-second-brain

    A passive daily work journal that Claude keeps FOR you so you never have to write it yourself.

    1.3k GitHub stars~1.3k tokensUpdated 5 days ago
    Knowledge ManagementAuto-check passed

  • Letterboxd Diary

    joe-bell/skills

    Fetch recently watched films from a Letterboxd member's diary RSS feed and render them as a compact markdown list, with first-run setup for the username.

    211 GitHub stars~4.2k tokensUpdated 3 days ago
    Knowledge ManagementAuto-check passed

  • Em Grid Scorer

    manager-dot-dev/manager-skills

    Score an Engineering Manager's coverage across all 12 cells of the EM Grid based on their calendar and Slack.

    114 GitHub stars~5.8k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed

  • Digital Brain

    foryourhealth111-pixel/Vibe-Skills

    This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content…

    3.6k GitHub stars~1.7k tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed

More from tetherto/qvac

All 50 skills in this repo

  • Qv Docs Solution Create

    tetherto/qvac

    Creates a Solutions page in the QVAC documentation website from a real use case, generalizing the case into reusable guidance and registering the page in the site navigation.

    674 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Qv Docs Update

    tetherto/qvac

    Updates the docs website after a change to the SDK or CLI. An agent skill from tetherto/qvac.

    674 GitHub stars~11k tokensUpdated today
    Auto-check passed

  • Qv Agent Stack Sync

    tetherto/qvac

    Plan and prepare the QVAC agent-stack release cascade across @qvac/inference, @qvac/sdk, @qvac/cli, @qvac/ai-sdk-provider, @qvac/opencode-plugin, and @qvac/openclaw-plugin.

    674 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Qv Quality Reporting

    tetherto/qvac

    Run the deterministic code-quality audit, turn related findings into contextual remediation groups, prepare approval-gated Asana proposals, reconcile recurring runs, or configure twice-monthly…

    674 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Cpp String API Review

    tetherto/qvac

    Review C++ changes for string parameter and call-site efficiency conventions (std::stringview, std::string&&, const std::string&, const char, and TransparentStringMap lookup).

    674 GitHub stars~702 tokensUpdated today
    Auto-check passed

  • Qv Addon Changelog

    tetherto/qvac

    Generate changelog entries for a target add-on package. An agent skill from tetherto/qvac.

    674 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Qv Dev Diary Setup

What does Qv Dev Diary Setup do?

Set up the opt-in local dev diary for any developer. An agent skill from tetherto/qvac. Qv Dev Diary Setup is an agent skill from tetherto/qvac. Set up the opt-in local dev diary for any developer.

When should I use Qv Dev Diary Setup?

Qv Dev Diary Setup fits situations like: the user asks to enable diary logging; initialize diary capture; run diary --init; configure local daily work updates.

How do I install Qv Dev Diary Setup in Claude Code?

Run `npx skills add tetherto/qvac --skill qv-dev-diary-setup -a claude-code`. Or copy the skill folder (.agents/skills/qv-dev-diary-setup in tetherto/qvac) into .claude/skills/qv-dev-diary-setup in your project. Claude Code loads it when a task matches its description.

How do I install Qv Dev Diary Setup in Codex?

Run `npx skills add tetherto/qvac --skill qv-dev-diary-setup -a codex`. Or copy the skill folder (.agents/skills/qv-dev-diary-setup in tetherto/qvac) into .agents/skills/qv-dev-diary-setup in your project. Codex loads it when a task matches its description.

Can I use Qv Dev Diary Setup 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 tetherto/qvac --skill qv-dev-diary-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qv-dev-diary-setup, .gemini/skills/qv-dev-diary-setup, .github/skills/qv-dev-diary-setup and .opencode/skills/qv-dev-diary-setup in your project.

What does Qv Dev Diary Setup need to run?

Going by SKILL.md and its folder, Qv Dev Diary Setup needs the command-line tools its instructions call (node and curl) and credentials named ASANA_ACCESS_TOKEN. Our summary lists: A credential in ASANA_ACCESS_TOKEN.

Does Qv Dev Diary Setup access the network?

SKILL.md names 1 domain. As links in the text: developers.asana.com. This is read from the text; nothing was executed.

Is Qv Dev Diary Setup 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 Qv Dev Diary Setup use?

Qv Dev Diary Setup 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 Qv Dev Diary Setup use?

About 874 tokens (SKILL.md is roughly 3.5k 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 Qv Dev Diary Setup?

Skills that share tags, products or a category with Qv Dev Diary Setup: LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), Munger Perspective (alchaincyf/munger-skill, 377 stars), Daily Journal (huytieu/COG-second-brain, 1.3k stars) and Letterboxd Diary (joe-bell/skills, 211 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Qv Dev Diary Setup?

tetherto (a GitHub organization) maintains it in tetherto/qvac, which has 674 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 7, 2026.

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