audit-support-deficiency
Sub-skill of audit-support: Deficiency (+4).
Best use case
audit-support-deficiency is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of audit-support: Deficiency (+4).
Teams using audit-support-deficiency should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/deficiency/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How audit-support-deficiency Compares
| Feature / Agent | audit-support-deficiency | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of audit-support: Deficiency (+4).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Deficiency (+4) ## Deficiency A deficiency in internal control exists when the design or operation of a control does not allow management or employees, in the normal course of performing their assigned functions, to prevent or detect misstatements on a timely basis. **Evaluation factors:** - What is the likelihood that the control failure could result in a misstatement? - What is the magnitude of the potential misstatement? - Is there a compensating control that mitigates the deficiency? ## Significant Deficiency A deficiency, or combination of deficiencies, that is less severe than a material weakness yet important enough to merit attention by those charged with governance. **Indicators:** - The deficiency could result in a misstatement that is more than inconsequential but less than material - There is more than a remote (but less than reasonably possible) likelihood of a material misstatement - The control is a key control and the deficiency is not fully mitigated by compensating controls - Combination of individually minor deficiencies that together represent a significant concern ## Material Weakness A deficiency, or combination of deficiencies, such that there is a reasonable possibility that a material misstatement of the financial statements will not be prevented or detected on a timely basis. **Indicators:** - Identification of fraud by senior management (any magnitude) - Restatement of previously issued financial statements to correct a material error - Identification by the auditor of a material misstatement that would not have been detected by the company's controls - Ineffective oversight of financial reporting by the audit committee - Deficiency in a pervasive control (entity-level, IT general control) affecting multiple processes ## Deficiency Aggregation Individual deficiencies that are not significant individually may be significant in combination: 1. Identify all deficiencies in the same process or affecting the same assertion 2. Evaluate whether the combined effect could result in a material misstatement 3. Consider whether deficiencies in compensating controls exacerbate other deficiencies 4. Document the aggregation analysis and conclusion ## Remediation For each identified deficiency: 1. **Root cause analysis:** Why did the control fail? (design gap, execution failure, staffing, training, system issue) 2. **Remediation plan:** Specific actions to fix the control (redesign, additional training, system enhancement, added review) 3. **Timeline:** Target date for remediation completion 4. **Owner:** Person responsible for implementing the remediation 5. **Validation:** How and when the remediated control will be re-tested to confirm effectiveness
Related Skills
llm-wiki-audit-feedback-loop
Durable feedback loop for correcting llm-wiki pages without losing the correction to chat history. Use when (1) a human notices a wiki page is wrong, outdated, or contradicts a source, (2) processing the `audit/` inbox of a domain wiki, (3) reviewing what feedback has been resolved vs deferred, (4) needing to leave a comment on a specific text range that survives line- number drift. Implements the anchored-text audit file pattern from lewislulu/llm-wiki-skill, adapted for workspace-hub's domain-wiki layout under /mnt/local-analysis/llm-wiki/wikis/<domain>/. Extends the 5-op model (compile/ingest/query/lint) from research/llm-wiki with the missing `audit` op. Never silently delete feedback — rejected audits stay archived with rejection rationale.
pre-completion-cleanup-audit
Audit and dispose of session residue (orphan files, scratch dirs, sibling-repo state, locks, trash-stages) BEFORE claiming a task complete. Required gate before any agent says "all done", "task complete", or hands work back to user/orchestrator.
repo-mission-portfolio-audit
Audit the workspace-hub repo portfolio to extract each repo's mission, identify documentation gaps, and prioritize a plan/approval sequence with explicit LLM-wiki weighting for future issue triage.
provider-session-ecosystem-audit-and-exporters
Build and maintain cross-provider session-log audits for Codex, Codex, Hermes, and Gemini, including exporter design, normalization, and behavioral verification.
orcawave-orcaflex-readiness-audit
Audit the real readiness of digitalmodel OrcaWave/OrcaFlex spec-driven workflows by reconciling workspace-hub issues, source/tests, semantic-equivalence boundaries, and wiki synthesis gaps.
read-only-pre-implementation-audit
Systematic cross-check workflow to validate assumptions before TDD coding begins
provider-audit-bootstrap-and-path-classification
Fix provider-session ecosystem audit failures caused by source-checkout imports and over-aggressive symbolic-path classification.
gtm-site-readiness-audit-local-vs-production
Audit GTM feature work by separating local artifact readiness from production deployment state, then fix common blockers in aceengineer-website and GTM collateral.
gsd-operational-audit
Audit a repo's live GSD/get-shit-done workflow state against docs, issues, and runtime outputs to find stale issues, automation reliability gaps, parser drift, migration residue, and policy contradictions.
github-issue-label-existence-audit
Prevent GitHub issue creation failures by auditing exact label existence, duplicate titles, and partial-create risk before calling gh issue create.
github-issue-label-audit-and-command-bundles
Safely turn drafted issue bodies into reusable gh issue create commands by auditing repo labels, exact duplicates, and auth first.
orcaflex-spec-audit
Audit, classify, and score OrcaFlex spec.yml files across the model library for quality, schema validity, and structure type categorization.