dbs-skill-maker
Build and Validate Reusable Agent Skills
Recurring tasks often lack clear boundaries, reusable instructions, and reliable acceptance tests. This skill turns those tasks into focused agent skills with structured validation and optional GitHub delivery.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "dbs-skill-maker" from https://skillstore.io/skills/dontbesilent2025-dbs-skill-maker.md and its manifest at https://skillstore.io/api/skills/dontbesilent2025-dbs-skill-maker/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 "dbs-skill-maker". Create a local skill that turns approved incident notes into a customer update.
Expected outcome:
- Candidate: incident-update, with task instructions and interface metadata.
- Boundary: use approved notes only; stop when customer impact is unknown.
- Validation: structural checks passed; behavior remains unverified.
- Delivery: local files only; no remote repository created.
Using "dbs-skill-maker". Review a candidate that produces inconsistent release summaries.
Expected outcome:
- Observed failure: the candidate includes changes outside the requested release.
- Proposed change: require an explicit release boundary before selecting changes.
- Evaluation plan: compare baseline and candidate on normal, boundary, negative, and held-out cases.
- Status: improvement remains unproven until actual outputs pass the evaluation.
Using "dbs-skill-maker". Prepare this reviewed skill for sharing without publishing it yet.
Expected outcome:
- Prepared local repository staging with a README and runtime skill resources.
- Compared staged files with the source and excluded evaluation records.
- Remote creation, pushing, tags, releases, and external installation verification remain pending authorization.
Security Audit
Medium RiskMost alerts are Markdown formatting, readable Chinese documentation, or bounded syntax checks; no evidence found of encrypted payloads or audit manipulation. Repository preparation trusts the frontmatter name, allowing file copies outside staging and possible overwrites. Additional concerns involve unsandboxed installation verification and instructions recommending an entire external skill collection globally.
Confirmed security concerns (2)
Capability review items (1)
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 (29)
📁 Filesystem access (2)
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/dontbesilent2025-dbs-skill-maker/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dontbesilent2025-dbs-skill-maker?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dontbesilent2025-dbs-skill-maker?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dontbesilent2025-dbs-skill-maker/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dontbesilent2025-dbs-skill-maker.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
dontbesilent2025. (2026). dbs-skill-maker security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dontbesilent2025-dbs-skill-maker/audits/1BibTeX citation
@techreport{dontbesilent2025-dontbesilent2025-dbs-skill-maker-2026,
author = {dontbesilent2025},
title = {dbs-skill-maker security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/dontbesilent2025-dbs-skill-maker/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: "dbs-skill-maker security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "dontbesilent2025"
date-released: "2026-10-17"
url: "https://skillstore.io/skills/dontbesilent2025-dbs-skill-maker/audits/1"
identifiers:
- type: other
value: "skillstore:dontbesilent2025-dbs-skill-maker:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Standardize a Repeated Development Task
Turn a recurring code-review preparation task into one skill with clear inputs, exclusions, and observable completion checks.
Formalize a Team Workflow
Convert recurring operational questions into a reusable skill with explicit decisions, required evidence, and permission boundaries.
Evaluate an Existing Skill
Assess a candidate against normal, boundary, negative, and held-out cases before choosing a minimal improvement and running regression checks.
Try These Prompts
Use dbs-skill-maker to turn my recurring meeting-summary task into one skill. Define its inputs, outputs, boundaries, and observable completion criteria.
Create a local release-notes skill from these requirements and examples. Generate real files, run structural checks, and report unverified behavior. Do not publish or install dependencies.
Evaluate this candidate skill using normal, boundary, negative, and held-out cases. Keep expected answers hidden from execution. Propose one minimal change and check regressions.
Prepare a local GitHub staging directory for this reviewed skill. Validate destination containment and inspect public files. Request approval before remote writes or external installation checks.
Best Practices
- Define observable success, excluded tasks, and permission boundaries before generating files.
- Keep expected answers separate from execution and report only the validation level supported by actual evidence.
- Review destination paths and public files, and approve external installation or remote writes separately.
Avoid
- Treating structural validation as proof of behavioral quality or comprehensive security.
- Publishing private examples, expected answers, credentials, or unrelated staged files.
- Running unreviewed global collection installs or assuming a temporary HOME provides a security sandbox.
Frequently Asked Questions
What does this skill produce?
Can I use it with Claude, Codex, or Claude Code?
Does it publish to GitHub automatically?
What do the validation levels mean?
Are behavioral tests fully automated?
Is installation verification a security sandbox?
Developer Details
Author
dontbesilent2025License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
c4bfe0144eb0cdb3563c1735b109699674cbca0e
Maintenance freshness
10/17/2026
Usage
0 downloads · 0 views