dotai
Skills for agents.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/udecode/dotai with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/udecode/dotai'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/udecode--dotai)HTML
<a href="/listings/udecode--dotai"><img src="/api/listings/udecode--dotai/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Install a skill with the Skills CLI, naming the skill and each agent, for example `npx skills add udecode/dotai --skill test-audit --agent codex claude-code`. Project scope is the default; use `--global` only for a user-wide install.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 35 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- # dotai
- Shared skills that the pstack plugin does not cover: test audits (`test-audit`, adapted from openclaw's), screenshot walkthroughs and video transcripts, and pstack setup, sync and skill-drift audits (`sync-pstack`). Review runs on pstack's panels with Codex seats, on the work each project's reviews list names.
- `passwords` owns unattended 1Password login and new-Mac setup. Each owner's
- machine configuration stays in `~/.config/agent-passwords/machines/`, outside
- the shared source and installed skill folder.
- The engineering method comes from the pstack plugin, `pstack@pstack-claude` from `michael-denyer/pstack-claude`, pinned per project: poteto-mode, its playbooks, the principle skills, how, why, architect, arena, interrogate, swarm, reflect, show-me-your-work, tdd, deslop and the rest. dotai does not vendor them.
- Read [SKILLS.md](SKILLS.md) for the generated inventory, capability limits and pinned install commands for the unchanged upstream skills listed in `upstream-skills.json`. Their source is not copied here.
- ## Ownership
- - `skills/` owns reusable methods. Keep product names, private paths, credentials, release environments and infrastructure assumptions out of shared instructions.
- - `sync-pstack` sets pstack up in a project through an interview and keeps every pstack project on one plugin tag and one shared overrides block. Its `assets/block.md` is the shared override source; project-only rules stay in each project.
- - Each project's instructions own its commands, source and verification owners, and publication policy.
- - Native tools, browser access, provider connections, paid models and host-provided skills are separate capabilities. Installing a method does not supply them.
- ## Install
- Install a skill with the Skills CLI, naming the skill and each agent, for example `npx skills add udecode/dotai --skill test-audit --agent codex claude-code`. Project scope is the default; use `--global` only for a user-wide install.
- ## Validate
- ```sh
- scripts/validate-skills
- scripts/validate-skills --all
- node scripts/build-workflow.mjs
- node scripts/build-workflow.mjs --check
- ```
- `validate-skills` checks every skill's frontmatter and the generated catalog. Then it runs only the skill tests that the working tree's changes can reach. A test file runs when it changed, or when it names a changed file or a script that reaches one. A template under a skill's `assets/` reaches the script that renders that folder. `node scripts/affected-tests.mjs --why` prints each pick and the chain that reached it. `--all` runs every test, as a release or a pstack sync does.
- `build-workflow.mjs` regenerates `SKILLS.md` and `workflow-manifest.json`, rejects duplicate ownership, resolves dependencies and local Markdown references, and records file checksums and modes. `--forbid '<pattern>'` optionally scans shipped content for project or private vocabulary.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.