gravitas
Verify Repository Changes with Gravitas
Coding agents can change repositories without clear scope or reliable evidence. Gravitas provides task contracts, adaptive planning, and verification guidance tied to observed results.
安裝前請停止並請求確認。
請審查安裝計畫,並在變更檔案前取得使用者明確同意。
使用我的智慧代理安裝
將此請求複製給你的智慧代理,其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "gravitas" from https://skillstore.io/skills/udaysharmadev-gravitas.md and its manifest at https://skillstore.io/api/skills/udaysharmadev-gravitas/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.你的智慧代理仍應顯示其計畫,並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時,請使用這些連結。
測試它
正在使用「gravitas」。 Plan a shared authentication timeout change without editing files.
預期結果:
- Scope: update the timeout definition and directly affected tests only.
- Risks: callers may depend on the previous timeout; inspect middleware and integration coverage.
- Verification plan: reproduce current behavior, run focused tests, then check affected callers.
- Status: planning only. No files changed and no verification results claimed.
正在使用「gravitas」。 Assess verification readiness when Python test tools are missing.
預期結果:
- Status: unverifiable because the required test runner is unavailable.
- Evidence: no test execution results are available.
- Next step: obtain approval to prepare the environment, then rerun the required checks.
- Completion: not claimed.
安全審計
高風險Most static alerts match Markdown formatting, local documentation links, source searches, or normal verification tooling. Four execution findings retain package download risks; semantic review identifies an unconditional refusal prohibition and verification helpers that can report success without sufficient checks. No evidence found of credential exfiltration or deliberate malware.
已確認的安全問題 (2)
能力複核項目 (4)
這些是真實的本機能力,對此技能而言可能是預期行為,因此需要複核,但不會按已確認的惡意行為計分。
風險因素
📁 檔案系統存取 (23)
⚙️ 外部命令 (50)
🌐 網路存取 (1)
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據,不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/udaysharmadev-gravitas/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/udaysharmadev-gravitas?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/udaysharmadev-gravitas?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/udaysharmadev-gravitas/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/udaysharmadev-gravitas.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
udaysharmadev. (2026). gravitas security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/udaysharmadev-gravitas/audits/1BibTeX 引用
@techreport{udaysharmadev-udaysharmadev-gravitas-2026,
author = {udaysharmadev},
title = {gravitas security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/udaysharmadev-gravitas/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gravitas security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "udaysharmadev"
date-released: "2026-10-15"
url: "https://skillstore.io/skills/udaysharmadev-gravitas/audits/1"
identifiers:
- type: other
value: "skillstore:udaysharmadev-gravitas:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Reproduce and Verify a Bug Fix
Trace affected code, capture the failing behavior, implement a scoped repair, and compare fresh verification results.
Plan a Shared Module Refactor
Map callers and dependencies, compare implementation options, define rollback steps, and choose regression checks before editing.
Review Evidence for Risky Changes
Check acceptance criteria, execution evidence, unresolved failures, and verification gaps without modifying the repository.
試試這些提示
Use Gravitas to inspect [module] in read-only mode. Identify its tests, callers, and relevant configuration. Report uncertainties without changing files.
Investigate [bug]. Reproduce it before editing and propose a narrow write scope. Use approved local validators after repair. Report skipped checks and failures.
Plan [refactor] without editing files. Define acceptance criteria, non-goals, allowed write scope, dependency impact, verification depth, and rollback steps. Request approval before implementation.
Review [migration] using deep verification planning. Map affected systems and destructive risks. Require approved local validators and explicit checkpoints. Preserve host safeguards and report unverifiable criteria.
最佳實務
- Define explicit acceptance criteria and write boundaries before multi-file or high-risk work.
- Use reviewed, locally installed validators and confirm which checks actually executed after the final change.
- Keep host safety rules active and record unresolved failures, skipped checks, and uncertain claims explicitly.
避免
- Treating prompt instructions as a substitute for installed runtime hooks or enforced permissions.
- Running unreviewed project commands or allowing missing tools to resolve from a package registry without approval.
- Claiming completion from a success banner when required checks were skipped or evidence is stale.