Install
$ agentstack add skill-narek-khachikyan-skillranger-frontend-agents-md-bootstrap ✓ 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
Frontend AGENTS.md Bootstrap
Use this skill when creating or improving repo-local AGENTS.md guidance for a frontend project so coding agents understand commands, architecture, conventions, validation steps, and safety boundaries. Do not use it for generic README writing, public product documentation, or agent rules that conflict with the repository's actual scripts and structure.
Decision Rules
- Ground every instruction in files that exist in the repository.
- Prefer concise, durable guidance over long policy text that will drift quickly.
- Include commands only when they are discoverable from project config or documentation.
- Keep agent safety boundaries explicit: do not invent secrets, deployment actions, or destructive maintenance rituals.
Workflow
- Inspect package scripts, test config, build config, framework files, folder structure, and existing docs.
- Identify the project stack, source layout, common commands, test strategy, style conventions, and generated artifacts to avoid editing.
- Draft guidance sections for overview, setup assumptions, commands, coding conventions, validation, and agent-specific cautions.
- Add repo-specific notes only when supported by evidence from files or existing docs.
- Keep the document short enough that an agent can use it as active context.
- Flag any missing information the maintainer should confirm instead of guessing.
References
- No packaged references are required for this MVP skill.
- When available in the project, inspect
package.json, README files, framework config, test config, CI workflow, and existing agent or editor rules.
Validation
- Every command in the output should match a real script, config, or documented workflow.
- The guidance should avoid credentials, private deployment steps, and machine-specific absolute paths.
- If the project already has
AGENTS.md, proposed edits should preserve valid existing conventions and remove only stale or contradictory text with evidence.
Output Contract
- Provide the proposed
AGENTS.mdstructure or patch summary. - Cite the project files that justify commands and conventions.
- List validation commands run or recommended.
- Call out assumptions, missing maintainer decisions, and any safety-sensitive guidance.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Narek-Khachikyan
- Source: Narek-Khachikyan/SkillRanger
- License: MIT
- Homepage: https://skillranger.netlify.app/
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.