agentleFS
Sign inStart free
arunendapallyarunendapally/portfolio-copilot/skills/analyze/SKILL.md

analyze

Skill0 starsChanged 29 days agoMITView on GitHub

Fundamentals assessment of one NSE/BSE stock the investor holds or names. Use for "analyze [stock]", "is [stock] worth holding", "fundamentals of [stock]", "should I re-enter [stock]".

70 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use constitution, revise and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArvorCoSkill

    constitution

    Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.

    Also in 4 projects that use this

  • stormlightlabsSkill

    revise

    Address review comments on an open pull request and push the fixes. Use for /edit, /revise, or when asked to respond to review feedback on a PR number.

    Also in 3 projects that use this

  • DockerSkill

    write

    Write or edit reader-facing technical prose for immediate comprehension. Use for documentation, PR titles and descriptions, release notes, design documents, user-facing explanations, and substantive comments. Also use when asked to make writing clearer, more natural, less AI-generated, or easier to read. For documentation fixes, handles edits, formatting, self-review, and commits after research identifies what to change. Do not use for code-only tasks with no prose deliverable.

    Also in 6 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 5 projects that use this

  • H-mmerSkill

    submit

    Draft and submit a vulnerability report to the bug bounty platform. Reads scope.yaml for platform/program, uses brain + findings for content. Always drafts first for review.

    Also in 3 projects that use this

  • GoogleSkill

    quality

    Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

    Also in 3 projects that use this

  • +1 more from ArvorCo

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 60 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always delegate: spawn the fundamentals-analyst agent (Task tool) with the symbol, whether it is held, and the investor's verdict from …

    line 9

“Common” is measured: kept by at least 6 in 10 of the 60 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Analyze

  1. Confirm the stock is held or was named by the investor. If they ask "what should I buy", explain that this tool analyzes their choices and offer to analyze a name they pick.
  2. Always delegate: spawn the fundamentals-analyst agent (Task tool) with the symbol, whether it is held, and the investor's verdict from profile_get verdicts.<SYMBOL>. One agent per stock; several stocks run in parallel. Do not answer inline.
  3. Show the agent's report unchanged: keep its format, bracketed source quotes and vintages; do not summarise, reword or add numbers. If the analysis disagrees with a standing verdict, say so and suggest the investor update the verdict; never edit it yourself.
  4. If the report's Data gaps line names a blocked primary source (Screener.in, NSE/BSE filings), tell the investor this is a partial analysis before any stop or exit decision, and do not classify the name against GTT policy rule 5 from it. Offer a re-run once the source is allowed (see README, Guardrails).
  5. If the name holds a stop that fails the crash test and the analysis is complete, apply GTT policy rule 5: if the company is weakening, propose verdicts.<SYMBOL>.stop_review = {decision: "keep", at: <today>, reason, review_by: <next results date>}; if it is sound, propose {decision: "widen", at, reason} and the gtt skill. Save with profile_update only after the investor confirms.
  6. log_append a one-line summary with the date.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free