📦

birdview

Name: birdview
Author: qiuner

Révision du contenu r1 Sûr ⚙️ Commandes externes⚡ Contient des scripts📁 Accès au système de fichiers🌐 Accès réseau🔑 Variables d’environnement

Map Architecture Before You Change Code

Complex repositories hide ownership, constraints, and change impact. Birdview builds evidence-linked maps and reviewable implementation scopes before coding begins.

Prend en charge: Claude Codex Code(CC)

📊 76 Adéquat

Maintain this Skill? Claim it 📊 76 Adéquat

Arrêtez-vous et demandez confirmation avant l’installation.

Examinez le plan et obtenez le consentement explicite de l’utilisateur avant de modifier des fichiers.

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent

Review the Skillstore skill "birdview" from https://skillstore.io/skills/qiuner-birdview.md and its manifest at https://skillstore.io/api/skills/qiuner-birdview/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/qiuner-birdview.md manifest signé GET /api/skills/qiuner-birdview/manifest lockfile signé GET /api/skills/qiuner-birdview/lockfile

Tester

Utilisation de « birdview ». Map the authentication flow without changing code.

Résultat attendu:

An HTML architecture view showing authentication modules and relationships.
Source-linked evidence for each mapped responsibility.
Coverage notes and unresolved architecture questions.

Utilisation de « birdview ». Plan a cache invalidation change with Birdview.

Résultat attendu:

A change view highlighting current and proposed module impact.
A list of affected files, applicable constraints, and verification steps.
A confirmation request before implementation begins.

Utilisation de « birdview ». Build a complete constraint inventory for the API directory.

Résultat attendu:

A reviewed constraint graph grouped by topic and directory.
Source ranges, applicability decisions, and unresolved conflicts.
An explicit statement of checked coverage and remaining gaps.

Audit de sécurité

Sûr

v1 • 22/09/2026 Ouvrir le rapport versionné

All 400 presented static findings are false positives after contextual review; they arise from generated assets, translated documentation, safe rendering, and explicit CLI, build, or test operations. No prompt injection, credential collection, covert network transfer, or malicious intent was found in the reviewed evidence, but 2,774 capped static matches remain outside this adjudication. Static review was capped at 400/3174 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.

167

Fichiers analysés

21,593

Lignes analysées

Éléments à examiner

Faux positifs ignorés

Facteurs de risque

⚙️ Commandes externes (50)

⚡ Contient des scripts (50)

📁 Accès au système de fichiers (50)

🌐 Accès réseau (50)

docs/index.html:15 docs/index.html:24 docs/index.html:52 docs/index.html:57 docs/index.html:61 docs/index.html:63 docs/installation.md:24 docs/installation.zh.md:24 docs/site.js:92 docs/site.js:97 examples/architecture.json:15 examples/harness-activity.html:272 package-lock.json:29 package-lock.json:46 package-lock.json:63 package-lock.json:80 package-lock.json:97 package-lock.json:114 package-lock.json:131 package-lock.json:148 package-lock.json:165 package-lock.json:182 package-lock.json:199 package-lock.json:216 package-lock.json:233 package-lock.json:250 package-lock.json:267 package-lock.json:284 package-lock.json:301 package-lock.json:318 package-lock.json:335 package-lock.json:352 package-lock.json:369 package-lock.json:386 package-lock.json:403 package-lock.json:420 package-lock.json:437 package-lock.json:454 package-lock.json:471 package-lock.json:478 package-lock.json:488 package-lock.json:500 package-lock.json:505 package-lock.json:547 package-lock.json:554 package-lock.json:560 package-lock.json:564 package-lock.json:571 package-lock.json:586 package-lock.json:593

🔑 Variables d’environnement (27)

Le dernier audit statique et sémantique terminé n’a détecté aucun constat de sécurité confirmé. Cela ne prouve pas que le skill est sans effets secondaires.

Audité par: codex

Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné

Copier le lien du rapport

https://skillstore.io/skills/qiuner-birdview/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/qiuner-birdview/security.svg)](https://skillstore.io/skills/qiuner-birdview?utm_source=security_passport_badge)

Badge HTML

<a href="https://skillstore.io/skills/qiuner-birdview?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/qiuner-birdview/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Carte intégrable

<iframe src="https://skillstore.io/embed/skills/qiuner-birdview.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citations académiques (APA · BibTeX · CFF)

Citation APA

qiuner. (2026). birdview security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/qiuner-birdview/audits/1

Citation BibTeX

@techreport{qiuner-qiuner-birdview-2026,
  author = {qiuner},
  title = {birdview security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/qiuner-birdview/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: "birdview security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "qiuner"
date-released: "2026-09-22"
url: "https://skillstore.io/skills/qiuner-birdview/audits/1"
identifiers:
  - type: other
    value: "skillstore:qiuner-birdview:audit:1"
    description: "Skillstore immutable audit report identifier"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen

Architecture

Maintenabilité

Contenu

Communauté

Conformité aux spécifications

Ce que vous pouvez créer

Understand an unfamiliar repository

Create an evidence-linked architecture map before selecting files or proposing changes.

Review an AI change plan

See affected modules, files, constraints, and verification steps before authorizing implementation.

Trace repository constraints

Collect local instructions, review applicability, and connect approved rules to architecture modules.

Essayez ces prompts

Map this repository

Use Birdview to map this repository. Do not edit code. Show the HTML preview, source evidence, coverage, and uncertainties.

Review project constraints

Use Birdview to discover and review effective constraints for [scope]. Show source coverage, applicability, conflicts, and unresolved gaps.

Plan a focused change

Use Birdview to plan [change]. Map the current architecture, identify affected modules and files, include applicable constraints, and wait for confirmation.

Assess architecture and refactoring

Use Birdview to evaluate [subsystem]. Separate evidence from inference, identify structural risks, propose staged refactoring scopes, and define verification for each stage.

Bonnes pratiques

Start with a specific repository scope and state whether you need architecture, constraints, or a change plan.
Review the rendered HTML, evidence links, uncertainty markers, and coverage notes before accepting the map.
Refresh the map when responsibilities, relationships, constraints, or planned modules materially change.

Éviter

Do not treat a valid schema as proof that module ownership or architectural claims are correct.
Do not use example maps or unreviewed source text as evidence for the current repository.
Do not start implementation before reviewing and confirming the displayed change scope unless confirmation is explicitly waived.