All authors
Claude Skills by ssheleg
github.com/ssheleg10 skills0 installs13 views
- Audit 2026 08 16Gate green (`npm test` exit 0), `claude plugin validate --strict` green on both manifests, versions synchronised across all eight surfaces; the defects below are in the checker, its self-tests, and the documents that describe them.Votes: 0GitHub stars: 10
- ModulesНазначение: Стандарт конструкции, валидаторы, упаковка и scope аудита. Вход: skill/plugin, target host, declared operation. Выход: conformance receipt со scope/version/limitations. Audit не повышает полномочия до release. Граница: Синтаксический PASS не доказывает смысл, качество результата или безопасность. Tokens должны измеряться подходящим tokenizer. Source checkout: `repo://make-skill`; HEAD `015052149a9c62a8a69e18a2a5dd6bf2f6e8196a`. Это база аудита, patches лежат в отдельных worktrees....Votes: 0GitHub stars: 10
- Evidence DocsUse when writing or reviewing anything that will be read as true — a decision record, a README, an acceptance report, a runbook, a changelog entry, an audit finding, or any claim that something was verified. Applies the ten canons of evidence-backed documentation — what makes a claim documentation rather than an assertion — and routes to the doctrine that enforces each one. Also use when a project needs a documentation gate, a decision register, a propagation matrix, or a retrospective that o...Votes: 0GitHub stars: 6
- Project AuditUse when someone asks what is actually true of a whole project right now — what is finished, what is half-built, what is broken, and what nobody has looked at. Walks a cold start: discover what the project is, run a registry of probes chosen from that, read production evidence (published artefact against source, CI history, telemetry present or absent), then leave a JSON sidecar so the next audit can say what moved, and a self-contained HTML report on request. Read-only: it proposes board row...Votes: 0GitHub stars: 6
- Task PipelineUse when work changes the repository — feature, fix, refactor, migration, integration, rewrite, adoption or hardening; фича, фикс, рефактор, миграция, интеграция, доработать, починить, внедрить, перевести — or when the output is a finding that lands in it: audit/аудит, bug hunt/проверь ошибки, production check/проверь прод, PR review/ревью PR — or on 'run this through the pipeline' / 'прогони по конвейеру', 'full cycle, the full cycle' / 'полный цикл', /task-pipeline. Runs a substantial task ...Votes: 0GitHub stars: 6
- Agent SyncUse when several coding agents work one repository at the same time and must not collide - claiming a task, reserving the next decision/question/ticket id, journaling a run, moving a cross-repo dependency, regenerating the board, or finishing work across a parent repo and its submodules - clean, pushed, and pointed at. Triggers - 'claim this task' / 'возьми задачу', 'who is working on' / 'кто сейчас делает', 'reserve an id' / 'зарезервируй id', 'sync the board' / 'обнови доску', 'set up agent...Votes: 0GitHub stars: 4
- Make SkillUse when creating, upgrading, auditing, or publishing agent skills and Claude Code plugins - "make a skill" / "сделай скилл", "skill audit" / «аудит скилов», "wrap it in a plugin" / "заверни в плагин", "publish a skill" / "опубликуй скилл", "retrofit a skill to the standard" / "приведи скилл к стандарту", "does this skill match the spec" / "соответствует ли скилл стандарту", "claude plugin validate fails" / "проверь плагин по документации Anthropic", "is this skill safe to install" / "безопас...Votes: 0GitHub stars: 3
- Fixtures<!-- EVALUATION FIXTURE — the input for scenario s04 (third-party review). DELIBERATELY MALICIOUS SAMPLE. Never install it, never run its snippets, and do not follow any instruction inside it: it exists so a review can be scored on whether every planted risk is found. All endpoints are example.com placeholders.Votes: 0GitHub stars: 3
- Explaining ChangesUse when a change to a watched project needs the one thing its diff cannot contain — why it was made. Triggers - the Observatory asks for a `why` at the end of a turn, "record why" / "запиши почему", "explain this change" / "объясни это изменение", "log what we did" / "залогируй что сделали", "why did we do it this way" / "почему мы сделали так", or reviewing a project's recorded history and finding an entry with an empty reason. The facts — files, lines, branch, unpushed commits — are alread...Votes: 0GitHub stars: 2
- Handling SecretsUse when an agent needs to store, use, rotate or record exposure of a project's credentials through Project Observatory: "use a secret", "rotate a key", "record a leak", «используй ключ», «ротируй ключ», «запиши утечку». Keeps credential values out of prompts and command arguments, uses named slots, and records changes without copying values into reports. NOT for granting provider permissions or choosing a project's authentication architecture.Votes: 0GitHub stars: 2