fiftyone-code-style
Apply FiftyOne Python Code Style
FiftyOne contributors need consistent Python style across imports, docstrings, utilities, and validation. This skill provides focused conventions and checklists for compatible code.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "fiftyone-code-style" from https://skillstore.io/skills/adonaivera-fiftyone-code-style.md and its manifest at https://skillstore.io/api/skills/adonaivera-fiftyone-code-style/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 "fiftyone-code-style". A new FiftyOne module with mixed import order and missing logger setup.
Expected outcome:
- Move standard library imports before third-party, eta, and FiftyOne imports.
- Add module-level logger setup after imports.
- Use the documented FiftyOne aliases for core modules.
Using "fiftyone-code-style". A function with informal comments instead of a public API docstring.
Expected outcome:
- Use a Google-style docstring with a short summary.
- Add Args entries for each parameter and include defaults where useful.
- Add Returns and Raises sections only when the function behavior requires them.
Using "fiftyone-code-style". A plugin change that imports a heavy optional dependency at module load time.
Expected outcome:
- Use lazy import guidance for optional or heavy dependencies.
- Add a clear fallback or warning path for missing optional packages.
- Confirm the validation checklist covers linting, formatting, and targeted tests.
Security Audit
SafeAll 74 static findings were adjudicated as false positives. The matches are Markdown code fences, inline code, a documentation URL, fixed example validation commands, or a style-guide heading, with no executable malicious behavior found.
Risk Factors
⚙️ External commands (72)
🌐 Network access (1)
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/adonaivera-fiftyone-code-style/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/adonaivera-fiftyone-code-style?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/adonaivera-fiftyone-code-style?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/adonaivera-fiftyone-code-style/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/adonaivera-fiftyone-code-style.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
AdonaiVera. (2026). fiftyone-code-style security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/adonaivera-fiftyone-code-style/audits/8BibTeX citation
@techreport{adonaivera-adonaivera-fiftyone-code-style-2026,
author = {AdonaiVera},
title = {fiftyone-code-style security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/adonaivera-fiftyone-code-style/audits/8},
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: "fiftyone-code-style security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "AdonaiVera"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/adonaivera-fiftyone-code-style/audits/8"
identifiers:
- type: other
value: "skillstore:adonaivera-fiftyone-code-style:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare FiftyOne Contributions
Align new modules, imports, docstrings, and helper functions with FiftyOne repository conventions before submitting a pull request.
Build Consistent Plugins
Use the documented aliases, lazy import guidance, and validation checklist when writing FiftyOne plugin code.
Review Python Changes
Compare proposed code against a compact checklist for import ordering, utility reuse, docstrings, logging, and tests.
Try These Prompts
Review this Python module for FiftyOne code style. Focus on import groups, aliases, module layout, logger setup, and private helper naming.
Rewrite these docstrings in the FiftyOne Google-style pattern. Include Args, Returns, and Raises sections only where they apply.
Inspect this implementation for redundant helpers. Suggest existing FiftyOne or eta utilities that may replace custom path, JSON, image, or type-checking logic.
Perform a FiftyOne style pass on this change. Check import organization, lazy imports, guard patterns, warning behavior, utility reuse, tests, and lint commands.
Best Practices
- Use the import group order before making deeper style changes.
- Check existing FiftyOne and eta utilities before creating new helper functions.
- Run linting, formatting checks, and targeted tests after applying the guidance.
Avoid
- Do not treat the examples as a complete replacement for repository CI.
- Do not add heavy imports at module load time when lazy imports are appropriate.
- Do not create duplicate utilities without checking FiftyOne and eta modules first.
Frequently Asked Questions
What does this skill help with?
Does it modify files automatically?
Can I use it for FiftyOne plugins?
Does it run pylint, black, or pytest?
Is it useful outside FiftyOne?
Which assistants can use it?
Developer Details
Author
AdonaiVeraLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/AdonaiVera/fiftyone-skills/tree/main/code-style/skills/fiftyone-code-styleRef
c1fdca50ff516318f65fed0d7f9e82797c5171dc
Maintenance freshness
7/22/2026
Usage
6 downloads · 292 views
File structure
📄 SKILL.md