bquery-ai-guidance-sync
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Documentation
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Node.js · Bun
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: bquery-ai-guidance-sync
description: Refresh bQuery AI guidance and release metadata. Use when version, engines, exports, AGENT.md, l…
category: documentation
runtime: Node.js / Bun
---
# bquery-ai-guidance-sync output preview
## PART A: Task fit
- Use case: Refresh bQuery AI guidance and release metadata. Use when version, engines, exports, AGENT.md, llms.txt, copilot-instructions, .cursorrules, .clinerules, README, CONTRIBUTING, or check-ai-guidance need to stay in sync. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to Use / Source of Truth / Procedure” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Refresh bQuery AI guidance and release metadata. Use when version, engines, exports, AGENT.md, llms.txt, copilot-instructions, .cursorrules, .clinerules, README, CONTRIBUTING, or check-ai-guidance need to stay in sync. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “When to Use / Source of Truth / Procedure” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “When to Use / Source of Truth / Procedure”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: bquery-ai-guidance-sync
description: Refresh bQuery AI guidance and release metadata. Use when version, engines, exports, AGENT.md, l…
category: documentation
source: tomevault-io/skills-registry
---
# bquery-ai-guidance-sync
## When to use
- Refresh bQuery AI guidance and release metadata. Use when version, engines, exports, AGENT.md, llms.txt, copilot-instr…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to Use / Source of Truth / Procedure” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "bquery-ai-guidance-sync" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to Use / Source of Truth / Procedure
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js / Bun | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}bQuery AI Guidance Sync
When to Use
Use this skill when release metadata, supported engines, public exports, or shared AI-facing repo guidance change.
Typical triggers:
- version bump in
package.json - engine floor changes for Node.js or Bun
- changes in public module exports
- refreshes to
AGENT.md,llms.txt, or.github/copilot-instructions.md - updates to
.cursorrulesor.clinerules - changes to the guidance sync script
- release sweeps for README, docs, or changelog after a public-surface change
Source of Truth
Trust these in order:
package.jsonsrc/*/index.tsAGENT.mddocs/guide/*.mdCHANGELOG.mdfor release deltas and migration context
Procedure
- Confirm the real version, engines, scripts, and exports in
package.json. - Verify the current public runtime surface in the relevant
src/*/index.tsbarrels. - Update the shared AI-facing files as a synced set:
AGENT.mdllms.txt.github/copilot-instructions.md.cursorrules.clinerulesREADME.mdCONTRIBUTING.md
- If public exports changed, re-check
src/full.ts. - If the release messaging changed, update the relevant docs guides and
CHANGELOG.md. - Run the repo sync check before finishing.
Project-Specific Guardrails
- Keep the role split clear:
AGENT.md= deep referencellms.txt= compact mirror.github/copilot-instructions.md= behavioral and meta guidance.cursorrulesand.clinerules= derived snapshots
- Do not let the guidance files drift from
package.jsonversion or engine metadata. - Avoid updating only one guidance file when the change obviously applies to the synced set.
Required Validation
Run:
bun run check:ai-guidance
Use additional validation as needed for the actual code or docs touched.
Source: bQuery/bQuery — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review