Daily Focus Board
github/awesome-copilot
Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.
Ask a focused question about another vlx-term session without importing its full conversation into the current context.
MITAuto-check passed
Install Vask
$ npx skills add vlinx-io/VelaTerm --skill vask -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vlinx-io/VelaTerm vask --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/vlinx-io/VelaTerm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vask .claude/skills/vask && 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 "vask" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vask into .claude/skills/vask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vask", 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/vlinx-io/VelaTerm/tree/dev/skills/vaskType 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 vlinx-io/VelaTerm --skill vask -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vlinx-io/VelaTerm vask --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vlinx-io/VelaTerm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vask .agents/skills/vask && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vask" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vask into .agents/skills/vask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vask", 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 vlinx-io/VelaTerm --skill vask -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vlinx-io/VelaTerm vask --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vlinx-io/VelaTerm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vask .cursor/skills/vask && 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 "vask" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vask into .cursor/skills/vask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vask", 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/vlinx-io/VelaTerm.git --path skills/vask--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 vlinx-io/VelaTerm --skill vask -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vlinx-io/VelaTerm vask --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vlinx-io/VelaTerm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vask .gemini/skills/vask && 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 "vask" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vask into .gemini/skills/vask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vask", 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 vlinx-io/VelaTerm vaskInstalls 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 vlinx-io/VelaTerm --skill vask -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vlinx-io/VelaTerm.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vask .github/skills/vask && 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 "vask" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vask into .github/skills/vask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vask", 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 vlinx-io/VelaTerm --skill vask -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vlinx-io/VelaTerm vask --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vlinx-io/VelaTerm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vask .opencode/skills/vask && 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 "vask" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vask into .opencode/skills/vask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vask", 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
vask- GitHub stars
- 270
- Token cost
- ~538 tokens
- SKILL.md length
- 227 words
- Files
- 1
- Skills in repo
- 26
- Repo updated
- First seen
- Licence
- MIT
At a glance
Ask a focused question about another vlx-term session without importing its full conversation into the current context.
- The target session is known and the user needs a conclusion
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vask is an agent skill from vlinx-io/VelaTerm. Ask a focused question about another vlx-term session without importing its full conversation into the current context. This is the skill form of vrefer SESSION --ask "QUESTION". Use it when the target session is known and the user needs a conclusion, decision, result, reason, or status from it. Read-only: nothing is sent to the target session and nobody is interrupted. Available only inside vlx-term-hosted local sessions.
Its SKILL.md is about 540 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: VelaTerm = Codex + iTerm2, The Best ADE for AI Coding. The licence is MIT.
When your agent uses it
- The target session is known and the user needs a conclusion
Example prompts
- “QUESTION”
- “/vask”
Requirements
- Pre-approved tools (allowed-tools): Bash(vrefer:*), Bash(vsearch:*)
What it can do on your machine
Read from SKILL.md and the folder at commit 98b5f2f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(vrefer:*)Bash(vsearch:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
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.
Context cost
Vask loads about 538 tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 227 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from vlinx-io/VelaTerm at commit 98b5f2f, republished under its MIT licence (© vlinx-io). 227 words, ~538 tokens.
Download SKILL.mdSave it as
.claude/skills/vask/SKILL.md (or your agent's skills folder).- name
- vask
- description
- Ask a focused question about another vlx-term session without importing its full conversation into the current context. This is the skill form of `vrefer SESSION --ask "QUESTION"`. Use it when the target session is known and the user needs a conclusion, decision, result, reason, or status from it. Read-only: nothing is sent to the target session and nobody is interrupted. Available only inside vlx-term-hosted local sessions.
- allowed-tools
- Bash(vrefer:*), Bash(vsearch:*)
vask
Use vask as the focused-question form of vrefer --ask. There is no separate shell command: invoke
the existing read-only command with the session reference and the user's question.
vrefer <session> --ask "<question>"If the target is not known, search first:
vsearch <distinctive words...>
vrefer <id-from-search> --ask "<question>"<session> accepts a full id, an id prefix of at least eight characters, an exact session name, or a
unique substring. Quote names containing spaces. If several sessions match, select an id from the
candidate list and retry rather than guessing.
By default the answering agent receives the complete transcript. If the user enabled Summarize first
in Settings → Agents, VelaTerm compresses the transcript with the one globally selected Agent, model,
and reasoning effort, adds relevant original full-text search excerpts from the same session, and then
asks the answering agent. This setting is automatic; the skill command and --ask syntax do not change.
Use --with <kind> only when the user explicitly wants a particular answering agent. It does not
change the configured pre-summary Agent. Use --timeout <seconds> when the default 120-second overall
limit is unsuitable.
The returned text is an agent's reading of another session, not a verbatim transcript. When exact wording
or broader context matters, follow up with vrefer <session> or vrefer <session> --range A:B.
If answering fails, vrefer explains the reason on stderr and returns the transcript as its fallback.
Check stderr before treating stdout as a completed answer.
© vlinx-io, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/vask of vlinx-io/VelaTerm.
Open the folder on GitHubat commit 98b5f2f
Compare with similar skills
Vask 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 |
|---|---|---|---|---|---|---|
| Vask this skillvlinx-io/VelaTerm | 270 | — | ~538 | Automated safety check: Pass | MIT | |
| Daily Focus Boardgithub/awesome-copilot | 40k | — | ~3k | Automated safety check: Pass | MIT | |
| Focus Stylesthedaviddias/Front-End-Checklist | 74k | — | ~639 | Automated safety check: Pass | MIT | |
| Terms Of Servicethedaviddias/Front-End-Checklist | 74k | — | ~585 | Automated safety check: Pass | MIT | |
| Focus Orderthedaviddias/Front-End-Checklist | 74k | — | ~519 | Automated safety check: Pass | MIT | |
| Focus Managementthedaviddias/Front-End-Checklist | 74k | — | ~465 | Automated safety check: Pass | MIT |
Similar skills
- Official
Focus Styles
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Provide visible custom focus indicators.
Terms Of Service
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing whether a website or web application has a visible Terms of Service link accessible from every page.
Focus Order
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure logical focus order.
Focus Management
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Manage focus during dynamic interactions.
Recipe Block Focus Time
googleworkspace/cli
Create recurring focus time blocks on Google Calendar to protect deep work hours.
More from vlinx-io/VelaTerm
All 26 skills in this repoAssess Patch Risk
vlinx-io/VelaTerm
Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility.
Vspawn
vlinx-io/VelaTerm
Explicitly spawn a standalone child session under the current vlx-term session, passing the task in as its first message (mirrors spawntask).
Deep Security Scan
vlinx-io/VelaTerm
A skill your agent uses when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide or scoped-path Codex Security scan.
Define Security Policy
vlinx-io/VelaTerm
Define, review, or update SECURITY.md guidance for a repository or component.
Track Findings
vlinx-io/VelaTerm
Track validated Codex Security findings in Linear, Jira, GitHub issues, or draft GitHub security advisories.
Verify Fix
vlinx-io/VelaTerm
Use only when the user explicitly requests verification that a security fix remediates a reported vulnerability.
Questions about Vask
What does Vask do?
Ask a focused question about another vlx-term session without importing its full conversation into the current context. Vask is an agent skill from vlinx-io/VelaTerm. Ask a focused question about another vlx-term session without importing its full conversation into the current context.
When should I use Vask?
Vask fits situations like: the target session is known and the user needs a conclusion.
How do I install Vask in Claude Code?
Run `npx skills add vlinx-io/VelaTerm --skill vask -a claude-code`. Or copy the skill folder (skills/vask in vlinx-io/VelaTerm) into .claude/skills/vask in your project. Claude Code loads it when a task matches its description.
How do I install Vask in Codex?
Run `npx skills add vlinx-io/VelaTerm --skill vask -a codex`. Or copy the skill folder (skills/vask in vlinx-io/VelaTerm) into .agents/skills/vask in your project. Codex loads it when a task matches its description.
Can I use Vask 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 vlinx-io/VelaTerm --skill vask -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vask, .gemini/skills/vask, .github/skills/vask and .opencode/skills/vask in your project.
What does Vask need to run?
SKILL.md names no scripts, command-line tools or credentials: Vask is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(vrefer:*), Bash(vsearch:*).
Does Vask 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 Vask 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 Vask use?
Vask is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vask use?
About 538 tokens (SKILL.md is roughly 2.2k 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 Vask?
Skills that share tags, products or a category with Vask: Daily Focus Board (github/awesome-copilot, 40k stars), Focus Styles (thedaviddias/Front-End-Checklist, 74k stars), Terms Of Service (thedaviddias/Front-End-Checklist, 74k stars) and Focus Order (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vask?
vlinx-io (a GitHub user) maintains it in vlinx-io/VelaTerm, which has 270 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 7, 2026.
Source: vlinx-io/VelaTerm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.