fluxly Search skills… ⌘K 中文 Publish

axiom-audit-camera

Security Verified
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Security
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
94 / 100 · audit passed
Author / version / license
@CharlesWiltgen · MIT
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
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，默认拥有全部工具权限。

Output preview axiom-audit-camera.preview 
---
name: axiom-audit-camera
description: Use this agent to scan Swift code for camera, video, and audio capture issues including deprecat…
category: security
runtime: no special runtime
---

# axiom-audit-camera output preview

## PART A: Task fit
- Use case: Use this agent to scan Swift code for camera, video, and audio capture issues including deprecated APIs, missing interruption handlers, threading violations, and permission anti-patterns. You are an expert at detecting camera, video, and audio capture issues — both known anti-patterns AND missing/incomplete patterns that cause UI freezes, dead sessions af….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Tool Use Is Mandatory / Files to Exclude / Phase 1: Map the Capture Pipeline” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Use this agent to scan Swift code for camera, video, and audio capture issues including deprecated APIs, missing interruption handlers, threading violations, and permission anti-patterns. You are an expert at detecting camera, video, and audio capture issues — both known anti-patterns AND missing/incomplete patterns that cause UI freezes, dead sessions af…”.
- **02** When the source has headings, the agent prioritizes “Tool Use Is Mandatory / Files to Exclude / Phase 1: Map the Capture Pipeline” 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.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: Use this agent to scan Swift code for camera, video, and audio capture issues including deprecated APIs, missing interruption ha…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “Tool Use Is Mandatory”, “Files to Exclude”, “Phase 1: Map the Capture Pipeline”, “Step 1: Identify Sessions and Devices”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name axiom-audit-camera directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “Tool Use Is Mandatory / Files to Exclude / Phase 1: Map the Capture Pipeline” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.