CSS At Property
thedaviddias/Front-End-Checklist
A skill your agent uses when implementing animated gradients, complex CSS transitions that involve custom property values, or building a typed design token system where custom property misuse should…
Read a VelaTerm session's saved properties and parent-child relationships.
MITAuto-check passed
Install Vself
$ npx skills add vlinx-io/VelaTerm --skill vself -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vlinx-io/VelaTerm vself --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/vself .claude/skills/vself && 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 "vself" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vself into .claude/skills/vself/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vself", 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/vselfType 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 vself -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vlinx-io/VelaTerm vself --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/vself .agents/skills/vself && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vself" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vself into .agents/skills/vself/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vself", 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 vself -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vlinx-io/VelaTerm vself --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/vself .cursor/skills/vself && 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 "vself" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vself into .cursor/skills/vself/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vself", 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/vself--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 vself -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vlinx-io/VelaTerm vself --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/vself .gemini/skills/vself && 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 "vself" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vself into .gemini/skills/vself/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vself", 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 vselfInstalls 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 vself -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/vself .github/skills/vself && 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 "vself" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vself into .github/skills/vself/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vself", 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 vself -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 vself --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/vself .opencode/skills/vself && 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 "vself" agent skill from https://github.com/vlinx-io/VelaTerm/tree/dev/skills/vself into .opencode/skills/vself/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vself", 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
vself- GitHub stars
- 270
- Token cost
- ~764 tokens
- SKILL.md length
- 353 words
- Files
- 1
- Skills in repo
- 26
- Repo updated
- First seen
- Licence
- MIT
At a glance
Read a VelaTerm session's saved properties and parent-child relationships.
- Agent sessions when the user asks who spawned a session
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Which child sessions it has
- What configuration is saved on it
What it does
Vself is an agent skill from vlinx-io/VelaTerm. Read a VelaTerm session's saved properties and parent-child relationships. Use for ordinary or agent sessions when the user asks who spawned a session, which child sessions it has, or what configuration is saved on it. Can inspect the current session or another session by ID or name. Read-only: does not open, launch, message or interrupt any session.
Its SKILL.md is about 760 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
- Agent sessions when the user asks who spawned a session
- Which child sessions it has
- What configuration is saved on it
Example prompts
- “/vself”
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 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
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
Vself loads about 764 tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 353 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). 353 words, ~764 tokens.
Download SKILL.mdSave it as
.claude/skills/vself/SKILL.md (or your agent's skills folder).- name
- vself
- description
- Read a VelaTerm session's saved properties and parent-child relationships. Use for ordinary or agent sessions when the user asks who spawned a session, which child sessions it has, or what configuration is saved on it. Can inspect the current session or another session by ID or name. Read-only: does not open, launch, message or interrupt any session.
vself
vself
vself <session>
vself [session] --jsonOmit the target to query the calling session. A target accepts a full ID, an ID prefix of at least eight
characters, an exact name or a unique name substring. Quote names containing spaces. An ambiguous
reference returns candidates; use an exact ID rather than guessing. To find a session ID by name,
vrefer --list lists the connected instance's sessions, including those with no readable transcript.
The text form lists identity, parent, ancestors and direct children. Use --json whenever saved
attributes are requested. This works for terminal, agent and browser sessions, including archived ones,
without requiring a plan-execute workflow or an active process.
JSON has session, parent, ancestors and children. parent is null for a top-level session;
ancestors starts with the immediate parent. children contains only direct children, ordered as in
the sidebar, including archived children whose parent link is still saved. Query a child to inspect
its children. Relationships come from parentSessionId, not similar names or groupId.
Each session object contains its saved fields: ID, project/group, name, agent kind, shell, directory,
launch configuration, permissions, collaboration mode, preset, executable, shortcut, engine, native
conversation ID, parent ID, collapse/fork state, worktree and baseline ref, archive time, browser URL,
mark, sort order and creation time. Additional properties are modelSettings (saved model/effort),
launchModelSettings (model/effort explicitly present in saved launch arguments),
codexSettings (service tier/personality), claudeSettings (Chrome), autoContinue (saved resumption
schedule), and workflowIds (direct memberships). Null denotes an unset saved value, not an inferred
effective default. Lookup does not run the agent or sample its native configuration files.
Show full SKILL.md (100 more words)Show less
redactedFields identifies masked launch input, environment values and URL credentials/query/fragment;
environment variable names remain visible. Do not interpret masked values as missing configuration.
Use vflow list <session> for related plan-execute tasks and current workflow states, or
vrefer <session> for its conversation. A native agentSessionId is different from the VelaTerm ID:
use id/sessionId in VelaTerm commands.
Run inside a VelaTerm-hosted session so the injected VLX_* environment points at the right backend.
Queries read only that connected instance. If the command rejects a target argument, the running
backend predates this query form; report the version mismatch instead of guessing or modifying SQLite.
© 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/vself of vlinx-io/VelaTerm.
Open the folder on GitHubat commit 98b5f2f
Compare with similar skills
Vself 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 |
|---|---|---|---|---|---|---|
| Vself this skillvlinx-io/VelaTerm | 270 | — | ~764 | Automated safety check: Pass | MIT | |
| CSS At Propertythedaviddias/Front-End-Checklist | 74k | — | ~602 | Automated safety check: Pass | MIT | |
| Logical Propertiesthedaviddias/Front-End-Checklist | 74k | — | ~526 | Automated safety check: Pass | MIT | |
| Setting Up Warehouse PropertiesPostHog/posthog | 40k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Context Savegarrytan/gstack | 136k | — | ~9.8k | Automated safety check: Notes | MIT | |
| CSS Custom Propertiesthedaviddias/Front-End-Checklist | 74k | — | ~492 | Automated safety check: Pass | MIT |
Similar skills
Logical Properties
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use CSS logical properties for i18n and RTL support.
- Official
Setting Up Warehouse Properties
PostHog/posthog
Populate person or group properties from a data warehouse table or materialized view, so warehouse columns become properties usable in feature flags, cohorts, and insights.
Context Save
garrytan/gstack
Captures git state, decisions made and remaining work so that a later session can resume the task without losing context.
CSS Custom Properties
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use CSS custom properties for design tokens.
Aria Required Parent
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure ARIA roles are contained by required parent roles.
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 Vself
What does Vself do?
Read a VelaTerm session's saved properties and parent-child relationships. Vself is an agent skill from vlinx-io/VelaTerm. Read a VelaTerm session's saved properties and parent-child relationships.
When should I use Vself?
Vself fits situations like: agent sessions when the user asks who spawned a session; which child sessions it has; what configuration is saved on it.
How do I install Vself in Claude Code?
Run `npx skills add vlinx-io/VelaTerm --skill vself -a claude-code`. Or copy the skill folder (skills/vself in vlinx-io/VelaTerm) into .claude/skills/vself in your project. Claude Code loads it when a task matches its description.
How do I install Vself in Codex?
Run `npx skills add vlinx-io/VelaTerm --skill vself -a codex`. Or copy the skill folder (skills/vself in vlinx-io/VelaTerm) into .agents/skills/vself in your project. Codex loads it when a task matches its description.
Can I use Vself 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 vself -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vself, .gemini/skills/vself, .github/skills/vself and .opencode/skills/vself in your project.
What does Vself need to run?
SKILL.md names no scripts, command-line tools or credentials: Vself is instructions for the agent only.
Does Vself 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 Vself 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 Vself use?
Vself 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 Vself use?
About 764 tokens (SKILL.md is roughly 3.1k 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 Vself?
Skills that share tags, products or a category with Vself: CSS At Property (thedaviddias/Front-End-Checklist, 74k stars), Logical Properties (thedaviddias/Front-End-Checklist, 74k stars), Setting Up Warehouse Properties (PostHog/posthog, 40k stars) and Context Save (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vself?
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.