acquisition-policy-workflow
Trace Federal Acquisition Policy with Evidence
Federal acquisition policy changes across codified rules, deviations, notices, and guidance. This skill produces dated, sourced analysis with explicit status and decision boundaries.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "acquisition-policy-workflow" from https://skillstore.io/skills/1102tools-dev-acquisition-policy-workflow.md and its manifest at https://skillstore.io/api/skills/1102tools-dev-acquisition-policy-workflow/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 "acquisition-policy-workflow". Explain the current FAR rule for a cited provision as of a specified date.
Expected outcome:
- Documented status: Current codified text as of the requested date.
- Authority layers: Codified text is separated from later notices and guidance.
- Limitations: Procurement-specific applicability remains with authorized officials.
Using "acquisition-policy-workflow". Compare an agency deviation with RFO model text and the eCFR baseline.
Expected outcome:
- Comparison: Each source is listed with scope, effective date, and exclusions.
- Status: Model text is not treated as operative without agency adoption.
- Conflict handling: Material disagreements remain documented and unresolved.
Using "acquisition-policy-workflow". Prepare an Acquisition Policy Impact Brief from approved findings.
Expected outcome:
A validated DOCX brief presents the executive summary, status, timeline, impacts, evidence register, limitations, and reserved determinations.
Security Audit
SafeAll 40 static findings are false positives caused by safe validation, document formatting, and Markdown patterns. The fixed validator subprocess uses an argument list, while archive handling only checks DOCX structure. No credential access, reconnaissance, obfuscation, prompt injection, or exfiltration intent was found.
Risk Factors
โ๏ธ External commands (11)
๐ Filesystem access (3)
๐ Env variables (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/1102tools-dev-acquisition-policy-workflow/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/1102tools-dev-acquisition-policy-workflow?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/1102tools-dev-acquisition-policy-workflow?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/1102tools-dev-acquisition-policy-workflow/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/1102tools-dev-acquisition-policy-workflow.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
1102tools-dev. (2026). acquisition-policy-workflow security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/1102tools-dev-acquisition-policy-workflow/audits/1BibTeX citation
@techreport{1102tools-dev-1102tools-dev-acquisition-policy-workflow-2026,
author = {1102tools-dev},
title = {acquisition-policy-workflow security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/1102tools-dev-acquisition-policy-workflow/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: "acquisition-policy-workflow security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "1102tools-dev"
date-released: "2026-08-24"
url: "https://skillstore.io/skills/1102tools-dev-acquisition-policy-workflow/audits/1"
identifiers:
- type: other
value: "skillstore:1102tools-dev-acquisition-policy-workflow:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Verify Agency Policy Status
Compare codified rules and agency deviations for a defined procurement date and FAR part.
Assess Regulatory Change
Trace a rulemaking timeline and summarize documented operational effects for an industry audience.
Review Public Comments
Analyze a bounded comment sample with recorded search terms, coverage, exclusions, and limitations.
Try These Prompts
Explain FAR 15.404-1 as of 2026-08-24. Distinguish codified requirements from guidance and cite official sources.
Determine documented policy status for [agency], FAR Part [number], as of [date]. Ask for missing procurement dates before retrieval.
Compare eCFR text, RFO model text, and [agency] deviation for FAR Part [number]. Preserve scope, effective dates, exclusions, and conflicts.
Analyze comments for docket [ID] using an approved sample, then prepare a neutral Acquisition Policy Impact Brief with evidence IDs and limitations.
Best Practices
- Provide the exact question, as-of date, agency, FAR part, and relevant procurement dates.
- Approve the source plan before multi-source analysis or formal brief generation.
- Review evidence, conflicts, limitations, and status classifications before approving a brief.
Avoid
- Do not send private, proprietary, classified, credential-bearing, or source-selection information to public research tools.
- Do not treat model deviations, proposed rules, or future-effective rules as current agency policy.
- Do not use sampled public comments as authority, consensus, or a representative survey.
Frequently Asked Questions
Which acquisition sources does this skill use?
Can it determine which clause applies to my procurement?
Can it analyze an agency deviation?
Does it analyze public comments?
Can it create a formal report?
What happens when required tools are unavailable?
Developer Details
Author
1102tools-devLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
f574cb0caf5332a78ff4c1a3035cae6ad409aa6d
Maintenance freshness
8/25/2026
Usage
0 downloads ยท 0 views
File structure
๐ agents/
๐ openai.yaml
๐ references/
๐ document-intake.md
๐ evidence-contract.md
๐ launch-menu-and-framing.md
๐ source-routing.md
๐ status-and-decision-boundaries.md
๐ scripts/
๐ build_acquisition_policy_brief.py
๐ validate_acquisition_policy_brief.py
๐ validate_policy_research_record.py
๐ SKILL.md
๐ test.md
๐ testing.md