npm - agent-skills-standard - Versions diffs - 2.6.1 → 2.6.4 - Mend

agent-skills-standard 2.6.1 → 2.6.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (5) hide show

package/LICENSE CHANGED Viewed

@@ -1,201 +1,21 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-   1. Definitions.
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-   END OF TERMS AND CONDITIONS
-   APPENDIX: How to apply the Apache License to your work.
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-   Copyright [yyyy] [name of copyright owner]
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-       http://www.apache.org/licenses/LICENSE-2.0
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.
+MIT License
+Copyright (c) 2026 Hoang Nguyen
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md CHANGED Viewed

@@ -5,7 +5,7 @@
 **Sync 242 AI coding standards to any project in one command.** Works with Cursor, Claude Code, GitHub Copilot, Gemini, Windsurf, Trae, Kiro, and Roo.
-**Current release:** `v2.5.1` — automated SkillSpector security scanning, pull request evaluation gates, and verified release tags.
+**Current release:** `v2.6.4` — skill validator accepts package directories under `scripts/`; SkillSpector security scanning, pull request evaluation gates, and verified release tags.
 ```bash
 npx agent-skills-standard@latest init   # detect your stack
@@ -44,7 +44,55 @@ The result: your AI agent reads `AGENTS.md`, follows the router to the right cat
 | `validate` | Checks your custom skills against format and token standards                                                                                                                                       |
 | `feedback` | Submits improvement suggestions to the registry                                                                                                                                                    |
 | `upgrade`  | Updates the CLI to the latest version                                                                                                                                                              |
+| `doctor`   | Check installation health (config, agents, lock file, MCP, hooks, CLI version) with human or JSON output and safe repairs                                                                         |
+| `restore`   | List backups in `.ags/backups` or restore one (replace-only)                                                                                                        |
+| `uninstall` | Remove files ags installed (keeps files you edited); backs up first                                                                                               |
+| `verify`    | Check installed files against `.skills-lock.json` (`--strict`, `--attestation`)                                                                                   |
+| `policy`    | Manage and check project agent policies (status, check, validate, compile, adopt)                                                                                  |
+### Install Safety & Sync Options
+`ags sync` safely tracks owned files in `.skills-lock.json` v2 and preserves local user edits:
+- **User-Edit Preservation**: If you edited a synced skill, workflow, specialist, or bridge file, sync keeps your version and warns instead of overwriting it.
+- `--dry-run`: Preview additions, updates, kept edits, and prunes without writing anything to disk or modifying configs.
+- `--dry-run --verbose`: List every affected file path by status.
+- `--dry-run --json`: Emit the full install plan as machine-readable JSON (`schema_version: 1, kind: 'sync.plan'`).
+- `--force <paths...>`: Overwrite specified user-edited files with upstream versions (a backup is created first).
+- **Automatic Backups**: Destructive changes (pruning or forced overwrites) automatically snapshot previous files into `.ags/backups/<timestamp>/` (retaining the 3 most recent backups).
+### Restore & Uninstall
+- `ags restore [--list] [id]`: List backups or restore files from `.ags/backups/<id>` (replace-only; does not delete newer files or modify lockfile).
+- `ags uninstall [--agent <agents...>] [--category <categories...>] [--all] [--dry-run] [-y, --yes]`:
+  - Removes only manifest entries whose on-disk sha256 still matches (owned-unchanged).
+  - Keeps user-edited files byte-identical.
+  - Automatically creates a backup of removed files and `.skills-lock.json` before deleting.
+  - `--all` removes all owned files, cleans MCP and hook registrations, clears `AGENTS.md` index block, and deletes `.skills-lock.json`. `CLAUDE.md` and `.skillsrc` are left unchanged.
+  - Non-interactive environments without `--yes` exit 1 with a preview.
+### Verification: `ags verify`
+Check installed files against `.skills-lock.json` to detect tampering, partial writes, or manual drift:
+- `ags verify`: Checks file integrity against the lockfile.
+- `ags verify --strict`: In addition to file integrity, fails (exit 1) if any locked ref now resolves to a different commit (moved tag) or cannot be resolved.
+- `ags verify --attestation`: Verifies build-provenance attestations using the GitHub CLI (`gh`). Requires `gh` on PATH; fails if any pinned source lacks `MANIFEST.json` or fails attestation.
+### Policy Layer: `ags policy`
+Prevents mistakes by cooperating agents; not a security boundary.
+Manage and check deterministic project rules in `.ags/policy.json` (`protected_path`, `command`, `required_check`):
+- `ags policy status [--json]`: Show policy rules in force and built-in rules (identity/secret deny-list).
+- `ags policy check (--path <p> | --command <cmd> | --diff) [--no-bypass] [--json]`: Evaluate a path, command executable, or git diff against active policy rules.
+- `ags policy validate [--fail-on-stale] [--json]`: Validate `.ags/policy.json` for schema errors, rule conflicts, and stale compiled rules.
+- `ags policy compile [--json]`: Scan `AGENTS.md` and `CLAUDE.md` to propose candidate rules into `.ags/policy-candidates.json`. Compiled rules can only warn or rewrite.
+- `ags policy adopt <ids...> [--json]`: Activate candidate rules into `.ags/policy.json` after conflict validation.
+Set `AGS_POLICY_BYPASS=1` (or `AGS_POLICY_BYPASS=true`) to turn policy decisions into allow while reporting waived rules.
 ---
 ## Configuration
@@ -54,6 +102,8 @@ The `.skillsrc` file controls everything:
 ```yaml
 registry: https://github.com/HoangNguyen0403/agent-skills-standard
 agents: [cursor, copilot, claude]
+workflows_ref: workflows-v1.0.0      # pinned workflows release tag
+specialists_ref: specialists-v2.0.0  # pinned specialists release tag
 skills:
   react:
     ref: react-v1.3.1
@@ -65,6 +115,8 @@ skills:
     custom_overrides: ['common-tdd'] # protect your local edits
 ```
+A project without pins gets `workflows_ref` and `specialists_ref` written once to `.skillsrc` on first sync from the registry's latest releases (`--dry-run` never writes them). If the registry does not publish releases, sync falls back to the default branch with a warning.
 ---
 ## What Gets Generated
@@ -104,12 +156,59 @@ ags mcp uninstall --from project   # remove our entry; siblings preserved
 The CLI **never** modifies user-home files (`~/.cursor/mcp.json`, `~/.gemini/settings.json`, etc.) unless you explicitly choose `scope: user` AND confirm each write. See [`mcp/README.md`](../mcp/README.md) for full details and [`mcp/ARCHITECTURE.md`](../mcp/ARCHITECTURE.md) for the threat model.
+## Installation Health: `ags doctor`
+Run read-only health checks across seven subsystems: configuration (`.skillsrc`), detected/configured agents, skill-content lockfile (`.skills-lock.json`), MCP server registrations, pre-edit hooks, legacy folder migrations, and CLI version.
+```bash
+ags doctor                   # Human-readable health check report
+ags doctor --offline         # Skip the network-backed CLI version check
+ags doctor --json            # Emit a versioned JSON report (schema_version: 1, kind: 'doctor.report')
+ags doctor --exit-on-fail    # Exit with code 1 when any check fails (default exit code is 0)
+ags doctor --fix             # Apply available safe repairs interactively (prompts per fix)
+ags doctor --fix --yes       # Apply repairs non-interactively
+```
+### JSON Envelope
+When `--json` is supplied, `ags doctor` outputs a single JSON payload matching the `doctor.report` contract:
+```json
+{
+  "schema_version": 1,
+  "kind": "doctor.report",
+  "data": {
+    "schema_version": 1,
+    "checks": [
+      {
+        "name": "config",
+        "status": "ok",
+        "evidence": ".skillsrc parsed",
+        "fixable": false
+      }
+    ],
+    "summary": {
+      "total": 7,
+      "ok": 7,
+      "warn": 0,
+      "fail": 0,
+      "skip": 0
+    },
+    "healthy": true
+  }
+}
+```
+### Exit Behavior
+`ags doctor` always exits with code `0` by default so it never unexpectedly breaks pipelines. When `--exit-on-fail` is passed, it exits with code `1` if any check produces a `fail` status (`healthy: false`).
 ---
 ## Privacy & Security
 - **Text only** — the CLI downloads Markdown and JSON files, never binaries or scripts
-- **No telemetry** — zero data collection, no background processes
+- **No telemetry by default** — zero data collection unless you opt into the local usage log (see docs/FRESHNESS.md)
 - **Transparent** — fetches from the [public registry](https://github.com/HoangNguyen0403/agent-skills-standard), nothing hidden
 - **Override protection** — `custom_overrides` prevents the CLI from touching your local modifications
 - **MCP consent model** — runtime configs in `$HOME` are only ever modified with explicit per-file consent