Install
$ agentstack add skill-wreos-flutter-cursor-plugin-integrate-mobile-api ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Integrate Mobile API
Use this skill for integrating backend APIs into Flutter applications.
Workflow
- Confirm API scope and constraints:
- protocol (
RESTorGraphQL) - authentication model (JWT, OAuth, API key, session)
- required endpoints/operations
- Define architecture boundaries:
- data layer for client/datasource
- domain layer for repository contracts and use cases
- presentation layer for state updates
- Implement API client with safe defaults:
- timeouts
- retry/backoff policy where appropriate
- request/response logging with redaction
- Add auth handling:
- token attach/refresh strategy
- unauthorized flow (
401/403) and sign-out fallback
- Add DTO mapping and error normalization:
- map API payloads to domain entities
- map transport/server failures to typed domain failures
- Add tests:
- unit tests for mapping and repository behavior
- integration tests for happy/error paths (mock server/client)
- Validate with analysis and impacted tests.
Guardrails
- Do not expose secrets/tokens in logs or source files.
- Keep API client concerns in data layer; avoid direct networking in widgets.
- Do not claim API integration is complete without naming changed files and validation evidence.
- In simulation/planning mode, use
planned/not executedwording.
Required output
- API scope and auth model selected.
- Files changed by layer (presentation/domain/data).
- Validation commands and results.
- Error handling and retry strategy summary.
- Remaining risks/follow-up tasks.
Required references
../../rules/flutter-development-best-practices.mdc../../rules/dart-effective-dart.mdc../../rules/flutter-test-best-practices.mdc
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Wreos
- Source: Wreos/flutter-cursor-plugin
- License: MIT
- Homepage: https://docs.flutter.dev/ai/get-started
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.