boyue
Govern AI-Assisted Software Decisions
AI coding can turn weak ideas into lasting complexity before teams evaluate value and risk. Boyue applies evidence-based boundaries to scope, ownership, delivery, and retirement decisions.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "boyue" from https://skillstore.io/skills/wuaishare-boyue.md and its manifest at https://skillstore.io/api/skills/wuaishare-boyue/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 "boyue". Should we build a custom analytics export requested by one prospect?
Expected outcome:
Mode: Select. Recommendation: Defer. Demand is not established. Revisit when measured usage or repeated customer requests justify the ownership cost.
Using "boyue". Should an internal workflow become a public API in the first release?
Expected outcome:
Ownership decision: Reduce. Keep the workflow internal until external demand, compatibility needs, and support obligations are understood.
Using "boyue". How should we validate an AI invoice extraction prototype?
Expected outcome:
Test representative invoices, record field accuracy and failure modes, measure latency and cost, and compare a deterministic alternative before committing.
Security Audit
SafeAll 76 static findings are false positives caused by Markdown links, code-span formatting, manual installation examples, ordinary prose, or UTF-8 Chinese text. The skill contains governance guidance and templates, with no runtime code, automatic network activity, credential handling, prompt injection, or data-exfiltration intent.
Risk Factors
🌐 Network access (8)
📁 Filesystem access (47)
⚙️ External commands (4)
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/wuaishare-boyue/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/wuaishare-boyue?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/wuaishare-boyue?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wuaishare-boyue/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/wuaishare-boyue.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
wuaishare. (2026). boyue security audit report (audit version 1) [Author version 0.2.3]. Skillstore. https://skillstore.io/skills/wuaishare-boyue/audits/1BibTeX citation
@techreport{wuaishare-wuaishare-boyue-2026,
author = {wuaishare},
title = {boyue security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/wuaishare-boyue/audits/1},
note = {Author version 0.2.3}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "boyue security audit report (audit version 1)"
version: "0.2.3"
type: report
authors:
- name: "wuaishare"
date-released: "2026-09-07"
url: "https://skillstore.io/skills/wuaishare-boyue/audits/1"
identifiers:
- type: other
value: "skillstore:wuaishare-boyue:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Evaluate a feature request
Separate interesting options from justified commitments, then record a Commit, Defer, or Discard decision.
Review an architecture change
Identify durable ownership surfaces, migration costs, simpler alternatives, and evidence needed before production adoption.
Reduce mature system complexity
Review low-value features, stale settings, dependencies, and services for maintenance, simplification, or retirement.
Try These Prompts
Classify this change as Explore, Select, Shape, Deliver, or Evidence. Explain the lightest useful process and the next decision.
Apply the Commitment Boundary to this feature request. State the problem, evidence, alternatives, non-goals, and recommend Commit, Defer, or Discard.
Review this architecture proposal through the Ownership Boundary. Identify durable surfaces, maintenance obligations, simpler options, and recommend Own, Reduce, or Reject.
Design an evidence plan for this uncertain AI capability. Define hypotheses, representative tests, failure criteria, costs, and a Minimum Coherent Value Slice.
Best Practices
- Use the fast path for small, reversible work that does not expand long-term ownership.
- Record evidence, decision outcomes, and explicit revisit triggers for deferred work.
- Test uncertain AI behavior with representative inputs before designing production architecture.
Avoid
- Do not treat generated code or a successful prototype as proof of product value.
- Do not add permanent APIs, settings, schemas, or services without reviewing ownership costs.
- Do not impose arbitrary numeric gates when project evidence should determine the threshold.
Frequently Asked Questions
Does Boyue write or execute code?
Should every task use every Boyue mode?
What is the Commitment Boundary?
What is the Ownership Boundary?
How does Boyue handle uncertain AI capabilities?
When should a team review retirement?
Developer Details
Author
wuaishareLicense
MIT
Author version
v0.2.3
Skillstore revision
r1
Ref
e5464e662405de6361fdde6b984f9ea865635f64
Maintenance freshness
9/8/2026
Usage
0 downloads · 0 views