gardener
Maintain Accurate Agent Context
Stale context files mislead agents and increase maintenance risk. Gardener verifies documentation against code, repairs references, and keeps risk baselines controlled.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "gardener" from https://skillstore.io/skills/drix10-gardener.md and its manifest at https://skillstore.io/api/skills/drix10-gardener/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "gardener". Check whether our agent context is stale after the latest merge.
Expected outcome:
Context health: two stale references found in AGENTS.md. No files changed. Next action: run the documentation repair workflow.
Using "gardener". Review new risk surfaces without accepting anything.
Expected outcome:
- Protected path candidate: deployment credentials directory.
- Risk boundary candidate: release automation scripts.
- Human decision required before any baseline update.
Using "gardener". Repair the flagged documentation and verify it again.
Expected outcome:
Updated verified claims and manifest references. The final context check passed, with one implementation issue opened for a missing lint rule.
Security Audit
SafeMost static findings are false positives caused by Markdown backticks around paths, identifiers, and tool names. Two findings are confirmed because the skill directs agents to run an unpinned npx package and a git command with a repository-derived path.
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
โ๏ธ External commands (26)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/drix10-gardener/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/drix10-gardener?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/drix10-gardener?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/drix10-gardener/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/drix10-gardener.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
drix10. (2026). gardener security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/drix10-gardener/audits/1BibTeX citation
@techreport{drix10-drix10-gardener-2026,
author = {drix10},
title = {gardener security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/drix10-gardener/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: "gardener security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "drix10"
date-released: "2026-09-27"
url: "https://skillstore.io/skills/drix10-gardener/audits/1"
identifiers:
- type: other
value: "skillstore:drix10-gardener:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Check Context Health
Inspect context files for stale claims, missing references, invalid timestamps, and unresolved placeholders.
Review Risk Baselines
Evaluate new risk surfaces and prepare focused choices for human approval.
Refresh Documentation Indexes
Classify documentation as current, stale, missing, or archived using repository history.
Try These Prompts
Run the context health check. Report every failed check and provide the exact next command without changing files.
Update the documentation index from current repository files and commit dates. Show stale, missing, and archived entries before applying edits.
Find stale context claims, verify each against current code, repair supported statements, update references, and rerun validation.
Run synchronization, risk audit, diagnosis, and repair in order. Summarize fixes, required human decisions, and proposed enforcement mechanisms.
Best Practices
- Review the code behind every flagged claim before changing documentation or timestamps.
- Keep human approval for risk acceptance and protected write operations.
- Run the final health check after every repair and explain any remaining failure.
Avoid
- Do not refresh verification timestamps before validating claims against current code.
- Do not accept secrets into a risk baseline or treat heuristic matches as final verdicts.
- Do not delete superseded documentation, edit protected paths, or modify source code through this role.
Frequently Asked Questions
What files can Gardener edit?
Does Gardener change application code?
Can Gardener repair documentation automatically?
How does the risk audit work?
What happens to outdated documents?
Can it run outside the Pi environment?
Developer Details
Author
drix10License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/drix10/agent-flow/tree/aac4c5c023b25d073997626804c355ed11348feb/skills/gardenerRef
8b5ad1599e7c55e9b6c627bca3f556f6e9061cb1
Maintenance freshness
9/30/2026
Usage
0 downloads ยท 0 views
File structure
๐ SKILL.md